Fetching from the wire…
Public story · 2026-07-25 · high
The paper's benchmarks skip latency and token cost, yet a reference build scores 92% on LongMemEval and 93.2% on LoCoMo.
Why now: It's here on July 25 because Dadhich's paper is the first cost model I've seen for agent memory, right as builders argue token bills without a number to point to.
A new paper splits AI agent memory into five stages, per Gaurav Dadhich's arxiv paper. Only one stage, done right, keeps costs from spiraling.
Teams running agents in production eat that cost. Accumulate history naively and it grows quadratically as conversations get longer. Summarize it crudely and the curve flattens back to linear, but at an accuracy cliff, where real information gets cut along with the noise. A reference build that gets this right, called Maximem Synap, still scores 92% on LongMemEval and 93.2% on LoCoMo.
Dadhich names the five stages as architecting, ingesting, scoping, anticipating, and compacting and consolidation. The last one is where the money is: only compaction validated against accuracy loss gets both linear cost and preserved fidelity. The framework treats memory as a resource shared across an organization's agents and teams, not a single user's chat log.
Those scores measure recall. They don't cover the things the paper says no benchmark captures: latency, token efficiency, and resistance to context rot. That gap means 92% and 93.2% describe how well the system remembers, not how fast or cheap it runs.
Teams buying bigger context windows to fix agent memory are solving the wrong problem. The paper's cost curve says compaction quality decides the bill, not window size, and nobody outside Dadhich's paper has benchmarked that yet.
Each link below shares sources, entities, or timing with this story.
EverMemOS benchmarked against LoCoMo / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (EverMemOS benchmarked against LoCoMo); both cover LoCoMo, LongMemEval; reported by the same outlet (arxiv.org).
NapMem benchmarked against LoCoMo / Shared entities / Same source domain / Earlier coverage
Linked by a graph relationship (NapMem benchmarked against LoCoMo); both cover LoCoMo, LongMemEval; reported by the same outlet (arxiv.org).
mem0 benchmarked against LoCoMo / Shared entity: LoCoMo / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (mem0 benchmarked against LoCoMo); both cover LoCoMo; overlapping topics (accuracy, agent, benchmark).
mempalace benchmarked against LoCoMo / Shared entity: LoCoMo / Earlier coverage
Linked by a graph relationship (mempalace benchmarked against LoCoMo); both cover LoCoMo; earlier LoCoMo coverage from 2026-07-21.
mempalace benchmarked against LoCoMo / Shared entity: LongMemEval / Earlier coverage
Linked by a graph relationship (mempalace benchmarked against LoCoMo); both cover LongMemEval; earlier LongMemEval coverage from 2026-04-30.
ByteRover CLI benchmarked against LoCoMo / Shared entity: LoCoMo / Earlier coverage
Linked by a graph relationship (ByteRover CLI benchmarked against LoCoMo); both cover LoCoMo; earlier LoCoMo coverage from 2026-04-18.
mempalace benchmarked against LoCoMo / Shared topic / Tension
Linked by a graph relationship (mempalace benchmarked against LoCoMo); overlapping topics (agent, benchmark); pushes against this story (against).
Same source domain / Shared topic / Tension
Reported by the same outlet (arxiv.org); overlapping topics (accuracy, agentic, benchmark, cost); pushes against this story (but).