The Memory System That Makes Sessions Compound

Session 1: you explain everything. Session 2: you explain everything again. Session 3: you explain everything again. See the pattern?

Without memory, Claude Code has amnesia. With memory, sessions compound. Each one starts where the last one ended.

The Memory Architecture

The memory system has three layers:

Layer 1: CLAUDE.md — Static context. Your stack, conventions, preferences. Doesn't change session to session.

Layer 2: Memory files — Accumulated knowledge. What Claude learned about your project, your corrections, your patterns. Grows over time.

Layer 3: Handoffs — Session-specific state. What was done, what's next, what's blocked. Written at session end, read at session start.

Setting It Up

1. Add to your CLAUDE.md: "At session start, read memory/ directory. At session end, write to memory/ with today's date."
2. Create a memory/ directory in your project
3. At the end of your first session, ask Claude to write a memory file
4. At the start of your next session, it reads that file automatically

What Compounds

After a week, Claude knows your naming conventions without being told. After two weeks, it knows which files relate to which features. After a month, it anticipates what you need.

This is the unlock. Not smarter prompts. Not better models. Just persistent context that accumulates.

The session lifecycle makes this automatic. Set it up once, benefit forever.