Hermes agents may forget their workflow in a new session
use suggests a can work well on the first run but become unreliable in a later session. Even when one agent has one clear job, detailed instructions, and agreed steps for how the work should be done, the next-day result can change sharply. Hermes may create .md that describe the , but a new session may act as if it did not check those files or the memory.
The agent may stop following the earlier method and choose its own path instead. The setup uses for memory, so the problem may not simply be memory being overwritten.
Key points
- A can perform well once, then produce very different results in a new session.
- Created .md may not be used automatically on the next run.
- Using memory does not guarantee that the earlier will carry over.
- For repeat tasks, tell Hermes at the start to check memory and the first.