Waterbrother

Messaging Channels

Waterbrother is adding gateway-first messaging support. Telegram is now the first live single-user adapter; Discord and Signal remain in guided-foundation mode until their live bridges land. For the wider surface across models, MCP, messaging, and terminal control, start with the integrations overview.

Telegram

First remote-control target

DM-first bot control with explicit pairing, deterministic routing, typing indicators, and cleaner rendered replies.

Open Telegram guide

Discord

DMs before channels

Use a bot token and application id, start with direct messages, then add policy later.

Open Discord guide

Signal

Private but heavier

Signal uses a local signal-cli bridge and should be treated as a controlled adapter.

Open Signal guide

CLI 
waterbrother channels list
waterbrother channels status
waterbrother channels show telegram
waterbrother gateway status
waterbrother gateway pairings
waterbrother gateway pair telegram 123456789
waterbrother gateway run telegram
waterbrother onboarding telegram
Rollout Order
  1. Single-user remote control of one Waterbrother terminal.
  2. Status and observation from linked channels.
  3. Approval flows over messaging.
  4. Only then group DM collaboration.
Telegram v1 Limits
  • Unknown Telegram DMs create pending pairing requests you approve locally with waterbrother gateway pair telegram <user-id>.
  • Pending Telegram pairings expire automatically after 12 hours unless approved.
  • Remote prompts run with approval=never.
  • Status, runtime inspection, and read-oriented prompts work best today.
  • Mutating and approval-heavy work stay local until remote approvals land.