Reference

CLI

The repowire command is a thin wrapper around setup, the daemon, and the bot peers. Most users only ever need setup. Everything else is for operators running their own daemon or control surfaces.

repowire setup

repowire setup [--relay] [--experimental-channels] [--http-mcp] [--no-service] [--non-interactive]

One-time install. Detects every supported agent runtime present (Claude Code, Codex, Gemini CLI, OpenCode), wires the appropriate Repowire transport for each, and installs the daemon as a user service. --relay opts in to the hosted relay at repowire.io. --experimental-channels enables the experimental MCP channel / ACP transport for Claude Code. --http-mcp enables localhost Streamable HTTP MCP at /mcp and generates a bearer token if needed. --no-service skips daemon service installation. --non-interactive skips prompts and uses flag values only.

repowire serve

repowire serve [--host HOST] [--port PORT] [--relay]

Run the daemon in the foreground. Useful for debugging hooks or running outside the installed service. Defaults to 127.0.0.1:8377.

repowire service

repowire service install
repowire service restart
repowire service status
repowire service uninstall

Manage the installed daemon user service. install writes and starts the platform service (launchd on macOS, systemd --user on Linux), restart restarts the installed daemon after a local reinstall or config change, status shows whether it is installed/running, and uninstall removes the service entry. Prefer these commands over raw launchctl or systemctl unless you are troubleshooting the platform service manager directly.

repowire build-ui

repowire build-ui

Build the Next.js dashboard into the static export served by the daemon at /dashboard. Run after editing files under web/.

repowire peer

repowire peer list
repowire peer describe NAME_OR_ID [--circle C]
repowire peer claim-role orchestrator [--peer NAME_OR_ID] [--circle C] [--force]
repowire peer prune

Inspect and repair registered peers. peer list is an operator view across all circles. peer describe shows one peer's identity, role, liveness, open asks, and recent events. peer claim-role orchestrator is a narrow repair command for an existing peer whose durable session mapping lost the orchestrator role after daemon restart; it refuses to demote a fresh online or busy holder unless --force is passed.

repowire schedule

repowire schedule self WHEN_OR_CRON TEXT [--cron]
repowire schedule create TO_PEER WHEN_OR_CRON TEXT --from-peer FROM_PEER [--cron]
repowire schedule list
repowire schedule delete SCHEDULE_ID

Create one-shot or recurring scheduled mesh messages. Without --cron, the time may be ISO-8601 or relative, such as 10m, 1h, or in 30s. With --cron, use five-field cron syntax or aliases such as @hourly, @daily, @midnight, @weekly, and @monthly. Add --kind ask when the scheduled delivery should open an ask thread.

repowire telegram start

repowire telegram start

Run the Telegram bot peer. Reads TELEGRAM_BOT_TOKEN and TELEGRAM_CHAT_ID from the environment. The bot registers as the telegram peer; messages from it are framed as human input.

repowire slack start

repowire slack start

Run the Slack bot peer over Socket Mode (no public URL needed). Reads SLACK_BOT_TOKEN, SLACK_APP_TOKEN, and SLACK_CHANNEL_ID.

repowire update

repowire update

Re-install repowire via the same package manager that installed it. Use after pulling a new release.

repowire uninstall

repowire uninstall [--yes]

Remove hooks, MCP entries, and the daemon service. Prompts before deleting ~/.repowire/ (config, logs, attachments); decline to keep it for reinstalls. --yes skips the prompts and removes the directory along with the installed package.