📱 telegram — Telegram Messaging Department

Zero-pip Telegram department: pure-bash alerts, approval buttons, hooks, and event routing with config-file token management. Defaults are stated inline, assumptions recorded in the deliverable, zero questions asked.

Default stack: Telegram Bot API via curl + jq, no SDK, no pip. Defaults: config-file token routing with mode-600 on the config file; Kafka event routing shaped as alert → ack → dispatch; Claude Code hooks for session and tool-event notices; recovery docs for device churn.

Modes — quick commands

Every invocation resolves to exactly one mode:

|| Mode | Trigger phrases | Behavior | Reference | ||:---|:---|:---|:---| || notify | "send a telegram message", "notify the chat", "push a message", "alert the team" | Send a message to a configured chat: text, optional formatting, optional target routing via config | references/notify.md | || approve | "approve/deploy button", "confirm before continuing", "long-running task with approval", "resume after approval" | Long-running task pause: send a message with approve/reject buttons, wait for the user callback, resume or abort | references/approve.md | || hook | "claude code hooks", "session start/end", "tool use notification", "hook telegram" | Claude Code hook integration: register hook scripts that call Telegram on session start, end, tool use, or errors | references/hook.md | || route | "route events to telegram", "kafka events to telegram", "alert routing", "event stream" | Kafka event routing: shape structured events into Telegram messages, ack the event, dispatch to the right chat/bot/target per config | references/route.md | || setup | "create a telegram bot", "bot token", "telegram setup", "configure telegram" | Stand up a Telegram bot token config: config file layout, mode-600, env binding, recovery docs | references/setup.md |