Telegram Agent Interface

Messaging is the interface, and it comes last. Telegram turns the Agent OS into something you drive from your pocket — but the gateway means running Hermes on a VPS (production = cost), so this branch only opens after the local architecture, actors, skills, and orchestration are proven on the CLI/TUI.

Local-first, Telegram when there's a VPS. A bot that holds write tools — that can apply for jobs, send messages, or touch money — is a serious attack surface. Pairing, allowlists, and per-chat session isolation are not optional; draft/approval stays on.

Planned notes

• Telegram as a control plane (not a chatbot)
• The gateway: bringing Hermes online for messaging
• BotFather and bot setup
• Pairing and the allowlist
• Per-chat sessions and isolation
• Delivery and file handling
• Busy modes and token locks
• Securing a bot that holds dangerous tools
• Roadmap: local-first now, Telegram when there's a VPS
• The 20+ messaging platforms beyond Telegram

Core sources

• Hermes — Messaging — https://hermes-agent.nousresearch.com/docs/user-guide/messaging/
• Hermes — Gateway Internals — https://hermes-agent.nousresearch.com/docs/developer-guide/gateway-internals
• Hermes — Security (bot attack surface) — https://hermes-agent.nousresearch.com/docs/user-guide/security

Connects to: Agent Security & Ops · Hermes Architecture · Schedulers & Automation · Native Orchestration