Project boundaries
Claude Project Memory: Boundaries, Instructions, and RAG
A Claude Project gives memory a boundary. It can have its own memory summary, its own instructions, and uploaded knowledge, but those are different mechanisms.
Project memory summaries are separate from non-project chat memory.
Moving a chat into or out of a project changes which summary it belongs to.
Project instructions guide behavior inside a project; they are not the same as memory summary.
Project RAG retrieves uploaded knowledge when project content grows large; it is not the same as memory.
"Claude maintains separate memory summaries for each individual project." Claude Help Center
Three project layers
Claude Projects combine three ideas that are often described as one thing. Project memory is the summary Claude maintains for that project. Project instructions are guidance you write for chats inside that project. Project knowledge is uploaded material Claude can use, and in larger projects it may be retrieved with RAG.
Keeping those layers separate makes project behavior easier to debug. If Claude gets a fact wrong, check project knowledge. If Claude uses the wrong tone, check project instructions. If Claude carries stale assumptions across chats, inspect memory.
Moving chats changes the memory boundary
The Help Center describes moving chats into and out of Projects as a way to manage what is included in memory summaries. If a conversation happened in the wrong place, move it out so it no longer belongs to that project-specific summary.
This is especially important for agencies, consulting teams, and anyone switching between clients. Project boundaries are only useful when chats are filed in the right project.
Project instructions vs project memory
Use project instructions for stable rules: audience, role, workflow, terminology, formatting expectations, and constraints. Use memory for learned continuity: what the project has been doing lately, what decisions have been made in chats, and what collaboration preferences are emerging.
If something must be visible before the first chat in a project, write it as an instruction. If it emerges over time, memory can carry it, but you should still promote durable decisions into a project doc.
RAG is not memory
Claude Help describes project RAG as a way to retrieve relevant information from uploaded documents instead of loading all project content into memory at once. That means RAG is a retrieval strategy for project knowledge, not the same thing as the memory summary.
Use clear filenames and organized uploads for knowledge. Use project instructions for behavior. Use memory for continuity. Blending all three into one "memory" bucket is how projects become hard to reason about.
FAQ
Should I put project rules in memory or project instructions?
Put stable rules in project instructions. Let memory capture continuity, then promote important decisions into durable docs.
Does uploading documents create memory?
No. Uploaded project knowledge can be retrieved, including through RAG when needed, but it is distinct from memory summaries.
Primary Sources
Claude Help Center · 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.
Accessed 2026-07-06
Claude Help Center · Help Center
Understanding Claude's personalization features
Primary reference for profile instructions, project instructions, and styles.
Accessed 2026-07-06
Claude Help Center · Help Center
Retrieval augmented generation (RAG) for projects
Primary reference for project knowledge RAG and how it differs from memory summaries.
Accessed 2026-07-06
Claude Help Center · 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.
Accessed 2026-07-06