Hermes Agent gets stuck for a while every time a new session is opened, and this question has been asked a lot in the community recently. While not all of them are caused by Honcho, the official Honcho documentation already states that the default is hybrid mode, which means that local memories run with Honcho. As long as Honcho participates in initialization, there is an additional layer of external memory flow than a pure local path.
How to tell if it's it
- First, check if you have configured Honcho's API key or base URL.
- If it's just a local test, temporarily turn off Honcho to see if the speed of the new session is significantly restored.
- Or change the memory mode to a more local mode instead of the default hybrid.
When should you not rush to close?
If you rely on cross-machine, cross-platform, and long-term user profiles, the value of Honcho exists. It's just that when your current pain point is "opening a game is too slow", doing an A/B investigation first is the most time-saving.
In a word: the new session is slow, first check whether Honcho is dragging initialization; Don't doubt the Hermes Agent main loop at the first moment.
Official open source address: https://github.com/NousResearch/hermes-agent; Official document entry: https://hermes-agent.nousresearch.com/.
