Memory for agents
Agents need memory beyond a single message: the current chat (short-term), and sometimes durable stores (preferences, project files, retrieved docs).
What it is
Agents need memory beyond a single message: the current chat (short-term), and sometimes durable stores (preferences, project files, retrieved docs).
Why it matters
Without memory design, agents repeat questions, forget constraints, or “remember” the wrong things. With careless memory, they store secrets they should not.
How it works (plain)
- Context window: working memory for this run
- Summaries: compressed older chat
- RAG/files: look up facts when needed
- User profile stores: explicit preferences (opt-in)
Write policies for what may be stored and for how long.
Everyday example
“Remember my preferred citation style for this project” (explicit) vs silently storing pasting of an API key (bad).
Try it
Draft a one-page memory policy: store / never store / ask first.
Myths
- ⚠️ Myth: Long context replaces a database.
- ✓ Reality: Context is finite and expensive; stores + retrieval scale better for corpora.
- ⚠️ Myth: More memory is always smarter.
- ✓ Reality: Stale or wrong memories poison future actions.
Sources
- ANN live: https://www.ainerdnetwork.com/learn/memory-for-agents ↗
- Course 07 context windows; Course 09 RAG
- NIST AI RMF (data governance themes): https://www.nist.gov/itl/ai-risk-management-framework ↗
