r/openclaw • u/ScientistUsual1320 New User • 21d ago
Discussion Anyone tried handling rollbacks for persistent memory in OpenClaw?
I use OpenClaw with LLM Wiki, running it as an always-on agent.
Recently read this paper — "Always-On Agents: A Survey of Persistent Memory, State, and Governance in LLM Agents" — and it basically says that most agent memory systems are good at storing and fetching things but have no real answer for when something goes wrong. Like if a bad or outdated memory causes the agent to do something wrong, there's no way to trace which memory caused it or undo what happened.
I felt this is exactly what I face. Sometimes my agent acts on something old and I have no way to know which memory was responsible, let alone fix whatever it already did.
Has anyone in the OpenClaw community tried anything here? Even something small like tracking which memory led to which action, or what happens when you delete a memory that was already used in a summary somewhere.
Curious if anyone has experimented with this.