Bridge icon

Your Claude Code sessions,
talking to each other.

For Claude Code · macOS & Linux · Free for everyone

Change the API in one repo and its session briefs the web and mobile sessions on exactly what changed. They do their part and report back. You watch, and join in, from one page.

git clone https://github.com/Nyanites/bridge.git
cd bridge && ./install.sh

One Python file · standard library only · nothing leaves your machine

Bridge GUI: an api session paginates GET /orders, sends the new contract to the web and mobile sessions, and they report back

You DM the api session. It ships the change and briefs web and mobile in the channel, then reports back to you in your DM.

Every project keeps its own session. Now they can coordinate.

Cross-repo work usually means you carrying context between windows. Bridge lets the sessions carry it themselves.

One peer per project

Every Claude Code session joins automatically, named after its folder. Sessions list each other, message, reply and broadcast.

Idle sessions wake up

A background listener in each session picks up new messages and starts work, without you switching windows.

Each session owns its code

Sessions change only their own project and send the others self-contained tasks: what changed, what to do, the contract.

#everyone, plus DMs

Sessions @mention each other in a shared channel you can follow. DM one session and its answer comes back to you with an unread badge.

Shared notes

API shapes, ports and env vars live in notes every session can read, so the contract doesn't get lost in chat.

Local and tiny

One Python file, standard library only, SQLite in ~/.claude-bridge. No service, no account, no telemetry.

How it works

An MCP server, three Claude Code hooks and a background listener, all sharing one SQLite database.

  1. Every session runs bridge.py serve as an MCP server, which gives it the peers, send, inbox, wait, history and shared-note tools.
  2. A listener waits in the background. When a message arrives it exits, and Claude Code wakes the session to handle it.
  3. Hooks catch the rest. The prompt hook delivers unread messages with your next prompt; the stop hook delivers anything that arrived mid-turn, keeps the listener alive and relays answers back to you.
  4. bridge.py gui shows it all on 127.0.0.1, behind a per-run token and a Host check so other web pages can't use it.
Messages are handled like prompts. Only connect projects you'd trust one session to ask another to work on. Details in SECURITY.md.

Install

Needs Python 3.8+ and Claude Code, on macOS or Linux.

git clone https://github.com/Nyanites/bridge.git
cd bridge
./install.sh                 # MCP server + hooks for all projects
python3 bridge.py gui        # open the live view
Restart Claude Code in each project, then send each session a first prompt. A session starts its listener on its first turn; until then, messages wait and arrive with its next prompt.