Repowire CLI
A local mesh for coding agents: Claude Code, Codex, OpenCode and Pi exchange questions across projects and machines
- 272 ★ on the repository
- Last commit
Broad access
Why this level
- Hooks and MCP tools let one agent send questions and tasks to another, while Telegram, Slack and the relay give remote control over sessions
- The daemon listens on a local dashboard port, and the relay secret sits in `~/.repowire/config.yaml`
Install
- Works in
Manual install
brew install prassanna-ravishankar/repowire/repowireThen run `repowire setup`: it finds installed agents and connects them. Needs macOS or Linux.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Hooks and MCP tools let one agent send questions and tasks to another, while Telegram, Slack and the relay give remote control over sessions
- The daemon listens on a local dashboard port, and the relay secret sits in `~/.repowire/config.yaml`
This is third-party code. Review the repository files before installing.
What it does
Repowire links the agent sessions you already have open into one network. Each session gets a name, and the agent in one project can ask the agent in another, for example which endpoints it exposes. The question goes through the `ask` MCP tool, the peer answers from its live working directory and the reply comes back as an `ack` notification. All participants connect to a local daemon that keeps the session registry, routes questions, tracks open asks and runs schedules. Claude Code connects through hooks and MCP, Codex through App Server, OpenCode through a TypeScript plugin and Pi through its own extension. The `repowire setup` command finds installed agents and wires them itself. Beyond questions there is a browser dashboard, control from Telegram and Slack, an inbox for the human, delayed reminders with `repowire schedule` and recurring scheduled jobs. The `repowire why` command uses commit trailers to show which conversations led to a change. An optional cloud relay adds remote access to the dashboard and a remote MCP.
Who it is for. Developers who keep several repositories and agents open at once and are tired of copying answers between them by hand.
Good fit when
- One repository needs the real API shape from another, and that project's agent is already running and knows its codebase
- A coordinator session should dispatch tasks to projects, collect status and keep reviews moving
- You want to watch the agents and answer them from a phone through Telegram or from a browser dashboard
- An agent should wake itself in ten minutes and check the build result
Not a fit when
- You need a scheduler that splits a goal into tasks and merges verified code: Repowire only links sessions that are already running
- Agents on different machines must message each other: the relay does not let such machines talk to each other
- Your system is neither macOS nor Linux: the README targets those two platforms
- You want a standalone chat window for people: Repowire is a mesh and dashboard around agents with no chat of its own
Example request
Ask the agent in project-b which endpoints it exposes and show me its replyLimitations
- It runs on macOS and Linux. The standard Claude Code setup needs tmux, while Codex, OpenCode and Pi do not require it.
- Claude Code must be version 2.1.224 or newer.
- The optional cloud relay uses outbound connections, and its secret is stored in `~/.repowire/config.yaml`.
- The Channel and ACP bridge for Claude Code is marked experimental and is enabled separately.
- The dashboard and the session model are still evolving: the author plans broader session control commands.
How to disable. Remove the Repowire connections from the agents' configs, stop the daemon and uninstall the package, for example with `brew uninstall repowire`. If you enabled the relay, delete the secret from `~/.repowire/config.yaml` and the `repowire-remote` plugin in Claude Code.
FAQ
How do I install Repowire?
On macOS and Linux run `brew install prassanna-ravishankar/repowire/repowire`, then `repowire setup`. There is also a checksum-verified script: `curl -fsSL https://github.com/prassanna-ravishankar/repowire/releases/latest/download/install.sh | sh`.
How do I check that agents see each other?
Open normal `claude` and `codex` sessions in different directories and run `repowire peer list`. Claude Code registers at session start and Codex when its terminal thread opens.
Does it need internet access or a third-party server?
By default the daemon runs locally on your machine. The cloud relay is optional and only serves the remote dashboard and the remote MCP.
Can I control agents from a phone?
Yes. Telegram and Slack act as control surfaces: a human message opens a tracked ask, and separate notify and FYI commands cover fire-and-forget nudges.
What is repowire why?
The command uses the `Repowire-Thread` and `Repowire-Session` trailers in a commit to show the agent conversations behind a change. It covers Claude Code commits made through Repowire.
Discussion
No questions or reviews yet.
Related
CLI toolsA local control panel for coding agents: it runs Claude Code and Codex, keeps a task queue and merges verified work into main.
A Rust daemon and MCP server: a team's Claude Code, Codex, Cursor and other agents exchange encrypted messages directly
DevChain runs a team of AI coding agents on your own machine with a shared board, chat, code review and live terminals.
A bridge between local CLI agents: Codex, Cursor or Claude Code delegate work to Antigravity, Grok, Kimi and seven more.
Agents Can Communicate (ACC)
Agents Can Communicate
ACC passes questions, reviews and handoffs between Claude Code, Codex and other client sessions on one machine
A hub and the anet CLI join Claude Code, Codex, Grok and OpenCode from different machines into a network driven from one window.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Repowire (this card) | no | 272 | ||
| MCP Agent Mail | no | API key | 2,232 | a mailbox for agents over MCP, without live sessions, schedules or a dashboard |
| AgentPeerChat | no | 162 | an agent-to-agent chat as a skill, without a daemon, session registry or mobile control |
README in short
The README starts from the task: give open agents names and let them pass messages without copy-paste. It continues with a quick start, a feature list, the daemon's design, tables of supported agents and surfaces, a comparison with schedulers and common workflows.