Skip to main content

Memory Stores

Workspace-scoped persistent memory for Managed Agents: a filesystem mounted into every session, versioned and auditable, so what an agent learns survives the run.

Hand-drawn line illustration in warm terracotta and cream: a loopy line-drawn hand lifts one cream folder out of a neat stacked column of identical folders resting on a single wobbly shelf line, a one-line profile face looking on.

What it is​

A session is disposable by design; a Memory Store is what persists across them. Per the Managed Agents docs (verify against platform.claude.com/docs; beta surfaces drift), a Memory Store is workspace-scoped persistent storage mounted into the session's container as a filesystem, at a path like /mnt/memory/<name>/. The agent reads and writes it with ordinary file tools. Contents are versioned, carry an audit trail, and support redaction.

Why files, not a database​

Anthropic's context-engineering guidance treats structured note-taking as a first-class memory technique: Effective context engineering for AI agents (September 2025) frames context as "a finite resource with diminishing marginal returns," which means an agent cannot simply carry everything it knows in the window. The working alternative is notes on disk: the agent writes down what it learned, and the next session reads only what it needs. A mounted filesystem makes that pattern native. No retrieval service, no embedding pipeline, no schema migration; the model already knows how to use files.

The versioning and audit trail matter because memory is state that compounds. A wrong fact written today poisons every future session that reads it, so you want to see what was written, when, and by which run, and be able to roll it back.

What it enables​

Persistent memory is the mechanism behind the Company Brain, the pattern where an agent accumulates knowledge of how a specific organization works. It is also load-bearing for long-running work and anything on a schedule: a nightly job that cannot remember last night starts from zero forever.

  • Rakuten's Managed Agents deployment is built on exactly this: "Cloud-hosted specialist agents with persistent compute and memory that work alongside employees across engineering, product, sales, marketing, and finance." (source)
  • Notion pairs agent orchestration with a "Self-improving skills database" that is "maintained by Claude after every completed task," so lessons from each run feed the next one. (source)
  • Greptile's review agent uses sub-agents for memory retrieval so codebase knowledge accumulated across reviews stays available without flooding the main context. (source)

The discipline it requires​

Memory is not free context. Everything above about context as a scarce resource still applies to what gets read back in; a memory store that grows without curation becomes a slower way to be confused. The pattern that works in Anthropic's guidance is deliberate: the agent maintains specific, named artifacts (a progress file, a decisions log, a map of the territory) rather than an append-only transcript of everything it ever thought.

Further Reading​