Guide · 31 episodes · updated 2026-09-06

Agent memory: how agents carry state across turns, tasks, and attacks

← all guides

How do AI agents keep and use memory across sessions, tasks, and teammates?

Agent memory is whatever survives past the current : a , a , a graph, or a shared board that an reads and writes as it works. The papers keep hitting the same wall because context alone can't hold months of deployment, long research runs, or multi-agent collaboration without either losing useful lessons or drowning in stale ones. They disagree on where memory should live — plain text notes, executable code, external graphs, or the model's own — and whether it should be private per agent or a shared, permissioned store the whole team edits. They agree on two things: unmanaged memory degrades performance over time, and treating what to keep or discard as a trainable beats fixed heuristics. A recurring dark side is that the same persistence agents rely on also gives attackers a durable place to hide.

What agent memory means

Agent memory is the persistent state an AI agent carries across turns, sessions, or tasks — everything beyond what fits in the current context window. Designs span scratchpads, vector stores, structured knowledge bases, and explicit episodic memories, all wrestling with the same tension: keep enough to be useful, prune enough to stay coherent.

The episodes (31)

Newest first. Each line is what that paper contributed to the question.

Papers we have not covered yet

Other guides

Intro written by Anthropic's Claude Sonnet 5; episodes selected and edited by Garrett Casey. Episode notes come from each episode's own analysis. How PaperDive is made.