repowire 0.14.1

Mesh network for AI coding agents - enables Claude Code, Codex, Gemini, and OpenCode sessions to communicate

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

Quickstart

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

1. Install Repowire and wire your agents.

uv tool install repowire    # or: pipx install repowire / pip install repowire
repowire setup

Or use the interactive installer:

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

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

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.
• 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, runs schedules, and feeds the dashboard timeline.

The stable public surface is still peers, circles, asks, notifications, broadcasts, and schedules. The v0.14 direction is session-native: sessions become the durable unit of work, while peers remain the live runtime executors. The current dashboard shows the selected peer/session view, merges Claude transcript history where available with realtime events, and is moving toward broader session commands for controls like resume, scheduling, approvals, and future backend/model changes.

Transport notes:

• Claude Code, Codex, and Gemini CLI use hooks plus MCP tools.
• OpenCode uses a TypeScript plugin plus WebSocket.
• Pi uses the Repowire extension path when detected by setup.
• Claude Code channel/ACP delivery is experimental and opt-in.
• Relay is optional remote access, not a requirement for local routing.

Supported Agents and Surfaces

Agent runtime	Connection path
Claude Code	Hooks + MCP; optional experimental channel/ACP transport
Codex	Hooks + MCP
Gemini CLI	Hooks + MCP through normalized BeforeAgent / AfterAgent events
Antigravity CLI (agy)	Plugin install verified; hook firing and MCP pending upstream verification
OpenCode	Plugin + WebSocket
Pi	Repowire extension

Human or service surface	Role in the mesh
Dashboard	Browser control surface at localhost:8377/dashboard or through relay
Telegram	Phone control surface and notification target
Slack	Team chat control surface
Orchestrator peer	Long-running coordinator that dispatches and reviews work
Relay dashboard	Optional remote dashboard and cross-machine bridge

repowire setup auto-detects installed runtimes and wires the supported transports it finds.

How It Compares

The agent-orchestration space is moving fast. Most projects cluster around a few shapes:

• Worktree/task runners: Claude Squad, Vibe Kanban, and dmux help launch and review many isolated agent workspaces.
• Deterministic schedulers: Bernstein decomposes goals, runs agents in parallel worktrees, verifies, and merges passing work.
• Hierarchical swarms: multi-agent-shogun defines manager/worker roles and routes tasks through tmux, files, or role-specific protocols.
• Agent IDEs and workflow systems: HumanLayer/CodeLayer focuses on planning, review, team workflows, and richer agent workspaces.

Repowire sits in a different slot: it is a live mesh and control plane for agent sessions you already have running. It does not try to be the scheduler that decomposes every goal, the kanban board that owns every branch, or the merge gate that lands code. It gives your existing terminals, dashboard, Telegram, Slack, and orchestrator session a shared address book, message lifecycle, schedule queue, and local session timeline.

Common Workflows

Ask another repo

Project A needs the real API shape from Project B. Ask project-b; the peer answers from its live checkout, not stale docs. See multi-repo coordination.

Drive from phone or dashboard

Send work to a peer from Telegram, Slack, or the dashboard, then receive progress updates from agents as notifications. Telegram and Slack human messages open tracked asks by default; use their notify/FYI commands for fire-and-forget nudges. See mobile mesh management.

Coordinate with an orchestrator

Run one session as the orchestrator. It can dispatch to project peers, ask for status, review PRs, and wake itself later. See orchestrator coordination.

Wake a peer later

Schedule a reminder, check-in, or future ask:

repowire schedule self 10m "check CI"
repowire schedule create orchestrator 1h "handoff" --from-peer project-a --kind ask

Bridge machines

Enable the hosted relay when you want remote dashboard access or cross-machine mesh traffic:

repowire setup --relay

Dashboard

The dashboard shows peers, status, descriptions, chat turns, tool calls, attachments, and the selected peer/session timeline. For Claude Code peers, it can merge transcript history with realtime events; other backends contribute realtime events as their transports report them.

