how to fix Hermes memory

[lean fox]

第一张图是它在凌晨在干的活。

然后我醒了，接着继续上次的回复，我问它改了什么，结果它一通乱回答。

后来我加了 discord 消息引用，它还是回答错误。

然后我再问它有什么能改进的吗，它也不能改进。

然后我又尝试让它读最近 10 条消息，结果它没有按当前子区的消息去读。读了别的区的消息。

最后我告诉他，读取当前子区最近的 10 条消息，他才真正找到了正确答案。

[tidal viper]

The first picture is what it was doing in the early morning.

Then I woke up and continued the last reply. I asked it what it had changed, but it gave random answers.

Later I added the discord message reference and it still answered incorrectly.

Then I asked if there was anything it could improve, and it couldn't.

Then I tried to let it read the last 10 messages, but it did not read the messages in the current subarea. I read news from other districts.

Finally I told him that he really found the correct answer by reading the 10 most recent messages in the current subarea.

[lean fox]

Use Never auto-reset (context lives until /reset or context compression) during hermes setup

[native remnant]

这条补充有帮助。Never auto-reset 可能会让旧上下文保留更久，所以它可能会放大“沿着旧任务继续乱答”的问题。

不过从截图看，核心问题不只是普通 memory 设置。更关键的是：它在当前 Discord thread 里回答时，似乎没有优先读取当前 thread 的最近消息，而是去用了最近 session / 其他任务上下文，所以才会把工作区和改动内容说到别的任务上。

请先不要删除记忆或重装。下一次它在 Discord 里答偏之后，请立刻发调试信息：

/debug

或者在服务器终端运行：

hermes debug share

请把 Report、agent.log、gateway.log 都发出来。这个问题需要 gateway.log，因为我们要看 Discord gateway 当时有没有拿到当前 thread 的消息、引用消息、channel/thread id，以及实际传给 agent 的上下文。

也请一起补充：

你当前这个 Discord channel / thread 名字
你发给 bot 的原始问题
你期望它根据哪几条消息回答
它实际答错的那条回复
Hermes 版本
provider / model
你在 setup 里选择的 context / auto-reset 设置

现在最像的方向是：旧 session/context 没有被重置，加上 Discord 当前 thread 消息没有被正确优先使用。日志能告诉我们到底是 gateway 没取到当前 thread，还是 agent 取到了但 session search / memory / 模型工具选择把它带偏了。

[tidal viper]

This supplement helps. Never auto-reset may keep the old context around longer, so it may amplify the "keep messing along old tasks" problem.

But judging from the screenshots, the core problem is not just ordinary memory settings. More importantly: when answering in the current Discord thread, it seems that it does not give priority to reading the latest messages of the current thread, but uses the recent session/other task context, so it transfers the workspace and changes to other tasks.

Please do not delete the memory or reinstall it yet. Next time it gives a wrong answer in Discord, please send a debugging message immediately:

/debug

Or run in the server terminal:

hermes debug share

Please send the Report, agent.log, and gateway.log. This question requires gateway.log, because we need to see whether the Discord gateway got the current thread's messages, reference messages, channel/thread id, and the context actually passed to the agent.

Please also add:

Your current Discord channel / thread name
Original question you sent to the bot
Which messages do you expect it to answer based on?
The reply it actually answered incorrectly
Hermes version
provider/model
The context / auto-reset settings you selected in setup

The most likely direction now is that the old session/context has not been reset, and the current Discord thread messages have not been correctly prioritized. The log can tell us whether the gateway did not obtain the current thread, or the agent obtained it but the session search / memory / model tool selection led it astray.

[lean fox]

sorry，我已经按 teknium 的建议禁用了 auto reset. 目前看起来良好

[tidal viper]

Sorry, I have disabled auto reset as suggested by teknium. It seems fine so far.

[native remnant]

很好，那先按这个状态继续用。

既然禁用 auto reset 后目前看起来正常，我先把这个 thread 当作已解决处理。之后如果又出现 Discord 里读取错 thread、继续旧上下文、或者回答和当前消息不匹配的情况，直接在这里补充新的现象和 /debug / hermes debug share 日志，我们再继续看。