# Agent memory solves storage, not recall

> Cloudflare and MinIO both shipped durable 'agent memory' products this year, framed as the fix for context rot. The research the fix is named after says the hard part was never storage.

Published: 2026-07-29
Tags: llms, memory, context-engineering
Canonical: https://aaronchartier.com/blog/agent-memory-solves-storage-not-recall

---
Two infrastructure vendors shipped durable memory for AI agents within four months of each other this year. Cloudflare put [Agent Memory into private beta in April](https://blog.cloudflare.com/introducing-agent-memory/), extracting facts, events, instructions, and tasks out of a conversation and storing them in Durable Objects so an agent can recall them weeks later without replaying the whole transcript. MinIO followed in July with AIStor Memory, pitched as a new storage primitive alongside objects and tables, offering what it calls infinite context — persistent memory that scales with disk rather than the model's window, nothing "truncated, summarized, or evicted". Cloudflare names the problem outright — context rot, the finding that a model's accuracy degrades as its input grows, often well before the window is full. Both are selling the same cure: keep everything durably, retrieve only what's relevant. The model never has to hold more than it needs at once.

That's a real engineering achievement and also a narrower one than the pitch suggests. Durability was never the hard part. A database that never forgets is a solved problem. We've had one since before language models existed. The hard part, the one [Chroma's research team documented in July 2025](https://www.trychroma.com/research/context-rot) across eighteen frontier models, is what happens to accuracy once information — any information, freshly retrieved or not — actually lands inside the context window. Their tests found degradation driven by position and by how easily a distractor could be mistaken for the answer. Not by raw token count. A model can hold a million tokens and still lose the thread at three hundred thousand if the right fact is surrounded by plausible-looking wrong ones. Storing a fact durably doesn't change how it behaves once it's back in front of the model's attention.

This is an old shape wearing a new name. Virtual memory solved the same kind of problem for operating systems in the sixties: give a process a disk-backed page file and it can address far more than fits in physical RAM. But a bigger page file didn't fix a program that thrashed — that took a better page-replacement policy, deciding which pages to keep resident and which to evict, because the disk was never the bottleneck. The bottleneck was always the decision about what to load back in. Durable agent memory is a page file. The retrieval step that decides what to surface is the replacement policy, and that's the part neither vendor's launch materials put a number on.

To be fair, Cloudflare's own design shows they know this. Their pipeline runs five retrieval channels in parallel — full-text, exact key lookup, raw message search, and two flavors of vector search. It merges them with reciprocal rank fusion and runs verification passes against the source transcript before anything gets classified as a fact worth keeping. That's not a naive dump-and-fetch system. Someone there has read the same research MinIO is citing in its marketing without showing any of the work. MinIO's launch coverage carried no benchmark, no skeptic, no number — just the claim that context scales with the object store now, so truncation is a thing of the past.

Neither company's memory system has been run through the benchmark built to test exactly this. BEAM, an ICLR 2026 benchmark testing agent memory across conversations up to ten million tokens, found that models with million-token context windows struggle as dialogues lengthen whether or not they're paired with retrieval augmentation. The paper's own proposed fix, an episodic-memory framework called LIGHT, only improved on the strongest existing baselines by three to thirteen percent. Real, but nowhere near solved. Retrieval narrows what a model sees. It doesn't guarantee what survives the narrowing is the right thing, and the benchmark built specifically to check that says the gap is still wide open.

My bet: within a year, someone runs a Chroma-style rot evaluation directly against one of these commercial memory layers, not the underlying model. It finds the same position sensitivity and distractor confusion turning up in retrieved memories that Chroma found in raw pasted context. The mechanism doesn't care where the tokens came from. A retrieved fact lands in the window and gets attended to exactly like a fact you pasted in yourself, degradation curve included. Cloudflare and MinIO built real infrastructure this year. What they didn't build, because nobody has yet, is proof that memory retrieved on demand is any less prone to getting lost than memory that was never organized at all.