Hermes agent telegram threads come in four flavours, threaded DMs, declared DM topics, the /topic multi-session mode and supergroup forum topics, and picking the right one decides how your sessions split, who creates topics and how much config you maintain.
This guide sets the four side by side, shows how to switch each one on, and lists the mistakes that make topics look broken.
Everything is drawn from the Hermes Telegram page, the sessions documentation and the GitHub release notes. Want a second opinion on your setup? Get your Backlink Gameplan, or try Polar Rank free for 3 days.
What All Four Options Have In Common
Every option relies on one rule: Hermes puts the Telegram thread ID into the session key.
Two messages with different thread IDs land in different sessions, each with its own history and context window.
What changes between the options is where the topics live, who makes them and whether you write any config.
That also means a reset is local. Typing /new inside one topic starts that topic over and leaves every other topic exactly where it was.
None of them gives a topic its own memory, skills or bot. Those belong to the profile, and every topic in a profile shares them.
The Four Options Compared
| Option | What it does | What it needs | Best for |
|---|---|---|---|
| Threaded DMs (dm_threads) | Each Telegram DM thread becomes its own session, or one shared session if you choose | Threaded Mode in BotFather | People whose client already opens threads |
| Declared DM topics (dm_topics) | Hermes creates a fixed list of topics and can bind a skill to each | Threaded Mode plus a config.yaml block | Permanent lanes you use daily |
| Multi-session DM (/topic) | Users create unlimited topics, each a fresh session, and can restore older sessions | Threaded Mode with user topic creation left on | Solo users juggling parallel jobs |
| Forum topics (group_topics) | Each supergroup topic is a shared session, with optional skills and filters | A supergroup with Topics mode and the bot added | Teams sharing one agent |
Two of these can run together on one bot. The docs say /topic and dm_topics coexist, with dm_topics managing operator-declared topics for other chats.
Option 1: Threaded DMs
Turn on Threaded Mode and Telegram starts attaching a thread ID to ordinary DM messages.
Hermes then keeps a session per thread. That default is called per_thread.
It suits you if your Telegram client opens a new thread for each question and you like that.
It doesn't suit you if the DM keeps fragmenting into sessions you never meant to start. The fix is platforms.telegram.extra.dm_threads: shared, which v0.23.2 introduced as opt-in.
Verdict for this option: leave the default unless the splitting annoys you.
Option 2: Declared DM Topics
Here the operator writes the topic list into config.yaml under platforms.telegram.extra.dm_topics, with your user ID as chat_id.
Each topic takes a name, optional icon fields and an optional skill that loads at the start of every new session in that topic.
Hermes creates the topics on startup and stores each thread_id back in the file.
The upside is predictability: the same lanes every day, never renamed, each primed with the right skill.
The downside is that changing the list means editing YAML.
Picture a small online shop with three lanes: Orders, Product Copy and Supplier Mail. Product Copy carries a skill holding the shop's tone of voice.
🔥 Want to see how other operators lay out their Hermes topics? Join the AI Profit Boardroom for video lessons on each Hermes feature, a downloadable Agent OS, live coaching four times a week and 3,400+ members comparing setups. → Join the AI Profit Boardroom
Option 3: The /topic Multi-Session Mode
This is the user-driven option. No config: send /topic in the root DM and the mode switches on.
Hermes first verifies the BotFather flags through getMe. If they're off, it sends a screenshot of the right settings page instead of activating.
After that, the root DM is a lobby, and every new topic you create from All Messages is an independent session that Hermes auto-names after the first exchange.
It also lets you pull an older Telegram session into a topic with /topic plus the session ID, which is handy for conversations that predate topic mode.
It suits a developer running five unrelated tasks at once. It suits a team less, because it lives in one person's DM.
Since v0.23.0, dm_topic_auto_transfer can also turn any message typed in the lobby into a brand-new topic.
Option 4: Forum Topics In A Supergroup
Supergroups with Topics mode already isolate sessions per topic with no config at all.
By default everyone in a topic shares the session; thread_sessions_per_user: true splits it per person.
Add group_topics only when you want skills bound to topics. Unlike DM topics, you type the thread_id yourself, taken from the topic's t.me/c link.
This is the only option with a full set of filters: allowed_topics, ignored_threads and free_response_topics.
Take a four-person agency with topics for Leads, Content and Reporting. Content gets a writing skill, Reporting receives a weekly cron post, and the staff Banter topic sits on the ignore list.
It suits any team that wants one agent across several workstreams.
How To Switch Each One On, Quickly
All four start from a bot that already replies in a plain DM. After that, the steps are short.
- Threaded DMs: open the BotFather Mini App, go to My bots, your bot, Bot Settings, Threads Settings, and switch Threaded Mode on. Add the dm_threads key only if you want one shared session.
- Declared DM topics: do the same BotFather step, add a dm_topics block with your user ID and topic names to config.yaml, then restart the gateway so Hermes creates the topics.
- /topic mode: do the BotFather step, keep user topic creation allowed, then send /topic in the bot DM. Hermes replies with any older sessions you can restore.
- Forum topics: create a supergroup, turn on Topics in its settings, add the bot, and allow the group in Hermes. Add group_topics and filters afterwards.
For groups, check privacy mode too. The Telegram page explains that the bot must be able to see group messages, so turn off BotFather privacy mode, make the bot an admin, or mention it.
After changing privacy, remove the bot from the group and add it again, because Telegram can keep the old delivery behaviour for existing members.
Then send one test message in each topic and watch the gateway log. A filtered topic shows a single INFO line the first time it drops a message, which is a quick way to confirm your whitelist works.
Which One Should You Pick?
- You work alone and run many jobs at once: /topic.
- You work alone with fixed jobs: dm_topics, with a skill per lane.
- Your DM keeps splitting: threaded DMs with dm_threads set to shared.
- You have staff: a forum supergroup, with allowed_topics as a fence.
- You need separate memory or logins per lane: none of the above. You need a second profile.
Topics Versus A Second Profile
This is the decision people get wrong most often.
A topic separates a conversation. A profile separates the agent: its memory, skills, persona, credentials and bot token.
The FAQ says profiles can't share one bot token, so each extra profile means a new BotFather bot and its own gateway.
For a group with several Hermes bots, the Telegram docs recommend require_mention and exclusive_bot_mentions both on, so a message addressed to one bot reaches only that bot.
A multiplexed gateway with gateway.profile_routes is the advanced alternative; its routes can match a chat and a thread. The multi-profile guide explains the scoring.
📞 Topics or profiles for your team? Get your Backlink Gameplan and we'll weigh the options against how your people actually work, or try Polar Rank free for 3 days. Backlink Gameplan or try Polar Rank free for 3 days
Common Mistakes That Make Topics Look Broken
- Looking for Threaded Mode in /mybots. It is only in the BotFather Mini App, under Bot Settings and Threads Settings.
- Typing thread_id into dm_topics. Hermes fills it in. Setting it by hand is only for group_topics.
- Forgetting General is topic 1. If allowed_topics leaves out 1, the General topic goes quiet.
- Expecting a whitelist to filter DMs. allowed_topics never touches DMs.
- Reusing a bot token across profiles. Telegram rejects concurrent polling for the same token.
- Allowing the user but not the group. In groups, the sender must be on TELEGRAM_ALLOWED_USERS or TELEGRAM_GROUP_ALLOWED_USERS, or the whole chat must be on TELEGRAM_GROUP_ALLOWED_CHATS. Group IDs are negative numbers, and that is normal.
- Reading unread badges as a fault. The docs call mismatched read markers in DM topics a Telegram limitation.
What Topics Cannot Do Today
Several popular requests are still open issues on GitHub, not features.
- A model or provider per topic in config (issue 57664).
- A bound working directory and persistent brief per forum topic (issue 61136).
- A topic wired to an external runtime such as Codex or Gemini CLI (issue 5394).
- Per-topic enabled_toolsets in group_topics, which is parsed but not enforced (issue 37743).
The working substitute is /model inside a topic: a plain switch is session-only, so it stays in that topic.
Extras That Make Topics More Useful
Cron jobs can deliver into a specific topic using a chat ID and thread ID target, per the cron docs.
/branch on Telegram opens a branch in a sibling thread, so you can explore an alternative without touching the original.
Two community plugins in the Hermes plugin catalog are topic-aware: walkie-talkie lets one session message another existing session such as a Telegram topic, and hermes-wake wakes the topic that started background work when it finishes. Both are community plugins, not Nous Research releases.
Still on the basics? Our Hermes Agent Telegram review covers connecting the bot in the first place.
My Verdict
For most solo users, /topic is the right default: one command and unlimited clean sessions.
For teams, forum topics win because they're shared and they're the only option with proper filters.
Declared DM topics are the best fit when a lane needs a skill loaded every time.
If you want these patterns explained on video, the AI Profit Boardroom walks through Hermes gateways and profiles step by step.
FAQ: Hermes Agent Telegram Threads
Which Hermes Telegram topic mode is easiest?
/topic. It needs no config: send the command in your bot DM and create topics from All Messages.
Can I use /topic and dm_topics on the same bot?
Yes. The docs say both features can coexist on one bot.
Do group topics need any config to keep sessions apart?
No. Forum topics are isolated per topic by default. group_topics is only for binding skills.
Why did my General topic stop answering?
If you set allowed_topics, the General topic counts as topic 1, so it must be on the list.
When should I use a second profile instead of a topic?
When a lane needs its own memory, skills, persona or credentials. Each profile needs its own bot token.
Is a per-topic model setting available?
Not in config yet; it is an open GitHub issue. Running /model inside a topic changes only that topic's session.
📺 Video notes + links to the tools 👉
🎥 Learn how I make these videos 👉
🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉
About Julian
I'm Julian Goldie, an SEO entrepreneur, author and founder of the AI Profit Boardroom, which has 3,400+ members.
I help business owners scale with AI agents, automation and SEO.
- I've built a 7-figure SEO and link building agency, Goldie Agency, with a team of 70+ SEO experts.
- I've grown a YouTube channel to 400,000+ subscribers.
- I wrote "Link Building Mastery".
- My Udemy courses have taught over 29,000 students.
→ Get my best AI training inside the AI Profit Boardroom
Pick the option that matches who creates the topics and who reads them, fence groups with allowed_topics, and if you want a hand choosing, get your Backlink Gameplan, try Polar Rank free for 3 days, or join the AI Profit Boardroom to get the most from hermes agent telegram threads.











