From Context to Memory: Your Agents Need a Real Memory Layer — Anders Swanson, Oracle
Anders Swanson argues that treating agent memory as a systems problem is necessary because current methods (like context windows or scratch files) fail to provide persistent, scalable recall. He outlines a modern memory architecture that involves four stages: formation, recall, evolution, and evaluation. This system requires a multi-model database to store typed memories (episodic, semantic, procedural, working state) and utilizes hybrid search, governance controls (like redaction), and continuous feedback loops to ensure data integrity and utility.
Key takeaways
-
Context Windows are not Memory
0:57
Context windows are merely input for the current run, not a persistent experience. Useful work synthesized by an agent is lost at the end of a session without persistence, forcing subsequent agents to repeat work and increasing the risk of hallucinations and failure. (0:57)
-
The Need for Structured Memory
2:07
Effective memory requires transforming useful agent experiences into managed, structured state. Simple workarounds like markdown files or tools like grep do not scale in large, multi-tenant environments, necessitating a database solution. (2:07)
-
The Memory Lifecycle Pattern
5:07
Modern memory systems converge on a pattern involving memory formation, recall, evolution, and evaluation. This process requires governance controls, such as redacting PII before writing, and continuous feedback to prevent memories from becoming stale, poisoned, or conflicting. (3:07, 4:37)