Agent Memory
Giving an AI a way to remember across conversations, since the model itself forgets everything the moment a session ends.
When not to use it
- For one-shot tasks. A translation or a summary doesn't need to remember you, and building memory into it adds privacy surface for nothing.
- When the conversation fits in the window. Re-sending it is simpler, exact, and free of retrieval bugs.
- When you can't answer "how does a user delete this?" Memory you can't erase is a liability with a UI.
Reach for something else instead
- Just re-send the conversation — context windows are large, and this is exact where retrieval is approximate.
- Explicit user profiles — a structured record the user can see and edit beats inferred memories they can't.
- Summarisation only when you need continuity within a long session but nothing across sessions.
Sources & further reading
- Park et al. (2023), Generative Agents: Interactive Simulacra of Human Behavior — a memory stream with retrieval and reflection, and the clearest worked example.
- Liu et al. (2023), Lost in the Middle: How Language Models Use Long Contexts — why stuffing history into the window is not the same as the model using it.
- Packer et al. (2023), MemGPT: Towards LLMs as Operating Systems — treating the context window as managed memory.
Primary sources, listed so you can check the claims on this page rather than take them on trust.
Where people go wrong
- Storing everything and retrieving badly, then concluding memory doesn't work. The failure is almost always retrieval, not storage.
- Letting the system infer sensitive facts and store them silently. Users find this unsettling, and they're right to.
- Forgetting that summaries are lossy and one-way. Whatever the summariser judged unimportant is unrecoverable.