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] [--non-interactive]One-time install. Detects every agent runtime present (Claude Code, Codex, Gemini CLI, OpenCode, Pi), wires lifecycle hooks and the MCP server for each, and installs the daemon as a user service. --relay opts in to the hosted relay at repowire.io. --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 build-ui
repowire build-uiBuild the Next.js dashboard into the static export served by the daemon at /dashboard. Run after editing files under web/.
repowire telegram start
repowire telegram startRun 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 startRun 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 updateRe-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.
Configuration lives in ~/.repowire/config.yaml. The MCP tools reference covers what agents call once the daemon is running.