Running Claude Code in one repo while needing information from another is a constant friction point. You either copy-paste context manually, maintain stale documentation, or just give the agent incomplete information and hope for the best. RepoWire, a new open-source project by Prassanna Ravishankar, tries to fix this by letting multiple Claude Code sessions talk to each other directly.
The setup works like this: a central WebSocket daemon routes messages between "peers," where each peer is a Claude Code session attached to a specific repository. Peers can send three types of messages: blocking questions (with a 300-second timeout), fire-and-forget notifications, and broadcasts to all peers in a group. The communication is synchronous, more like a phone call than email. One agent asks a question and waits for an answer from the agent that actually has the relevant codebase loaded.
Practical Setup
Installation uses uv or pip, and the tool requires macOS or Linux, Python 3.10+, and tmux (a terminal multiplexer that lets you run multiple terminal sessions). A typical setup looks like:
- Install RepoWire, run the setup command
- Create peers pointing at different project directories
- Group peers into "circles" (logical networks mapped to tmux sessions)
- Agents discover each other and can query across repos
The tool provides MCP tools including ask_peer, notify_peer, broadcast, list_peers, and spawn_peer, so Claude Code sessions can use them natively. There's a web dashboard at localhost:8377 for monitoring peer status, plus optional Telegram and Slack bot integrations for mobile control.
RepoWire targets 5-10 collaborating agents, which is a different niche than tools like Gastown (async orchestration for 20-30 agents) or Claude Squad (session management with worktrees). The project has 30 GitHub stars and hit v0.8.0 on March 27. It's MIT licensed.
The concept is interesting but early. Real-time agent-to-agent communication across codebases is something that will matter more as people run longer, more complex AI coding sessions. Right now the main audience is developers already deep into multi-agent workflows who want their Claude Code instances to stop working in isolation.