How it works
I describe memory as a stack of tiers, in the way an operating system separates RAM, disk and network.
- Boot-resident memory. What loads into context at startup: instruction files, tool catalogs, memory indexes. It is always visible and always paid for.
- Searchable files. Everything on the filesystem that the agent can find with search and open on demand. Large, cheap and invisible until a query touches it.
- Tool-gated stores. Databases and APIs behind a tool call. The agent has to know to ask.
- The world. Live sources that no store can cache faithfully.
Policies decide what stays resident, what is read on demand, what is promoted to a faster tier and what is removed. The comparison with hardware breaks in one place. A computer copies memory faithfully. A one-line summary of a document is a lossy copy, and it drifts as the document changes. Agent memory goes stale.
Where it shows up in real work
I tested two ways of locating documents in a pre-registered study, Reading More, Finding Less. One agent had only a hand-written index of one-line digests. The other searched the corpus and read what it found. The index led the agent to the correct document on 52.0% of 102 questions, against 80.4% for grep. Downstream, search-then-read was more accurate: 72.5% against 47.1%. A public replication over 141 documents and 120 frozen questions put search ahead by 12.5 points on accuracy. Its formal verdict is revised, because one prediction about token headroom failed, and the paper reports that failure next to the passes.
The write side failed too. In the same program, of 157 eligible files promoted into a durable memory directory, 2 were read later.
The result has a scope: an authored index of one-line digests over a prose corpus, used as the only locator. It says nothing about an index used together with search.
What it is not
Memory is not the context window, and a larger window is not more memory. Saving a fact is not remembering it either: remembering needs a later read that really happens.
When you need to design it
Design memory when an agent works over more material than fits in its context, which is most real work. Before you write an index that describes your files, check whether the agent with a search tool already beats it. If the agent saves notes for later, count the reads and not the writes. Treat every summary as a cached copy that can decay, and decide what validates it.