Every Hermes Agent tip from witcheer at Nous Research, in his own words. Collected in one place and updated daily.
witcheer says each tip ran on a real Hermes box before it shipped. Hermes changes fast, so check your version and the linked doc.
Latest tip #113 · switch projects from the chat · Oct 29, 2026
by default, when your Hermes Agent's gateway starts, it skips the Telegram messages that arrived while it was off.
if your agent runs on a computer that sleeps or shuts down at night, set this once:
hermes config set platforms.telegram.extra.drop_pending_on_cold_boot false
on the next start, those messages come in, in order.
your Hermes Agent can send you files on Telegram, not only text.
want something you can read later on your phone, or forward to someone?
ask for the format in your message:
"send me that as a PDF"
Hermes makes the file and it arrives in the chat as an attachment.
it works for a chart too, which comes through as an image, or a table as a spreadsheet!
want it every time? add a line to your ~/.hermes/SOUL.md asking for files over long text replies in chat.
docs: https://hermes-agent.nousresearch.com/docs/user-guide/features/deliverable-mode
you are mid-conversation with your Hermes Agent in the terminal and you have to leave your desk.
type this in the chat:
/handoff telegram
the session moves to your Telegram home channel with its full history, and the agent replies there with a short summary of where you left off. you carry on from your phone.
useful when you head out mid-project, or when a chat you started at your desk needs finishing on the train!
docs: https://hermes-agent.nousresearch.com/docs/user-guide/sessions#cross-platform-handoff
one command sends a message from any script to the platforms your Hermes Agent is already set up on.
it uses your gateway's bot credentials and makes no model call.
hermes send --to telegram "deploy finished"
or pipe anything into it:
tail -n 20 build.log | hermes send --to telegram
useful in cron scripts, CI jobs, or as a ping when a long training run is done!
docs: https://hermes-agent.nousresearch.com/docs/guides/pipe-script-output
your agent reads your messages through Telegram or Discord, but it does not see when you sent them.
message_timestamps under gateway in config.yaml changes that.
with enabled: true, every message you send carries its send time in front, for the model only. the chat you read does not change and the transcripts on disk stay clean. the agent can tell this morning from last week, notice a long gap, and answer with the right day in mind.
your messages only. the agent's replies and the system prompt are untouched.
gateway:
message_timestamps:
enabled: true
or from the terminal: hermes config set gateway.message_timestamps.enabled true
docs: https://hermes-agent.nousresearch.com/docs/user-guide/messaging#message-timestamps-in-model-context
Hermes Wingtips #43: Telegram topics or a second agent?
running several projects through one Telegram bot? there are two ways to split them, and they are not the same thing.
(1) /topic
parallel conversations inside one bot DM. still one agent behind them, so what it learns on one project helps the others.
(2) hermes profile create \<name\>
a second agent entirely, with its own bot.
pick topics when your projects should feed one brain, profiles when you need real walls between them. and both can run on the same machine!
Hermes Wingtips #1
running a hermes agent in a telegram group and it just sits there silent? the usual cause is BotFather's group privacy mode: it's on by default, so the bot only sees messages that mention it or start with /.
plain group messages never reach it.
easy fix: message BotFather, /setprivacy, pick the bot, Disable.
it doesn't apply to groups the bot is already in. remove it from the group and re-add it for the change to take.
All tips are written by witcheer and collected here with credit. Card images stay on his X posts.
May we use Google Analytics to measure visits and newsletter signups? It uses cookies. Declining will not affect the site. Privacy details