Everyone says their agent "has memory"- what do you actually mean by that?
Summary
The article discusses the ambiguous meaning of 'memory' in AI agents, highlighting different interpretations like context stuffing, vector DBs, user profiles, and scratchpads, and calls for clearer definitions.
Similar Articles
Do agents actually need memory, or are we using it to compensate for bad architecture?
The post questions whether memory in AI agents is essential or a workaround for poor architecture, and asks practitioners what needs to be persisted in production systems.
What I learned trying to make agent memory survive more than one session
The article reflects on the complexities of AI agent memory beyond simple storage, highlighting challenges such as determining truthfulness, priority changes, distinguishing decisions from noise, and appropriate timing for surfacing context.
How AI agent memory works (28 minute read)
The article provides a comprehensive technical overview of how AI agent memory works, distinguishing between working and long-term memory mechanisms, and discussing strategies for context management, embedding-based retrieval, and data lifecycle governance.
Do you see agent memory primarily as an AI problem, or as an infrastructure/data-management problem that happens to be used by AI?
A reflection on agent memory as primarily an infrastructure/data-management problem rather than an AI problem, focusing on practical complexities like permissions, scopes, and revision history.
Understanding Agent Memory (38 minute read)
This article compares three common shapes of agent memory systems—file-based, structured store, and experience-based—and evaluates their effectiveness through a benchmark using a common agent loop and open-weight model.