Claude-written notes
Claude Code Auto Memory: Storage, Limits, and Audits
Auto memory is Claude Code writing local Markdown notes for itself. It is useful precisely because it is automatic, and risky precisely because it can become stale.
Auto memory stores plain Markdown in ~/.claude/projects/<project>/memory/.
MEMORY.md is the startup index; topic files are read on demand.
Auto memory is per repository and shared across worktrees.
Use /memory to inspect, toggle, and open auto memory.
"Each Claude Code session begins with a fresh context window." Anthropic Claude Code Docs
What auto memory is
Auto memory lets Claude Code accumulate knowledge without you editing a project instruction file. It can save build commands, debugging insights, architecture notes, code style preferences, and workflow habits when Claude decides they will help later.
That makes auto memory a learning layer, not a policy layer. It should complement CLAUDE.md, not replace it.
Where it lives
The docs describe auto memory files as plain Markdown under ~/.claude/projects/<project>/memory/. MEMORY.md acts as the concise entrypoint. Deeper topic files can hold more detail and are read when needed.
Because these files are local to your machine and outside the repo by default, they are good for personal learned context. If a learning should help the whole team, promote it into a shared project file or docs page.
The startup limit
Claude Code loads the first 200 lines or first 25KB of MEMORY.md at conversation start, whichever comes first. Content beyond that threshold is not automatically loaded at startup. Topic files are available on demand, but only if Claude needs and reads them.
That means MEMORY.md should be an index, not a warehouse. Keep it short, point to topic files, and delete stale notes.
Audit rhythm
Audit auto memory when Claude repeats an old mistake, when a repo changes its build system, after a major migration, before switching clients, and before handing a workstation to someone else.
A simple audit loop is: run /memory, open the auto memory folder, skim MEMORY.md, remove stale facts, and promote team-relevant items into CLAUDE.md or project docs.
FAQ
Is auto memory committed to git?
No by default. Claude Code auto memory lives under your home directory, not inside the repository.
Can I edit auto memory?
Yes. The docs describe auto memory files as plain Markdown that you can edit or delete.