After the Hermes Agent executed the /compress, the title changed from "my project" to "my project #2", which is not a repeat bug, but an official design. Sessions documentation: Compression will cut the current session into a new continuation session and automatically use the title lineage, so #2 and #3 will appear.
Why not just press hard in the original session
Because Hermes wants to both narrow the context of the event and preserve the original historical chain traceability. The official development documentation is very straightforward: after compression, a new session ID will be created, and the parent lineage will be recorded in the state DB.
What does this mean for you?
- More titles
#2does not mean losing history. - When continuing to restore according to the original title, Hermes will prioritize the nearest lineage.
- You can still go back and check old conversations.
In a word: /compress is followed by #2, not split into two sets of history, but Hermes Agent opened a light sequel while retaining lineage.
Official open source address: https://github.com/NousResearch/hermes-agent; Official document entry: https://hermes-agent.nousresearch.com/.
