Skip to content

Setup

repowire setup

This is the one-time install step. It runs from your shell, not from inside an agent.

What setup does

For every agent runtime it finds, it wires the appropriate Repowire transport. Auto-detection covers Claude Code, Codex, Gemini CLI, OpenCode, and Pi. Then it installs the local daemon as a user service (launchd on macOS, systemd on Linux).

When setup finishes, the daemon is listening on 127.0.0.1:8377. Open a new agent session in any directory and it will register itself.

repowire setup owns Repowire's transport and routing layer. It does not install third-party skills or Claude Code marketplace plugins; those can be installed separately if you want reusable agent behaviors on top of the mesh.

Useful flags

repowire setup --relay                  # also connect to the hosted relay at repowire.io
repowire setup --experimental-channels  # use the experimental channel/ACP transport (Claude Code v2.1.80+, claude.ai login, bun)
repowire setup --http-mcp               # enable localhost Streamable HTTP MCP at /mcp
repowire setup --update-checks          # let status/doctor report new Repowire releases
repowire setup --non-interactive        # take flag values only, no prompts

--relay makes the dashboard available at https://repowire.io/dashboard over an outbound WebSocket. See relay access.

--experimental-channels replaces the default hooks transport's tmux-injection delivery with direct MCP-channel / ACP delivery for Claude Code only. It is experimental. See Claude Code setup.

--http-mcp is a local-only experimental MCP endpoint for clients that need Streamable HTTP instead of the default stdio server. It generates a daemon.auth_token if needed and requires clients to send Authorization: Bearer <token>. The normal repowire mcp stdio server remains the default setup path.

--update-checks opts this machine into update availability checks from repowire status and repowire doctor. It only reports that a newer release exists; repowire update remains the explicit command that upgrades the installed package, reinstalls hooks/plugins, and restarts the daemon service when needed.

Verifying

repowire status

Shows what was installed, which agents were detected, and whether the daemon is running. If something looks off, see troubleshooting.

You only run repowire setup once per machine. Next: open two agents and route an ask.