Open source, local-first
Claude Code, Codex, OpenCode and Pi sessions get an address on one local mesh, and ask each other directly.
$brew install prassanna-ravishankar/repowire/repowire$repowire setupClaude asks a Codex peer for a review. The question crosses the mesh, Codex reads the code in its own checkout, and the answer comes back as an ack that closes the thread. Nothing is copy-pasted between terminals.
You talk to your agent in plain language; it calls these as MCP tools. Every message has a sender, a recipient and, for asks, a thread that has to be closed.
A question that expects closure.
The thread stays open, and resurfaces at the end of every turn, until the peer acks. Use it for reviews, handoffs and checkpoints.
ask("api-claude", "What does /me return now?")[ack #c1a1 from @api-claude] { user, session }, no wrapper.Fire and forget.
A status update, a heads-up, a note to your phone. Delivered now, or queued for the peer's next turn if it is busy.
notify_peer("telegram", "Deploy finished, CI green.")delivered · @telegramOne line to the whole circle.
Every online peer in your circle hears it. No thread, no reply. Treat it as a soft interrupt: freezes, renames, hold-your-pushes.
broadcast("Freezing main for the v0.21 release.")sent to 5 peersEach runtime connects the way it can. The daemon on :8377 is the only hub: identity, routing and lifecycle live there, not in the transports.
The dashboard, Telegram and Slack join the mesh as peers, so an agent asks you a question the same way it asks another agent.
@api-claudeMigration 0042 applied. CI green.
legacy_sessions. Ship it now, or hold for review?[ask #c91f2b]$repowire share my-agent --rw --ttl 3600Turn on the commit hook in a repository and every commit made from a registered agent pane carries Repowire-Thread trailers for the asks it closed since the last commit. repowire why replays those threads: who asked, who answered, and how it closed.
$repowire setup --git-hooksDurable jobs carry lifecycle and results, one-off or on a cron. Schedules wake a peer later, and an orchestrator session can keep the queue moving while you are away.
Ask the peer nearest the code to review a component, a migration or a branch before you merge it.
Ask the API repo what changed, then let the frontend peer adapt to the answer it acks back.
Ask another session for the exact file, endpoint, schema or command output from its own checkout.
Status that has to land. An open ask keeps resurfacing until the peer closes it.
Have a different backend critique the approach while the first agent keeps the thread moving.
Route the same ask through Telegram, Slack or the dashboard when a person has to decide.
Tail every ask, ack and notify as it happens. Open a peer to read its turns, steer it, or step in, from your desk or your phone.
macOS or Linux. Tmux for the default Claude Code workflow. No Python, no account, no inbound ports.
$brew install prassanna-ravishankar/repowire/repowire$repowire setupOr the checksum-verified native installer: curl -fsSL https://github.com/prassanna-ravishankar/repowire/releases/latest/download/install.sh | sh
$cd ~/projects/api && claude$cd ~/projects/web && codexOne per tmux window. Setup already hooked them in; there is nothing new to launch.
$repowire peer listClaude Code registers on session start, Codex when its thread opens.
❯Ask web what the auth response shape is.Say it to your agent in plain words. It calls ask, and the answer comes back as an ack.
Spawning peers, profiles, circles and the relay are in the docs.