Organize source knowledge and inspect what Claude recalls from earlier work.
Conversation & research · Changing · Documentation checked 2026-10-04
Claude apps, projects, and Cowork; Claude Code and Claude Platform are separate environments.
Projects exist across plans; chat search and memory depend on paid access. A new Projects beta is rolling out, starting in Claude Code.
The worked example is illustrative and has not been tested in a signed-in product account.
What it does and how it connects
Organize source knowledge and inspect what Claude recalls from earlier work.
Project knowledge and instructions deliberately establish a working context. Chat search and memory retrieve or carry prior context where supported. The new Projects beta is a changing experience, starting in Claude Code; do not assume its coordinator behavior exists in every legacy project.
Walkthrough
Use the product named in the access panel. The steps below combine documented controls with the editorial example.
- Create or open a project and add a small approved knowledge set.
- Set concise project instructions about audience, evidence, and terminology.
- Review the memory controls available to your plan and inspect any recalled preferences.
- Begin a fresh project conversation and ask what context is actually available.
Worked example
Place an approved glossary and workshop agenda in an AI literacy project. Ask for a lesson that uses those terms. Test a deliberate conflict: an earlier casual preference should not replace a current requirement to label uncertain claims.
From this project’s glossary and agenda, draft a lesson about automation. List the sources available to you before drafting. Keep the glossary’s definitions. If remembered preferences conflict with the agenda, state the conflict and follow the current requirement. Do not invent prior decisions.
Inspect and verify the result
Compare definitions with the uploaded glossary and inspect memory settings directly. Project chat search is scoped differently from general past-chat search. Essential policy should be deliberately supplied rather than left to uncertain recall.
Limits and troubleshooting
Paid access affects chat search and memory. If information is missing, attach it or restate it explicitly. A new beta project interface may not match a legacy tutorial; use the linked current help article.
Data, permissions, and actions
Project knowledge persists as context, and memory can carry information into later work. Review shared-project access and avoid storing secrets as preferences. Incognito conversations have separate memory and retention behavior.
Related reading
Artifacts and editable outputs
Move a result into a surface that can be inspected, revised, and shared deliberately.
From reports to an editable briefing
Build a private Artifact from a bounded source set and a verified argument.
A bounded Cowork preparation task
Use an eligible agent to prepare a workshop pack while preserving original files.
Plugins, connectors, and skills
Separate packaged capabilities, reusable instructions, and the connections that let AI reach other software.
Sources and verification
Documentation checked 2026-10-04. Examples are illustrative unless described otherwise.
Projects and the new project experience · Anthropic
Chat search and memory · Anthropic