How to Make Claude Forget Something or Clear Its Memory
Remove an unwanted fact from the places that can supply it: saved memory, chats, project material, and connected work records. Check the result without mistaking a quiet answer for proof of deletion.
Updated 5 min read
To make Claude forget something, remove its saved memory entry and check any chats, project files, instructions, or connected records that still contain the information. Asking Claude to ignore a fact changes a conversation; it does not establish that every stored copy has been deleted.
Start by identifying the particular fact you want removed and where you entered it. Tools like fenbs keep shared work context outside Claude, so that record needs a separate review if it contains the same information. You can keep useful project continuity while deliberately removing an outdated or unwanted detail.
What should you remove first?
- Write a short description of the unwanted information without copying sensitive details into another app. Distinguish a wrong fact you want corrected from information you want removed entirely.
- Open Claude Settings, then Memory. Review the relevant saved topic and use its edit or delete control. You can also ask Claude to forget a fact, then inspect the setting yourself.
- Find conversations and project material containing the information. Decide which original records also need removal or correction.
- Check connected sources and separately maintained work notes. Removing something inside Claude does not remove a document or task from its original service.
- Start a fresh chat after the changes. Check the relevant controls and source records before treating the cleanup as complete.
Anthropic describes the saved-topic controls in its chat search and memory guide (opens in a new tab). If you only need to remove one thread, follow the narrower guide to deleting a Claude conversation.
Which places can still supply the same information?
Think about sources rather than one giant memory. A studio might remove an old delivery date from saved memory while leaving that date in its project instructions. The next answer can then repeat the date because another source still supplies it. That is a cleanup problem even if the first deletion worked.
| Place to check | What to inspect | What your cleanup needs to address |
|---|---|---|
| Saved memory | A topic containing the unwanted detail | Delete or correct the saved entry. |
| Conversation | The original message and later copies of it | Remove unwanted chat records separately. |
| Project material | Uploaded files and project instructions | Correct or remove the source supplied to that project. |
| Connected service | A document, task, or other outside record | Review it in the service that owns it. |
| Your own copies | Downloads, screenshots, exports, or pasted notes | Decide which copies you are authorized to retain. |
This map also helps when someone else maintains a source. Ask the project owner to review the relevant file rather than assuming your personal setting controls a shared document. Our Claude overview explains the app itself; the AI memory hub covers the broader distinction between stored context and chat history.
Should you pause memory or reset it?
Use an individual deletion when one detail is the problem. A broad reset can remove useful context you intended to keep, so decide what outcome you need before choosing an account-wide control. A general request such as “forget everything” is too vague to serve as your deletion checklist.
Claude distinguishes Pause memory, which keeps existing memories without using or adding to them, from Reset memory, which permanently deletes saved memories, including project memories. Verify the confirmation text in Settings before proceeding. Pausing is useful for stopping memory use; it is not a deletion action.
For example, changing employers may call for removing old workplace details while retaining a harmless writing preference. Review by topic instead of resetting first and reconstructing everything later. If you want no ongoing memory at all, check the memory setting again before starting new work.
Do project files and connected records need separate changes?
Yes. Anthropic explains that project knowledge and project instructions (opens in a new tab) supply context across chats in that project. Review both when a removed detail returns during project work. Editing a saved topic cannot rewrite an uploaded document.
For connected material, identify the original service and the action you need. Updating an outdated document, removing an attachment, and disconnecting access solve different problems. For example, Anthropic says data retrieved through its Google Workspace connectors (opens in a new tab) is retained with the associated chat; the underlying Google document is a separate record.
Review shared context in fenbs the same way: keep approved work facts current and remove unwanted detail from the relevant record, within your access. Its work context workflow is deliberately maintained; fenbs does not clear Claude memories or inspect your Claude chat history.
Review the work context you actually want to keep
Use fenbs for approved project facts, tasks, and the next step that should survive a Claude cleanup. Review that short record separately instead of copying an entire conversation. Connected assistants can read the maintained context when you choose to resume the work.
Create a free accountFree for one person · No credit card · Works with Claude, ChatGPT, Cursor and more
How can you check that the unwanted fact is gone?
Check records first and answers second. Reopen Memory and inspect the relevant topic, then confirm the selected source changes. Start a new conversation rather than testing in the thread where you just repeated the fact. Otherwise your test itself supplies the information you are trying to remove.
Ask a neutral question that would normally depend on the old detail, without including the answer. If Claude repeats it, ask which source it used and inspect any citation it provides. If Claude stays silent, that is useful behavior evidence, but it cannot prove that every server copy or external record is gone.
Anthropic separates visible deletion from back-end retention in its consumer data retention policy (opens in a new tab), including exceptions. Use that policy for a data-removal question rather than relying on a model’s assurance. The separate Claude API guide applies if you are building an app rather than using Claude chat.
How to do this with fenbs
- Create a free account and add the project whose approved work context you want to maintain.
- Write a short context note containing only the current nonsensitive facts needed to continue. Leave out the unwanted information and any unnecessary chat transcript.
- Record a person’s agreed retention or context rule in Decisions and rules. Keep its scope clear, such as which project facts assistants should save.
- Connect a supported assistant and ask it to read the project context. After working, ask it to save progress and the next step without reintroducing removed detail.
fenbs is free for one person, no credit card. It fits ongoing work you deliberately want available later. It is not the right fit for material you want to leave unrecorded, or for deleting information from Anthropic’s systems.