Hermes Agent cannot see the chat history on the Open WebUI side in the CLI, usually not because the database is broken, but because different entrances are inherently different sessions. The official Sessions documentation makes it clear that each conversation is saved separately by source platform, user, and session rules; This is also a high-frequency question that has been asked repeatedly in the community recently.
What does this mean?
- Open WebUI initiates its own API session.
- In the CLI,
/historyonly looks at the current CLI session and does not automatically cross over to the Open WebUI side. - The same goes for Telegram, Slack, and Discord, each with its own session track.
What should I do if I want to continue chatting across ends?
The safest approach is not to force a "unified chat box", but to write key context into a file, memorize or pinned note, and then let the new entry read it. If you are connecting the API yourself, you should use a /v1/responses session chain for multiple consecutive conversations, rather than expecting the CLI to automatically connect to the context of Open WebUI.
In a word: Hermes Agent does not share a chat shell for all portals, and by default it is an independent session with an isolated entrance.
Official open source address: https://github.com/NousResearch/hermes-agent; Official document entry: https://hermes-agent.nousresearch.com/.
