Telegram Topics Pipeline

Wire Telegram's forum topics into your agent infrastructure so each topic is its own isolated agent session with dedicated context, skills, and cron pipeline. No context bleed. No accidental cross-posting. One group, N independent workflows.

This is the single highest-impact operational change you can make to how your agent runs. A flat DM or group chat forces every topic into the same context window. Topics fix that.

How It Works

Telegram forum topics (supergroups with Topics mode) each carry a unique message_thread_id. Hermes (and OpenClaw) use the pair (chat_id, thread_id) as a session key:

agent:main:telegram:dm:{chat_id}:{thread_id}     # DM topics
agent:main:telegram:group:{chat_id}:{thread_id}   # Group forum topics

Messages in Topic A never appear in Topic B's session history. They are independent conversations with their own scrollback, memory, and active context.