Claude Memory Sources

Bibliography

Claude memory changes across product surfaces, so this site treats source freshness as part of the content rather than a hidden editorial chore. Every guide prefers Claude-owned docs, help-center pages, release notes, and Anthropic blog posts.

Community posts are useful for workflow inspiration, but they are not used as authority for what Claude stores, loads, deletes, or exposes. When a page gives a recommendation, the recommendation is separated from the official behavior it relies on.

• Anthropic Claude Code Docs: How Claude remembers your project. Primary reference for CLAUDE.md, auto memory, /memory, file loading, rules, imports, and troubleshooting.
• Claude Help Center: Use Claude's chat search and memory to build on previous context. Primary reference for Claude app memory, memory summaries, incognito behavior, settings controls, and data handling.
• Claude by Anthropic: Bringing memory to teams. Launch and product context for team memory, project boundaries, and editable summaries.
• Claude Help Center: How can I create and manage projects?. Primary reference for moving chats into or out of Projects and managing project-specific memory summaries.
• Claude by Anthropic: Managing context on the Claude Developer Platform. Primary reference for developer-platform memory as a file-based tool managed by the developer.
• Claude Help Center: Understanding Claude's personalization features. Primary reference for profile instructions, project instructions, and styles.
• Claude Help Center: Retrieval augmented generation (RAG) for projects. Primary reference for project knowledge RAG and how it differs from memory summaries.
• Claude Help Center: Claude release notes. Freshness reference for ongoing Claude app and Claude Code product changes.

Citation policy

Each guide includes a source block with accessed dates. Short primary-source quotes are included as signposts, while the substantive guidance is original writing derived from the source behavior.

If a source changes, the affected article and freshness log should be updated together.