Menu
Theme

Years I contributed:2026Developer tools · Open source

Context7 Widget

An independent Context7 chat widget that developers can adapt to their own product’s UI.

My role
Creator & key maintainer
Context
Personal initiative · DeSource Labs · Open source
Explore the project

I started Context7 Widget because the default embed did not offer enough control to fit the products using it. Fonts, spacing, buttons, and panel layout should match the rest of the application.

I am the author, creator, and key maintainer. The project provides a customizable interface around Context7’s documentation search and answers, with a drop-in script and native framework integrations. It is open source, and I welcome other contributors.

Built with
TypeScriptWeb ComponentsVue / NuxtReactAngularSvelteGitHub Actions
  • Control over the embedded UI

    Built customization for typography, colors, triggers, and panel layout so the widget can fit the product around it.

  • Framework integrations and chat behavior

    Built native framework packages around shared conversation and transport logic, with multiline questions, copyable code, Stop and Retry controls, and reading-aware scrolling.

  • Coexisting with the host application

    Handled keyboard-event boundaries so typing in the chat does not also trigger the host page’s shortcuts. Added unit and browser tests across the integrations to check that behavior.

Maintaining a UI for someone else’s backend

Context7 owns the backend and can change its request or streaming behavior independently. That makes compatibility an ongoing part of maintaining the widget, even when its appearance and public API stay the same.

I added a scheduled GitHub Actions workflow that compares the official widget’s JavaScript with a stored snapshot. When it changes, the workflow saves the new version and opens or updates a compatibility issue with the previous and current hashes. That gives me a concrete diff to investigate.

A changed bundle is a signal to review the request payloads and streaming format; it does not prove that an integration has broken. The workflow keeps that review visible, while testing and any necessary fixes remain separate maintenance work.

My independent practice

My independent work spans client collaborations and my own developer tools. I established my business in January 2025, building on earlier project work. I handle architecture, implementation, and delivery; when a project needs more capacity, I can bring designers and engineers through DeSource Labs.

Career timeline January 2025–present

  1. Individual Entrepreneur / Software Development Consultant

    January 2025–present

Broader responsibilities

Hands-on product development and technical consulting through my own business.

  • Develop web applications, front-end systems, and integrations for clients, from technical planning through implementation and handover.
  • Work on software architecture, backend and infrastructure planning, AI integrations, and blockchain applications.
  • Create and maintain developer tools including Phone Mask, DeSource Image, Context7 Widget, and Browser AI.
Full CV
Start a conversation

What are you
working on?

An engineering role, a product to build, or a technical problem to work through. I’d like to hear about it.