Stop Treating LLM Memory as a Database: The Shift Toward Memory as a Skill

Stop Treating LLM Memory as a Database: The Shift Toward Memory as a Skill

For the last two years, the industry has been obsessed with RAG. We've spent countless engineering hours optimizing vector databases, tweaking top-k retrieval, and arguing over chunking strategies. The underlying assumption has always been that memory is a retrieval problem: you store a document, you find the document, you feed it to the context window.

But if you've actually built and deployed agentic systems at scale, you know the truth: retrieval is the easy part. The hard part is curation.

I've been digging into the recent work on AutoMem (Automated Learning of Memory as a Cognitive Skill), and it hits on exactly why most RAG implementations feel brittle. The gap isn't in the retrieval algorithm; it's in the metamemory—the ability to decide what is actually worth remembering and how to organize it for future use.

The Problem with Passive Retrieval