Local-first agent team harness

Coordinate agent teams locally.

Repowire gives Claude Code, Codex, Gemini CLI, and OpenCode sessions an address in one mesh so they can ask each other questions, send updates, schedule follow-ups, and stay steerable from your browser or phone.

Start in 5 minutes View source

Default: local daemon
Messages: ask / notify / schedule
Surfaces: dashboard / Telegram / Slack

dashboard

See peers, status, chat turns, tool calls, and routed messages from the same browser surface that can reach your local daemon or optional relay.

real product surface

What changes day to day

Less terminal babysitting. Better handoffs.

Repowire is not another coding agent. It is the operating layer around the agents you already run, with practical messaging and control surfaces for multi-session work.

Ask across repos

Need the real API shape from another checkout? Ask the live peer that is already working there and get an explicit ack back.

Coordinate with an orchestrator

Keep one session focused on dispatch, status checks, review handoffs, and follow-ups while project peers do the implementation work.

Steer from browser or phone

Use the dashboard, Telegram, or Slack as human peers when you want to monitor, nudge, or route work without returning to every terminal.

Schedule the next nudge

Wake a peer later for CI checks, review reminders, morning handoffs, or any other deferred ask or notification.

Local by default

The daemon runs on your machine. The hosted relay is optional for remote dashboard access and cross-machine mesh traffic.

Transport-aware, not transport-locked

Hooks and MCP are the stable path today; Claude Code channel/ACP delivery is experimental and opt-in as the routing boundary hardens.

How it works

One routing layer for agents and humans

The daemon is the hub. Agents remain the workers, transports handle delivery, and human surfaces become first-class peers you can use when you need to steer.

Sessions register as peers

Setup wires supported agents into the mesh. Each live Claude Code, Codex, Gemini CLI, or OpenCode session gets a routable identity.

A message enters the daemon

Agents and human surfaces send asks, notifications, broadcasts, or schedules through MCP, hooks, the dashboard, Telegram, Slack, or the CLI.

The router chooses delivery

The local daemon checks peer state, circle access, and available transports, then forwards the message without needing every agent to know every integration.

The thread stays visible

Open asks keep resurfacing until acked, and the dashboard timeline shows recent peer activity, tool calls, attachments, and routed messages.

Architecture, simplified

local daemon → transport router → agent session → ack or timeline event

Roadmap, without overclaiming

Repowire is moving toward a session-native model where sessions are the durable unit of work and commands such as resume, scheduling, approvals, and future backend/model controls share one command surface. Those controls are being shipped in compatible slices, not all at once.

Install

Start with two local sessions

Repowire runs on macOS or Linux with Python 3.10+ and tmux. The one-liner installs the CLI and runs setup; manual uv, pipx, and pip paths are documented too.

quickstartlocal-first

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

Run setup

Open two agent sessions

Ask one peer from another

Prefer manual install? uv tool install repowire && repowire setup