Install from npm, launch once, and the first-run terminal wizard handles provider, API key when required, model, and profile setup. After that, use runtime status and runtime profiles to switch cleanly without redoing setup.
Auto Wizard
What happens on first launch
CLI asks which provider you want to use.
If that provider needs a key, it asks for the API key.
CLI tries to fetch live models for that provider, tells you when it is using the live list, and falls back to the built-in catalog if the provider list is unavailable.
CLI asks for your default model and agent profile.
CLI can optionally configure Telegram, offer to open the Telegram guide if you still need a bot token, and enable TUI gateway autostart.
Settings are saved to ~/.waterbrother/config.json (including trace + auto-compact defaults).
Choose a provider such as OpenAI, Anthropic, OpenRouter, Ollama, or SpaceXAI.
Create an API key if that provider requires one.
Set provider and key locally:
waterbrother config set provider openai
waterbrother config set apiKey YOUR_PROVIDER_API_KEY
Verify
Environment checks
After onboarding, you can still inspect the provider's live model list directly.
waterbrother doctor
waterbrother models status
waterbrother models list
waterbrother models catalog
waterbrother mcp list
Discord
Set up WATERBROTHER for Discord
If you are new to Discord, start with the dedicated Discord onboarding guide. It covers
creating a bot, enabling Message Content intent, saving your bot token safely via env vars,
and inviting the bot with the minimum useful permissions.
waterbrother runtime-profiles save review-anthropic
waterbrother runtime-profiles list
waterbrother runtime-profiles apply review-anthropic
Messaging
Prepare remote-control channels
The first-run wizard can offer Telegram setup directly. You can still use service-specific onboarding for Telegram, Discord, and Signal later.
waterbrother onboarding telegram
waterbrother onboarding discord
waterbrother onboarding signal
waterbrother channels status
waterbrother gateway status
MCP
Project-local tool servers
Partners can attach repo-local MCP stdio servers through project config.
waterbrother config set-json mcpServers '{"filesystem":{"command":"npx","args":["-y","@modelcontextprotocol/server-filesystem","."]}}' --scope project
waterbrother mcp list
Project Memory
Create source-of-truth file
WATERBROTHER can load WATERBROTHER.md from your project root into the system prompt.
This is useful for stable instructions and project constraints.
# inside interactive mode
/memory init
/memory add Always run tests before final answer.
/memory reload
