Five native sessions, running at once
Every switch meant rebuilding context, rewriting summaries or starting over.
The context should follow.
Watch the work move.
-
Record
Decisions and open questions
-
Diff
Compare what the target knows
-
Pack
Build bounded delta
-
Switch
Close one TUI, open the next
-
Resume
Continue inside native session
No copied transcript. No wrapper session. No restart.
Five agents. Equal citizens.
Same knowledge on every side. The session shape differs per agent, and each difference is stated, not glossed.
State, not transcripts. And not in your repo.
- Native Claude session
- Native Codex session
- Native Grok session
- Native Antigravity session
- Native OpenCode session
global project store
session refssync watermarksrecovery journalspending markersCanonical memory stays where it belongs: inside each agent's own session. What links them now lives outside the project entirely.
-
No transcripts
-
No SaaS
-
No telemetry
-
No API keys
One directory. More than one conversation.
Lanes isolate context. Now they can isolate the working tree too.
$ bridge lane$ bridge lane new refactor --seed main$ bridge lane switch main Each lane keeps its own agent links, switch history and checkpoints. Two terminals can run without their context colliding.
Parallel conversation — and, when a lane takes a worktree, parallel code.
More than a switch.
bridge status --json
linked sessions, machine-readable
bridge verify
every agent answers, every route configured
bridge inspect
what the last handoff actually ran
bridge handoff codex --dry-run
the road and payload, writing nothing
bridge search <text>
across local summaries and audits
bridge storage plan
preview the move out of .bridge/
bridge project adopt <id>
reconnect a directory that moved
bridge artifact export
a redacted, hashed context bundle
bridge artifact seal
encrypt it; the key leaves separately
bridge watch
metadata changes, read-only
Commands that change things preview first and act on --apply. Purge asks for the id typed back.
Engineering principles.
-
Local and private
No SaaS. No telemetry. Credentials are detected, never read.
-
Boundaries stated
macOS, with selected Linux and Windows acceptance. Power-loss durability is not claimed.
-
Failures visible
Inspect shows what agents actually ran, failures first.
-
Safe by default
Clean supports dry-run. Pending injection is never deleted.
The product is the handoff. Trust is the rest of the system.
npm install -g @serdardb/context-bridge