Claude's chat-search tool is available on Pro, Max, Team, and Enterprise across web, desktop, and mobile. Searches appear as tool calls, and references can link back to their source chats. Chat search and its boundaries, checked October 24, 2026.
Decide which conversations belong to the question
Anthropic describes two search scopes: conversations outside projects, and conversations within an individual project. A project search is limited to that specific project. Start inside the project that contains the work if that is where the decisions happened.
For work spread across projects, inspect the relevant project separately and bring the permitted passages into a comparison. Do not interpret a search confined to one project as proof that another project contains nothing relevant.
Search and saved memory have different roles. Memory can carry a useful preference into the next task; chat search helps you return to the exchange supporting a particular claim. If your goal is transferring preferences to another service, use the separate memory-import workflow.
Ask for the changes before asking for a fresh plan
This prompt works with your actual saved conversations:
Search our previous conversations about [IDENTIFIABLE PROJECT/TOPIC]
within [THIS PROJECT / CHATS OUTSIDE PROJECTS].
I need to reconstruct how [SPECIFIC DECISION] changed.
List the relevant conversations chronologically. For each, provide
its title/date if available, a source citation, the supporting passage,
and whether it records a proposal, accepted decision, or later change.
Do not invent dates or treat a drafted suggestion as my approval.
Return the latest supported decision, the earlier choice it replaces,
and any unresolved conflict. State the search scope and gaps.
Do not create a new plan or update saved memory yet.
Give it a distinctive phrase you actually remember, such as an unusual document title. A guessed deadline may steer retrieval toward the wrong exchange. Watch for the search tool call; if the answer merely says it remembers, ask for a search and source citations.
Check a revision that changes only one part of the plan
Consider these fictional conversation excerpts, written for this guide:
| Conversation | Recorded statement |
|---|---|
| Initial setup | “Use a two-column handout and include the equipment checklist.” |
| Layout revision | “Make the handout one column. Keep the equipment checklist.” |
| Later draft | Claude suggests removing the checklist; the user gives no response. |
The supported current instruction is one column with the checklist retained. The later draft does not establish permission to remove it. A useful reconstruction names both changes: the column count changed, while the checklist requirement continued.
Open each source citation and read the messages immediately after the quoted passage. An apparent approval might refer to a different proposal farther up the conversation. Check who wrote the words too; the assistant proposing a change and the user accepting it are different events.
When an expected conversation does not appear
Inspect Settings > Memory > Search and reference chats. Confirm the search scope and account. Incognito chats are excluded from search; Enterprise organizations using customer-managed encryption keys cannot use past-chat search. Anthropic documents these restrictions separately from ordinary memory settings. Search controls and exclusions
If you locate the conversation manually, supply the relevant passage with its source and explain that you found it yourself. Keep an unresolved gap visible when neither route retrieves the evidence. Do not reset memory to troubleshoot one missing conversation.
Finish by placing the checked current instruction and its source links in the working brief. In the handout example, record “one column; equipment checklist retained,” so the next draft starts from the accepted revision.