repowire

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 access and cross-machine mesh traffic.

Quickstart

Requirements: macOS or Linux, Python 3.10+, tmux.

1. Install Repowire and wire your agents.

curl -sSf https://raw.githubusercontent.com/prassanna-ravishankar/repowire/main/install.sh | sh
repowire setup

The installer detects uv, pipx, and pip in that order.

2. Open your normal agent CLIs.

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

# tmux window 1
cd ~/projects/project-a && claude

# tmux window 2
cd ~/projects/project-b && codex

3. Check that both peers appeared.

Claude Code registers on session start. Codex registers after its first interaction, so send a short warmup prompt in project-b, then run:

repowire peer list

4. Ask from one agent to the other.

In project-a, tell your local agent:

Ask project-b what API endpoints they expose.

Your local agent invokes Repowire's ask MCP tool, the second agent receives the question, and the reply comes back as an ack notification. Repowire is the mesh and tool surface around the agents, not a standalone chat UI. The same pattern works across Claude Code, Codex, Gemini CLI, OpenCode, and Pi when those runtimes are installed.

https://github.com/user-attachments/assets/a9eab9c4-8aea-4dbb-8914-e998311b6d14

You can also spawn peers through Repowire:

repowire peer new ~/projects/project-a
repowire peer new ~/projects/project-b --backend codex --profile fast

For durable recurring workers, scaffold a repo-local agent folder and target it from jobs:

repowire agents create daily-brief --backend codex
repowire jobs create "Daily brief" --path .repowire/agents/daily-brief --backend codex --cron "@daily" --prompt "Prepare the brief."

Full docs: docs.repowire.io.

What You Get

• Agent-to-agent asks: Non-blocking questions with explicit ack replies and reminder injection until a thread is closed.
• Human control surfaces: Browser dashboard, Telegram, and Slack can route messages as service peers.
• Durable jobs: Track one-off and recurring work through CLI/MCP, with dashboard visibility and controls for run, retry, and cancel.
• Orchestrator pattern: A dedicated peer can dispatch work, check status, coordinate reviews, and keep a queue moving.
• Scheduled wake-ups: Send a future notification or ask to yourself, another peer, or an orchestrator.
• Optional relay: Reach the dashboard remotely and bridge machines without opening inbound ports.

How It Works

All peers connect to a local daemon. The daemon keeps the registry, routes asks/notifies, tracks open asks, stores durable jobs, runs schedules, and feeds the dashboard timeline.