Run it locally at:

http://localhost:8377/dashboard

With relay enabled, use:

https://repowire.io/dashboard

Core Commands

repowire setup                         # install hooks/MCP/plugin/service for detected agents
repowire setup --http-mcp              # opt in to localhost Streamable HTTP MCP at /mcp
repowire setup --update-checks         # let status/doctor report available updates
repowire update                        # explicit package upgrade + hook reinstall + daemon restart
repowire status                        # show installed components and daemon status
repowire doctor                        # run diagnostics
repowire service restart               # restart the installed daemon service
repowire peer list                     # list mesh peers
repowire peer new PATH                 # spawn a peer in tmux
repowire schedule self 10m "check CI"  # wake this peer later
repowire telegram start                # run Telegram service peer
repowire slack start                   # run Slack service peer

The daemon uses ~/.repowire/state.db for durable local state. On first startup after install or update, it applies SQLite migrations and imports legacy schedules.json, events.json, and sessions.json once while leaving those files in place for downgrade/export compatibility. Migrated state is written to SQLite, and repowire doctor reports the SQLite schema, integrity, and import status.

See the full CLI reference and MCP tools reference.

Configuration and Security

Config lives at ~/.repowire/config.yaml.

daemon:
  host: "127.0.0.1"
  port: 8377
  auth_token: "rw_local_..."
  mcp_http:
    enabled: false
    bind: "localhost-only"
    require_auth: true
    allow_dangerous_tools: false
  spawn:
    commands:
      claude-code: "claude --dangerously-skip-permissions"
      codex: "codex --dangerously-bypass-approvals-and-sandbox"
      gemini: "gemini --yolo"
    allowed_paths: [~/git, ~/projects]
updates:
  check_enabled: false

relay:
  enabled: true
  url: "wss://repowire.io"
  api_key: "rw_..."

Update checks are off by default. If enabled with repowire setup --update-checks, repowire status and repowire doctor may report that a newer release is available, but they do not upgrade packages, rewrite hooks, or restart services. Use repowire update when you want to upgrade explicitly; it preserves enabled package extras such as repowire[acp] where practical.

Security defaults:

• Local daemon binds to 127.0.0.1.
• Relay is opt-in and uses outbound WebSocket.
• WebSocket and local HTTP auth are available through daemon.auth_token.
• Experimental HTTP MCP is opt-in, localhost-only, bearer-authenticated by default, and not exposed through the hosted relay.
• Spawn requires explicit command and path allowlists.
• Experimental channel/ACP transport is opt-in.

Developing From Source

git clone https://github.com/prassanna-ravishankar/repowire
cd repowire
uv sync --extra dev
uv tool install . --force-reinstall

Hooks and MCP servers run the installed repowire executable, not your checkout. After changing daemon, hook, or MCP code locally, reinstall the tool and restart the daemon service so the live mesh uses the new code:

uv tool install . --force-reinstall
repowire setup --non-interactive   # rewrites hooks/MCP/service to the installed local build
repowire service restart           # enough when only daemon code changed

If service management fails, use repowire service status first. Raw launchctl on macOS or systemctl --user on Linux are fallback troubleshooting tools.

References

• Quickstart
• Architecture
• MCP tools
• CLI
• Agent setup
• Control surfaces
• Troubleshooting
• Comparisons

Uninstall

repowire uninstall
uv tool uninstall repowire

repowire uninstall removes hooks, MCP entries, channel transport config, OpenCode plugin files, and the daemon service. It does not automatically remove ~/.repowire/, which contains local config, events, attachments, and relay keys.

Contributing

See CONTRIBUTING.md. Before opening a PR, run the advisory repo-hygiene checklist:

python3 scripts/pre_pr_hygiene.py

It is an opt-in prompt for docs, README, agent-instruction, and graphify follow-ups, not a mandatory hook. It also flags Beads JSONL ledger churn before it can leak into PR diffs.

License

MIT