context-bridge
Switch agents. Not context. Every command, what it is for, and why it behaves the way it does.
Install
npm install -g @serdardb/context-bridge
bridge doctor --fixStart here
Requirements
What has to be installed, which versions, and what "supported" is and is not claiming.
Getting started
Install it, let doctor bootstrap what is missing, then start the loop and switch agents with one command.
Everyday use
Handoffs
One command moves the work. What it carries, what it refuses to carry, and how to see it before it happens.
Lanes and worktrees
One directory can hold several independent conversations, and now each can have its own working tree.
Status, search and watch
Read-only ways to ask what the bridge thinks is true, without changing anything.
Doctor, verify and eval
Doctor reports what it can see, verify proves it works, and the difference between the two is the point.
Your data
Storage and migration
Runtime state left the repository in 0.13.0. This is where it went and how to move an existing project.
Project lifecycle
State that outlives its directory needs a way to be listed, reconnected, archived and permanently removed.
Privacy and what is stored
What is stored, where it lives, what can be in it, and what leaves the machine only when you ask.
Taking context elsewhere
Portable and sealed context
Context you can carry somewhere else: a redacted, hashed bundle, optionally signed, optionally encrypted.
Sharing sealed bundles
An opt-in way to move a sealed bundle between two machines, over a loopback server you run yourself.
Extending
MCP companion
A read-only MCP server over stdio, in a separate package, exposing metadata unless you opt into content.
Adapter contract
Two hundred lines that say what an agent must expose, plus a loader that refuses almost everything. Bringing your own agent is mostly writing the agent.
Aider and Pi
Aider and Pi ship in the package as opt-in candidates. What works, how to turn them on, and exactly what has not been proven.
Reference
Configuration and exit codes
Every environment variable the bridge reads, and the three exit codes it promises.
When something goes wrong
The three failures people actually hit, and what the tool does not do yet.
Release gates
Release gates that bind their result to the exact commit and packages they checked.