Hermes Agent sends the results to Telegram, Discord, or other home channels, but the main session cannot continue chatting, which is not a misconfiguration. The official cron documentation currently clearly states: "The agent cannot see this message, and therefore cannot respond to it." This means that the results of the scheduled task will be sent to a human, but will not be automatically written back to the current chat context.
So what to do now
- Write the cron output to a fixed file and let the main session read the file.
- Let cron only "generate results" and don't expect it to automatically continue the conversation.
- If the user needs to continue asking, explicitly ask the Hermes Agent to read the report or directory you just mentioned.
Why is this happening?
As of April 12, 2026, there are still relevant feature requests discussing this in the official repository, indicating that this is more like the current product boundary than just a bug. In other words, cron is more like a "background broadcast" rather than "automatically injecting results into the main session".
This question is most likely to be misjudged as a broken gateway. In fact, the gateway only delivers the results by design. The real solution is "how to return the result to the conversationable context", and the most practical solution is still file handoff, memory recording, or the user actively letting the main session read the result.
Official open source address: https://github.com/NousResearch/hermes-agent; Official document entry: https://hermes-agent.nousresearch.com/.
