clean-claude-memory

Clean Claude Memory

Claude Code stores project-scoped durable notes outside the repository:

~/.claude/projects/<encoded-absolute-project-path>/memory/

MEMORY.md is the index. Other Markdown files are topic memories. Memory is a hint for future sessions, not an authoritative source; verify every claim against current code, docs, configuration, tools, and project state.

Treat recorded plans as historical artifacts only, not as documentation or a source of truth. Never use them to implement other features or as authoritative evidence about current behavior; verify relevant claims against current code, tests, configuration, requirements, and project documentation.

Do not include these unless the user explicitly expands the scope:

• repository CLAUDE.md or AGENTS.md;
• global ~/.claude/CLAUDE.md;
• memories belonging to another project.

Workflow

1. Resolve the current project's memory directory.
2. Read MEMORY.md and inventory every sibling memory file.
3. Review topic files one at a time. For each file:
   • read it completely;
   • explain what it preserves;
   • verify its claims against current authoritative sources;
   • identify stale facts, duplication, historical narration, and transient paths, versions, plans, or commands;
   • recommend one action;
   • ask the user one direct question and wait before reviewing the next file.

Use these actions:

Action	Use when
Keep	Unique, durable intent or preference remains accurate and useful.
Rewrite	A valuable core remains, but the file contains stale or excessive detail.
Delete	The content is obvious, obsolete, historical, or already authoritative elsewhere.
Move	The information belongs in code, tests, docs, a backlog task, or a reusable skill.

For Move, create and verify the new home before deleting the memory:

• code invariant or non-obvious trade-off → nearby comment or test;
• actionable future work → project task or issue;
• durable project contract → project documentation;
• reusable agent workflow → skill.