The author proposes a mental model where AI agents should maintain a separate memory layer (brain) that stores reusable understanding, distinct from their knowledge base (library), to avoid rediscovering the same information repeatedly.
One thing that's always bothered me about AI agents is that they keep rediscovering the same things. You point an agent at docs, code, notes, meeting records, whatever. It finds the answer. Then a few days later it has to do the exact same retrieval and reasoning process all over again. 😓 Humans don't really work like that. A useful mental model I've been thinking about recently is: **The knowledge base is the library.** **Memory is the brain.** The library stores information. The brain stores understanding. When you learn something from a book, you don't reread the entire library every time someone asks you a related question. You reuse what you've already learned. Agents probably shouldn't have to rediscover everything either. That got me wondering whether we're drawing the boundary between knowledge bases and memory in the wrong place. A lot of agent memory systems focus on storing facts, preferences, or conversation history. But what if memory also stored reusable understanding? For example, after an agent spends time searching documents, comparing sources, and figuring something out, it could save the distilled insight rather than forcing future runs to repeat the same retrieval process. In that model: * the knowledge base remains the source of truth * memory becomes a reusable layer of understanding Another analogy I've found useful: **The KB is MySQL.** **Memory is Redis.** MySQL remains the source of truth. Redis exists because repeatedly recomputing or rereading the same thing is expensive. Agent memory feels similar. If an agent has already spent time understanding a document, comparing options, and reaching a conclusion, some of that understanding can probably be reused instead of rebuilt from scratch every time. I've been experimenting with this idea in a side project called **Little Heta**. The workflow is roughly: heta insert ./project-docs heta query "How does our deployment architecture work?" heta remember "We decided to use Postgres." heta recall "What database did we choose?" I've been using it together with Codex and Claude Code through a simple skill integration. The broader question I'm interested in is: **How do we make agents accumulate useful knowledge over weeks or months instead of starting from scratch every session?** Curious how others think about this.😆
An opinion piece arguing that AI agents in enterprises need a structured 'Company Brain' memory layer to reliably access context, policies, and permissions, rather than relying solely on RAG and tool access.
The article distinguishes between reusable knowledge (durable context) and operational memory (task state) as essential components for building proactive AI agents that can follow through on complex tasks.
This thread explores how the brain's dual memory systems (hippocampus and neocortex) offer lessons for building long-running AI agents, arguing that agents need a fast episodic capture and slow consolidation mechanism to avoid catastrophic interference, rather than relying solely on frozen models with temporary scaffolding.