What you will be able to do
- Describe how memory entries get created and why a wrong one stays after its chat is gone
- Correct a wrong memory entry through Settings or a normal chat, and rule out fixes that don't work
- Choose between incognito, memory off for one chat, pausing and resetting for a sensitive conversation
1.How memory is written, and why errors persist
Claude's memory carries context from your chats into new conversations, so a wrong detail in memory doesn't stay in one chat. It shapes every later answer that relies on it. Keeping memory accurate starts with knowing how entries get there.
Claude saves memory as individual topics while you chat. It does not write a summary after the conversation ends. If you mention that a deadline moved, your next conversation already knows. Claude saves on its own, and you can also tell it to "remember this" to save something directly. Memory concentrates on work: your role, projects, working style and preferences. Personal details unrelated to work may not be kept.
The catch is that a memory entry outlives the chat it came from. On Team and Enterprise plans, deleting a conversation, even under a retention period, does not remove the memory entries generated from it. Individual memories have to be deleted while memory is on. So fixing a wrong fact means editing memory itself, not cleaning up old chats.
Checkpoint 1 of 5· Check yourself
On a Team plan, Claude keeps using a wrong deadline that came up in an earlier chat. To fix it, the user deletes that earlier chat. What happens to the memory entry that holds the wrong deadline?
On Team and Enterprise plans, deleting a conversation does not remove the memory entries that came from it, even under a retention period. Claude also saves memory as topics while you chat, not as a summary after the chat ends. So the wrong entry has to be edited or deleted in memory directly.
“memory entries generated from it aren’t removed, but members can delete individual memories while memory is on”Source: support.claude.com
2.Reviewing and correcting memory entries
Two routes change memory at the source. In Settings, go to Settings > Your Claude and select Manage next to Your memory (Settings > Memory in the older layout). That view shows memory exactly as Claude sees it, and the "Tell Claude what to change or remove" box takes corrections. In a normal chat, simply tell Claude which detail to change or forget. To audit everything at once, ask Claude in a chat to write out its memories of you word for word, exactly as they are stored. You can save that readout as a backup.
| Action | Effect on the wrong entry |
|---|---|
| Manage next to Your memory in Settings > Your Claude, then correct it | Changes it |
| Telling Claude in a normal chat to change or forget the detail | Changes it |
| Stating the correct fact in an incognito chat | None: incognito neither uses existing memory nor adds to it |
| Editing Project instructions | None: instructions are a separate setting that only applies to chats in that project |
| Waiting thirty days | None: 30 days is how long incognito chats are retained, not how long memories last |
Checkpoint 2 of 5· Match them up
A memory entry about you is wrong. Match each action to what it does to that entry.
Tap a term, then the definition that fits it.
Only two routes change memory at the source: the Manage view in Settings and a direct request in a normal chat. Incognito chats are kept out of memory in both directions, Project instructions are a separate setting, and 30 days is the incognito retention period, not a memory expiry.
“Starting an incognito chat won’t use Claude’s existing memory.Incognito chats will not be included in future memory entries.”Source: support.claude.com
Checkpoint 3 of 5· Exam question
Memory now lists a wrong detail: that Ayo manages a team of ten, when it is three. Which two actions correct it at the source? Choose two.(Select 2)
Correct answers: A, D — Tell Claude in a normal chat to change or forget that detail about the size of his team.; Open Settings, go to Your Claude, choose Manage next to memory, and edit the relevant topic.
- A. Correct: telling Claude in a normal chat to change or forget something is a supported way to update memory.
- B. Incorrect: incognito chats are not saved to memory, so nothing said there can update a stored entry.
- C. Incorrect: memories are not removed on a thirty-day timer; stale ones stay until edited or deleted.
- D. Correct: the memory list can be browsed and individual topics edited directly in settings.
- E. Incorrect: Project instructions guide chats in that Project but do not rewrite the account's stored memory topics.
3.Keeping a conversation out of memory
Sometimes you want a conversation never to reach memory at all, such as rehearsing a salary negotiation with your current pay and fallback offers. Four controls touch memory. They differ most in what happens to the chat itself.
| Control | Effect on memory | Effect on the chat | Where and when |
|---|---|---|---|
| Incognito chat (ghost icon) | Doesn't use existing memory; never added to memory | Not saved to chat history, not found by past-chat search, can't be reopened once closed | Only for new chats outside projects |
| Memory off for one chat ("+" menu) | Doesn't use or add to your memory or the project's memory | Stays in chat history and can be found by past-chat search | Set before the first message; also works in projects |
| Pause memory | Keeps existing memory but uses none and creates none | Chats are saved as usual; nothing from the pause is added later | Account-wide, until you unpause |
| Reset memory | Permanently deletes all memories, including project memories | Cannot be undone; memory starts from scratch | Account-wide |
For the salary conversation, incognito is the only control that keeps it out of memory, out of chat history and out of later searches. Turning memory off for one chat leaves the chat in your history, where other conversations can still find it. Pausing memory removes nothing from history. Holding the conversation in a Project doesn't help either: incognito isn't available inside projects, and project chats are saved like any other. Inside a project, the closest option is to turn memory off for that chat before you send the first message. Incognito chats can't be reopened after you close them, so copy anything you need before ending the session.
Incognito is not invisible. Incognito chats aren't used for training, and they are retained for 30 days by default. On Team and Enterprise plans they appear in organizational data exports and follow the organization's retention policy. Reset is the opposite extreme. A compliance request to clear every stored memory, including memories inside Projects, is met by Reset memory, and employees should know it is permanent.
Checkpoint 4 of 5· Check yourself
Priya is working inside a Project and wants one chat about a sensitive pay dispute to stay out of memory, while memory keeps working in all her other chats. What should she do?
Incognito isn't available inside projects, and pausing memory applies to the whole account, so it would affect her other chats too. Turning memory off for one chat works in projects and affects only that chat. It has to be set before the first message, because the setting can't be changed after the chat starts.
“turn memory off for a single chat in a project by turning off "Memory" in the "+" menu before you send your first message.”Source: support.claude.com
Checkpoint 5 of 5· Exam question
Marcus is preparing for a salary negotiation and wants to talk through his fears, current pay and fallback offers with Claude. He does not want any of it saved to memory or chat history, or surfaced in later chats. Which option fits?
Correct answer: C — Start an incognito chat with the ghost icon, which is not saved to memory or chat history and is not searched later.
- A. Incorrect: a normal chat is saved in history, so deleting a memory topic afterwards does not remove the conversation itself.
- B. Incorrect: Projects have their own memory and keep their chats; they are a place for organized work, not a privacy mode.
- C. Correct: an incognito chat is not saved to memory or chat history and Claude will not search it later, which matches the privacy need exactly.
- D. Incorrect: pausing memory stops Claude from using or creating memories, but the chat itself would still appear in his chat history.
Practise it for real
Audit your Claude memory and correct one outdated entry at the source
1.Go to Settings > Your Claude and select Manage next to Your memory.
Why: This view shows memory exactly as Claude sees it, so you are reviewing what actually shapes its answers.
You should see: A list of what Claude currently remembers about you.
2.In a normal chat, ask: "Write out your memories of me verbatim, exactly as they appear in your memory." Copy the result into a local file.
Why: A full readout is easier to scan for stale details and doubles as a backup.
You should see: A complete text dump of your memory, saved on your computer.
3.Pick one outdated detail and correct it, either in the "Tell Claude what to change or remove" box or by telling Claude in a normal chat to change or forget it.
Why: These are the two routes that change memory at the source. Incognito chats and Project instructions do not.
You should see: The Manage view shows the corrected detail.
4.Start a new normal chat and ask a question that depends on the corrected detail.
Why: This confirms the fix reaches new conversations, which is the point of correcting memory.
You should see: Claude's answer uses the corrected detail.
Sources
(4)
Every claim above is drawn from one of these pages, quoted as it was written on the date shown.
- 1.https://support.claude.com/en/articles/11817273-use-claude-s-chat-search-and-memory-to-build-on-previous-contextOfficial docs
“Claude saves memory as a set of individual topics as you chat, rather than summarizing conversations after they end.”
↩︎ How memory is written, and why errors persist“Mention that a deadline moved, and your next conversation already knows.”
↩︎ How memory is written, and why errors persist“Claude saves on its own, and you can also tell Claude to "remember this" to save something directly.”
↩︎ How memory is written, and why errors persist“memory entries generated from it aren’t removed, but members can delete individual memories while memory is on.”
↩︎ How memory is written, and why errors persist“Clicking the ghost icon will open an incognito chat”
↩︎ Keeping a conversation out of memory“the chat stays in your chat history and Claude can still find it when searching past chats”
↩︎ Keeping a conversation out of memory“You need to turn memory off before you send the first message.”
↩︎ Keeping a conversation out of memory“A chat started with memory off in a project doesn't use your memory or the project's memory.”
↩︎ Keeping a conversation out of memory“Conversations while memory is paused won't be added to memory if you turn it back on.”
↩︎ Keeping a conversation out of memory“Reset memory: Permanently deletes all memories including project memories.”
↩︎ Keeping a conversation out of memory“memory entries generated from it aren’t removed, but members can delete individual memories while memory is on.”
↩︎ Exam trap 1“Claude keeps its existing memory, including sensitive topics if you have it turned on, but won't use memory or make new memories.”
↩︎ Exam trap 3“memory entries generated from it aren’t removed, but members can delete individual memories while memory is on”
↩︎ Checkpoint - 2.https://support.claude.com/en/articles/12123587-import-and-export-your-memory-from-claudeOfficial docs
“Claude's memory is designed to focus on work-related topics to enhance its effectiveness as a collaborator.”
↩︎ How memory is written, and why errors persist“To view your memory exactly how Claude sees it, go to Settings > Your Claude and select "Manage" next to Your memory”
↩︎ Reviewing and correcting memory entries“add that information using the "Tell Claude what to change or remove" box, or by asking Claude in chat.”
↩︎ Reviewing and correcting memory entries“Write out your memories of me verbatim, exactly as they appear in your memory.”
↩︎ Reviewing and correcting memory entries - 3.
“Starting an incognito chat won’t use Claude’s existing memory.”
↩︎ Reviewing and correcting memory entries“Incognito mode is currently only available for chats outside of projects”
↩︎ Keeping a conversation out of memory“Once closed, incognito chats cannot be reopened.”
↩︎ Keeping a conversation out of memory“they are retained for either 30 days (default)”
↩︎ Keeping a conversation out of memory“Incognito chats are included in organizational data exports available to account Owners.”
↩︎ Keeping a conversation out of memory“Incognito chats will not be included in future memory entries.”
↩︎ Exam trap 2“Incognito chats will not be included in future memory entries.”
↩︎ Prediction“Starting an incognito chat won’t use Claude’s existing memory.Incognito chats will not be included in future memory entries.”
↩︎ Checkpoint“turn memory off for a single chat in a project by turning off "Memory" in the "+" menu before you send your first message.”
↩︎ Checkpoint - 4.https://support.claude.com/en/articles/10185728-understanding-claude-s-personalization-featuresOfficial docs
“These instructions only apply to chats within that project.”
↩︎ Reviewing and correcting memory entries