Repowire

Repowire
  Let your coding agents talk to each other.

Repowire connects the coding agents you already have open. Claude Code in one repo, Codex in another, a dashboard in your browser, Telegram on your phone: Repowire gives them names and lets them pass messages without copy-paste.

It is a local control layer for multi-agent work: ask another agent a question, send a quick update, schedule a reminder, or run one session as the coordinator.

Use it when:

- One repo needs a concrete answer from an agent already working in another repo.
- You want a personal orchestrator session to dispatch tasks, collect status, or keep reviews moving.
- You want to monitor or nudge agent work from your phone or browser.
- A session should wake itself or another peer later with a scheduled check-in.

Repowire runs locally by default through a daemon on your machine. The hosted relay is optional and uses outbound connections for remote dashboard and remote MCP access.

Quickstart

Requirements: macOS or Linux. Tmux is required for the default Claude Code
workflow and Repowire-managed spawning/lifecycle, but not for pane-less Codex,
OpenCode, or Pi connections. Python is not required.

1. Install Repowire and wire your agents.

Or use the checksum-verified native installer:

The installer downloads a checksum-verified native binary from GitHub Releases.

2. Open your normal agent CLIs.

Use the tools directly; Repowire hooks into them after setup.

3. Check that both peers appeared.

Claude Code registers on session start. Codex registers through App Server when
its TUI thread opens, before the first prompt. Run:

4. Ask from one agent to the other.

In project-a, tell your local agent:

Your local agent invokes Repowire's ask MCP tool, the second agent receives the question, and the…