Hermes Telegram multi-bot profile isolation
A distilled note from a public Korean field report on operating multiple Telegram bots with Hermes.
Source
Hermes Telegram 디폴트 봇 1개에서 2개로 추가 할때 겪는 삽질기, posted on GPTers.
The source is a hands-on account of trying to add a second Telegram bot to Hermes and discovering that the stable solution is not simply adding another token to the default setup.
Key takeaways
Multi-bot operation is profile isolation
A second Telegram bot should be treated as a separate Hermes profile with its own configuration, secrets, memory, sessions, skills, and gateway process.
User IDs and bot tokens are different objects
Telegram user IDs are numeric identifiers, while bot tokens follow a number:string structure. Mixing them up leads to confusing gateway failures.
Gateway lifecycle should be per profile
Each bot should be started, restarted, inspected, and debugged in the context of its own profile so one bot does not accidentally inherit another bot’s role or memory.
Operating pattern
The practical pattern is to create a named Hermes profile for each Telegram bot, place profile-specific secrets in that profile’s environment, and operate its gateway independently.
~/.hermes/profiles/<bot-profile>/
.env
config.yaml
memory/
sessions/
skills/This keeps role, memory, skills, and delivery behavior separate. It also fits Hermes’ broader model of independent profiles for independent agents.
Why this matters for Teo Wiki
Teo Wiki is intended to grow as a public-facing knowledge surface backed by agent-maintained notes. Multi-profile Hermes operation is relevant because it suggests a scalable way to split agents by role: one agent can handle personal website maintenance, another can handle bus/shuttle tracking, and another can manage periodic briefings.