Using Telegram as a Hermes Agent Session Manager
I like one design of Hermes-agent.
During the installation and setup process, a telegram bot is bound, so I can chat with this bot directly no matter where I am.
DM-ing the bot directly, or finding the bot to chat in different groups — these are all different sessions, and the contexts won't pollute each other.
What I commonly use is, open a group, enable the topic feature, then open different topics to chat with the bot for different subjects, and the contexts won't pollute each other.
Does it look a bit like the effect of switching between different sessions on a webui? Compared with webui, telegram solves the network setup and operation for remote connection
Note that with this usage, the agent is still the same one, so after the session is summarized into memory, the memory is shared.
If you're worried that the stuff saved in memory is too messy and affects the usage effect, then you need to isolate at the agent level.
My usage has some common scenarios,
For example, if you always ask TA about various trivial matters in life, the merging of memory is actually a good thing — the agent's understanding of you becomes richer and richer.
And if you're the kind of person who may come up with many different ideas in a short period of time, then splitting into different sessions can avoid context pollution.
For example, you have a big-picture thing to do — say, starting a company.
You need to discuss many different topics, and it's ongoing discussion, not just one or two rounds of conversation. Company naming, tax incentives in different cities, office location registration, financial compliance, corporate email, which server provider to buy from, ...
Posts
