Auto memory
Learnings Claude Code saves across sessions on its own — build commands, debugging insights, project quirks — without you writing them down.
Last verified August 21, 2026 · 1 source
Auto memory is the half of Claude Code’s memory system that you do not maintain. As it works, Claude saves things worth keeping — the actual build command, why a test is flaky, which service the staging environment points at — and carries them into later sessions.
Why it exists separately from CLAUDE.md
CLAUDE.md captures what you already knew to write down. Auto memory captures what was learned in the
doing, which is usually the more expensive knowledge to reconstruct.
The two are complementary and are documented on the same page:
CLAUDE.md |
Auto memory | |
|---|---|---|
| Written by | You | Claude |
| Lives in | Your repository | Claude Code’s own storage |
| Version controlled | Yes | No |
| Shared with the team | Yes, via the repo | No |
| Good for | Standards and intent | Discovered facts |
What it does not do
- It does not replace
CLAUDE.md. Anything the team needs should be in the repository. - It is not shared. Memory learned on your machine is yours.
- It is not a substitute for documentation. If a fact matters beyond Claude, write it down where humans will find it.
What this page does not claim
Storage location, retention, per-project scoping and how to inspect or edit what has been remembered are documented upstream and are not reproduced here.
Plan availability
Anything left blank is not documented publicly, not a claim that it is unavailable. Compare every feature at once in the availability matrix.
- FreeNot available
- ProIncluded
- MaxIncluded
- TeamIncluded
- EnterpriseIncluded
- APINot documented
Comparisons
Sources
- 01How Claude remembers your project — Claude Code docsOfficialcode.claude.com
Page changelog
- VerifiedConfirmed as documented alongside CLAUDE.md on the memory page.