Waterbrother is being built as a local coding runtime that can extend into messaging, model providers, MCP tools, and remote-control gateways without losing deterministic local control.
The integration model is explicit: terminal first, provider-flexible runtime underneath, and channel adapters on top. Messaging is DM-first before collaboration.
Waterbrother is following the practical order that keeps remote control sane: one user first, then observation, then approvals, then collaboration. The messaging layer is explicit about what is live, what is staged, and what still needs a bridge.
The first real messaging surface for Waterbrother: paired bot control, live TUI bridging, shared-room commands, task flow, and group execution gating.
Discord now has a live gateway, native slash commands, guild and DM control, room state, tasks, role routing, and verification workflow controls.
See Discord integration
Signal stays in scope, but it comes after the lighter bot APIs because it needs a stricter local bridge path.
See Signal setup
WhatsApp is planned as another messaging surface once the Telegram room model is proven in real-world testing.
No setup yetSingle-user remote control, live TUI bridge, shared-room commands, and group execution gating.
DMs, guild channels, native slash commands, room control, tasks, role routing, and verifier workflow are live now.
Onboarding and config exist now; live bridge follows after lighter bot APIs.
Planned on the same messaging-room model once Telegram proves the collaboration surface.
Bring-your-own-model runtime across OpenAI, Anthropic, OpenRouter, Ollama, xAI, and compatible APIs.
Project-level MCP servers, tool discovery, and structured local workflow extension.
Runtime profiles, provider switching, and session persistence are the base layer that make messaging and remote control viable instead of one-provider hacks.
waterbrother config set-json channels '{"telegram":{"enabled":true,"botToken":"YOUR_BOT_TOKEN","pairingMode":"manual","allowedUserIds":[]}}' --scope user
waterbrother config set-json gateway '{"enabled":true,"controlMode":"single-user","startupChannels":["telegram"]}' --scope user
waterbrother gateway status
waterbrother gateway run telegram
waterbrother gateway pairings
waterbrother gateway pair telegram 123456789
Unknown Telegram DMs create a pending pairing request. Approve locally with
waterbrother gateway pair telegram <user-id>, then the linked remote session is available. Pending requests expire automatically after 12 hours if ignored.
If the TUI is open, Telegram prompts route into that live terminal session and the paired Telegram user operates with the same permissions as the terminal operator. Otherwise Waterbrother falls back to the remote session runner.
Interactive slash commands, durable sessions, exact shell routing, approvals, and checkpointed local work stay the source of truth.
MCP is part of the integration story too: structured tool extension instead of pushing every problem through raw shell commands.
waterbrother ps, up, down, and restart now manage the live Telegram and Discord surfaces like services, while the TUI stays the source of truth.
Build failures, user corrections, and scorecards can feed future work through regressions, correction learning, and /evolve proposals instead of vanishing into terminal history.
Streaming dictation, dual-model correction, and xAI speech output let Waterbrother operate as more than a text-only shell assistant.
Provider-aware errors, auto-retry, doom-loop detection, and context overflow recovery are part of the runtime underneath Telegram, Discord, and the terminal.
Signal bridge work, richer remote approvals, and deeper shared-project collaboration once the current multi-surface room model is proven.
Shared projects now have a dedicated collaboration model with room state, room modes, and a single active operator lock. Start with the Roundtable page before rolling shared Telegram rooms out to a team.