Memory is agent-curated knowledge; the agent’s instructions remain operator policy. Both are appended to the system prompt.
How recall works
The system prompt carries only a one-line index — slug plus description, one row per entry — not the bodies. The agent reads a specific entry from~/.claude/memory/<slug>.md when its description looks relevant. Prompt cost therefore scales with the entry count, not the size of the corpus.
Every session and run projects the agent’s memory into the workspace:
Agents curate their own memory
In a session an agent has two tools:save_memory— create or replace an entry (slug, description, body, optional kind). Saving an existing slug replaces it, so agents update rather than duplicate.delete_memory— remove an entry by slug.
Curating memory yourself
Pass
--body or --file, or pipe the body via stdin. The dashboard’s Context tab has the same list-and-edit surface.
Limits
At the cap, saving a new slug fails — the agent is told to consolidate or delete first. Replacing an existing entry always works.