memory.md
A file-based index inside Claude Code that tracks available memories for a project and points to separate memory files organized by topic, domain, and tool rather than storing all content in a single file
As defined in Every Claude Code Memory System Compared (So You Don't Have To)
Where it comes up · 1
Most important claims · 4 of 4Search all claims for “memory.md” →
- The memory.md file should function as an index pointing to separate files rather than storing all memories directly; for example, it contains 'feedback on project structure' which points to feedback_project_structure.md, keeping the index under 200 lines and only loading specific files when needed.Every Claude Code Memory System Compared (So You Don't Have To)
- Level 2 of memory systems improves reliability by using a structured memory approach rooted at .claude/memory with subdirectories for general.md (cross-project facts and preferences), domain-specific knowledge (topic markdown files), and tools (individual tool config files like slack.md), injected automatically via a Claude Code session start hook.Every Claude Code Memory System Compared (So You Don't Have To)
- For someone literally just starting with Claude Code, don't worry about memory systems and just turn on Level 1 (claude.md and memory.md files) which takes 10 minutes and is a massive improvement on inbuilt memory.Every Claude Code Memory System Compared (So You Don't Have To)
- Claude Code's auto memory system creates memory files only on a project-by-project basis, meaning an empty folder with no project history has no memory.md file or consolidated memory until projects are created.Every Claude Code Memory System Compared (So You Don't Have To)