starting to think “agent memory” is the wrong first framing
Summary
The author argues that 'agent memory' is the wrong first framing because it conflates working state and durable memory, leading to debugging issues. They advocate separating messy working state (which should expire) from strict durable memory with provenance and authority.
Similar Articles
agent memory should probably have verbs, not just storage
The article critiques the current framing of agent memory as merely a storage problem, arguing that memories should have typed roles, freshness, and authority levels to prevent stale or incorrect information from being treated as gospel.
I thought agent memory was a storage problem. I don't think that anymore.
A developer reconsiders agent memory as more than storage, proposing a living graph with roles and activation fields to give past information appropriate authority and context.
An agent remembering everything sounds useful until it remembers the wrong crap
The author critiques the idea of agents remembering everything and introduces TrueMemory, a system that converts memories into trait claims with confidence and evidence to better calibrate agent behavior.
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.
Agent memory is not just RAG over user facts
The article argues that simple RAG-based agent memory systems fail in production due to issues like stale preferences, missed keywords, and prompt injection, and advocates for a layered memory architecture with active selection, deterministic fallback, governance, and testing.