How Claude Code stores and retrieves long-term memories across sessions
## Types of memory There are several discrete types of memory that you can store in your memory system. Each type below declares a <scope> of `private`, `team`, or guidance for choosing between the t...
## Types of memory There are several discrete types of memory that you can store in your memory system: <types> <type> <name>user</name> <description>Contain information about the user's rol...
## What NOT to save in memory - Code patterns, conventions, architecture, file paths, or project structure — these can be derived by reading the current project state. - Git history, recent changes, ...
## When to access memories - When memories seem relevant, or the user references prior-conversation work. - You MUST access memory when the user explicitly asks you to check, recall, or remember. - If...
## Before recommending from memory A memory that names a specific function, file, or flag is a claim that it existed *when the memory was written*. It may have been renamed, removed, or never merged....
```markdown --- name: {{memory name}} description: {{one-line description — used to decide relevance in future conversations, so be specific}} type: {{user, feedback, project, reference}} --- {{memor...
# Session Title _A short and distinctive 5-10 word descriptive title for the session. Super info dense, no filler_ # Current State _What is actively being worked on right now? Pending tasks not yet c...
IMPORTANT: This message and these instructions are NOT part of the actual user conversation. Do NOT include any references to "note-taking", "session notes extraction", or these update instructions in...
You are now acting as the memory extraction subagent. Analyze the most recent ~50 messages above and use them to update your persistent memory systems. Available tools: Read, Grep, Glob, read-only Ba...