claude-skills/engineering-team/self-improving-agent/reference/memory-architecture.md

Claude Code Memory Architecture

A complete reference for how Claude Code's memory systems work together.

Three Memory Systems

1. CLAUDE.md Files (You → Claude)

Purpose: Persistent instructions you write to guide Claude's behavior.

Locations (in priority order):

Scope	Path	Shared
Managed policy	/etc/claude-code/CLAUDE.md (Linux)	All users
Project	./CLAUDE.md or ./.claude/CLAUDE.md	Team (git)
User	~/.claude/CLAUDE.md	Just you
Local	./CLAUDE.local.md	Just you

Loading: Full file, every session. Files higher in the directory tree load first.

Key facts:

• Target under 200 lines per file
• Use @path/to/file syntax to import additional files (max 5 hops deep)
• More specific locations take precedence over broader ones
• Can import with @README or @docs/guide.md
• CLAUDE.local.md is auto-added to .gitignore

2. Auto Memory (Claude → Claude)

Purpose: Notes Claude writes to itself about project patterns and learnings.

Location: ~/.claude/projects/<project-path>/memory/

Structure:

~/.claude/projects/<project-path>/memory/
├── MEMORY.md           # Main file (first 200 lines loaded)
├── debugging.md        # Topic file (loaded on demand)
├── patterns.md         # Topic file (loaded on demand)
└── ...                 # More topic files as needed

Key facts:

• Enabled by default (since v2.1.32)
• Only the first 200 lines of MEMORY.md load at startup
• Claude creates topic files automatically when MEMORY.md gets long
• Git repo root determines the project path
• Git worktrees get separate memory directories
• Local only — not shared via git
• Toggle with /memory, settings, or CLAUDE_CODE_DISABLE_AUTO_MEMORY=1
• Subagents can have their own auto memory

What it captures:

• Build commands and test conventions
• Debugging solutions and error patterns
• Code style preferences and architecture notes
• Your communication preferences and workflow habits

3. Session Memory (Claude → Claude)

Purpose: Conversation summaries for cross-session continuity.

Location: ~/.claude/projects/<project-path>/<session>/session-memory/

Key facts:

• Saves what was discussed and decided in specific sessions
• "What did we do yesterday?" context
• Loaded contextually (relevant past sessions, not all)
• Use /remember to turn session memory into permanent project knowledge

4. Rules Directory (You → Claude, scoped)

Purpose: Modular instructions scoped to specific file types.

Location: .claude/rules/*.md

Key facts:

• Uses YAML frontmatter with paths field for scoping
• Only loads when Claude works with matching files
• Recursive — can organize into subdirectories
• Same priority as .claude/CLAUDE.md
• Great for keeping CLAUDE.md under 200 lines

---
paths:
  - "src/api/**/*.ts"
---
# API rules only load when working with API files

Memory Priority

When entries conflict:

1. CLAUDE.md (highest — explicit instructions)
2. .claude/rules/ (high — scoped instructions)
3. Auto-memory MEMORY.md (medium — learned patterns)
4. Session memory (low — historical context)

The Self-Improving Agent's Role

Auto-memory captures → This plugin curates → CLAUDE.md enforces

MEMORY.md (raw notes)  →  /si:memory-review (analyze)  →  /si:promote (graduate)
                                                          ↓
                                                    CLAUDE.md or
                                                    .claude/rules/
                                                    (enforced rules)

Why this matters: MEMORY.md entries are background context truncated at 200 lines. CLAUDE.md entries are high-priority instructions loaded in full. Promoting a pattern from memory to rules fundamentally changes how Claude treats it.

Capacity Planning

File	Soft limit	Hard limit	What happens at limit
MEMORY.md	150 lines	200 lines	Lines after 200 not loaded at startup
CLAUDE.md	150 lines	No hard limit	Adherence decreases with length
Topic files	No limit	No limit	Loaded on demand, not at startup
Rules files	No limit per file	No limit	Only loaded when paths match

Best Practices

1. Keep MEMORY.md lean — promote proven patterns, delete stale ones
2. Keep CLAUDE.md under 200 lines — split into rules/ if growing
3. Don't duplicate — if it's in CLAUDE.md, remove it from MEMORY.md
4. Scope rules — use .claude/rules/ with paths for file-type-specific patterns
5. Review quarterly — memory files go stale after refactors
6. Use /si:memory-status — monitor capacity before it becomes a problem