Memory mechanism is broken?

[susyabashti]

There's this weird thing that happens when i leave the chat session in the web ui for a while and return. The agent like restarts itself reading from memory and is completely off topic focusing only on whats been recalled from memory though outdated stuff and so even my message is completely ignored sometimes.

The worst thing is that this happens also mid session. And this is the worst because you lose all the progress you've done with the agent. One moment he performs everything you asked him to do and give a great audit or report. Then you want to act on it and it suddenly reads from memory and and does his initial session reads.

Don't know if this is me if i did something wrong. Im still iterating on this though i might disable memory for good.

[Audacity88]

@susyabashti thanks for reporting this. This does not sound like expected behavior, and it does not sound like a setup mistake.

If the web UI reconnects after idle time, memory recall should only be supporting context. It should not replace the active user message, restart the session, or push the agent back into its initial memory-reading path mid-session.

This sounds closest to a gateway/web session + memory recall bug. It may be related to the resumed-session work in #6932, but the “current message gets ignored after memory recall” part is a separate enough symptom that I’d like to track it directly if we can reproduce it.

Could you add a few details?

• ZeroClaw version or commit SHA
• model/provider
• memory backend/config, especially whether memory is enabled per-agent or install-wide
• whether this happens after browser refresh, tab idle/reconnect, or with no visible reconnect
• whether disabling memory stops the behavior
• any gateway/runtime logs around the turn where it jumps back into memory reads

If you can reproduce it again, please also copy the last normal user message and the first bad assistant response. Redacted is fine. That should be enough to turn this into a focused bug.

[Audacity88]

@susyabashti I saw #8837 as well. These may be the same underlying issue, but I do not want to assume that yet.

If the behavior in this discussion is caused by the same context/history trimming path described in #8837, let’s continue the investigation there so the config, logs, and repro details stay in one place.

If this discussion turns out to be separate — for example, memory recall is taking over even when no context trim happened — then let’s keep that separate thread here and track it as its own memory-recall bug once we have the details.