How to Get Claude to Recall a Previous Conversation
You worked something out with Claude last week. Today you open a new chat, ask it to pick up where you left off, and it either admits it has no idea what you mean or, worse, cheerfully invents a version of the conversation that never happened. So you search for whether Claude can remember previous chats, read other chats, or retrieve a conversation you had before.
Whether Claude has any built-in way to look at earlier chats depends on your plan, your settings, and what Anthropic has shipped to your account, and that changes. What does not change is the practical problem: you need the substance of an old conversation inside a new one. This post covers the reliable ways to do that, in order from quickest to most durable, plus what to expect when the chat you want was deleted.
If you want the background question first, whether Claude remembers between conversations at all, that is answered in Does Claude Remember Previous Conversations?. This post is the how-to that follows from it.
Start With What a New Chat Can See
A new Claude conversation begins with a fresh context window. By default, it contains your message, any Project instructions and files if you started the chat inside a Project, and whatever account-level features you have switched on. The transcript of an earlier chat is not part of that unless something puts it there.
That gives you a useful way to think about every method below. Each one is a different way of putting the relevant parts of the old conversation in front of the new one. Some do it automatically and some by hand, but the end state is the same: the information has to be in the context, because Claude cannot reason about text it cannot see.
It also explains why "continue where we left off" fails so convincingly. Claude cannot see the earlier chat, so it treats the phrase as an instruction to produce something plausible, and it does. The output looks like continuity. It is a guess.
Method 1: Check What Your Account Offers
Before doing anything manual, spend a minute in your Claude settings. Anthropic has introduced memory and chat-reference capabilities on some plans, and availability varies by plan, region, and rollout. If your account has an option that lets Claude search or reference past chats, and it is switched on, you can ask directly in a new chat for it to find the earlier conversation about a specific topic.
A few things to know if you go this route:
- Be specific in the request. Name the topic, the rough date, and a distinctive term from the old chat. Vague requests retrieve vague matches.
- Ask it to quote, not summarise. A summary of a retrieved chat is a second layer of compression on top of the retrieval. Asking for the exact decisions or constraints it found makes it easier to spot when it pulled the wrong conversation.
- Verify one detail. Pick something you know was settled in the old chat and check that the answer includes it. If it does not, the retrieval missed, and you should fall back to a manual method.
If your account does not offer this, or the setting is off, nothing in a new chat will reach the old one on its own. Do not rely on any article, including this one, for what is available on your account today. Your settings page is the authority.
Method 2: Find the Old Chat and Copy the Parts That Matter
The most dependable method needs no feature at all. Open the old conversation from your chat history, copy the parts you need, and paste them into the new chat.
The key word is parts. Pasting an entire long transcript into a new conversation recreates the problem you probably had with the original: a large context full of dead ends, superseded ideas, and scaffolding, where the parts that matter compete with everything else for attention. A long chat also uses up a lot of the new conversation's room before you have asked anything.
Copy the following, in roughly this order of value:
- The final state. The conclusion, the working version, the plan you settled on.
- The decisions. One line each, with a few words of reason.
- What was ruled out. The options you rejected and why. This is the part people leave out and the part that stops Claude proposing the same rejected idea again.
- Constraints. Anything an answer must respect to be useful.
- The exact artefacts. Code, wording, numbers, or data that need to be reproduced precisely rather than approximately.
If you are having trouble finding the old chat in the first place, the search and naming advice in How to Find an Old AI Chat applies directly to Claude's history. Searching for a distinctive pasted string usually beats searching for the topic.
Method 3: Ask the Old Chat to Write the Handover
If the old conversation is still open and usable, you can have Claude do most of the copying for you. Go back into that chat and ask it to write a handover for a new conversation: the goal, the current state, the decisions made, the options rejected with reasons, the constraints, and any open questions.
This is faster than writing it yourself and usually better organised. It has one important weakness. If the old chat was long, Claude may already have lost sight of its earliest messages, which is often the reason you are moving on in the first place. A summary written from a partial view can be confident and incomplete at the same time.
So read the handover before you use it. Check it against what you remember was decided early in the conversation. Add anything missing. The minute you spend correcting it is the whole value of doing it this way rather than trusting it blindly. A fuller walkthrough of moving from a long chat into a fresh one is in How to Continue a Long Claude Chat in a New Conversation.
Method 4: Put It Where Every New Chat Will See It
If you expect to come back to the same work repeatedly, copying a handover into each new chat gets tedious. The supported way to make context persist across chats in Claude is a Project. A Project's instructions and attached files are supplied to every conversation started inside it.
To use that for recall:
- Move the work into a Project if it is not in one already, so future chats start with the shared material.
- Attach the handover as a file, or paste it into a document you keep in the Project's knowledge.
- Update it at the end of each session that changed anything. This is the step that matters. A Project only knows what its files say, and files do not update themselves.
Chats inside the same Project still cannot read each other's transcripts by default. Only the Project's instructions and files are shared. So the handover file is not a convenience, it is the mechanism. A simple structure for keeping it current, a short decision log you rewrite each session, is in Claude Project Decision Log.
What About Deleted Chats?
A recurring search is whether Claude can remember a chat after you delete it. From your side, the practical answer is no. Once a conversation is deleted from your history, you cannot open it to copy from, it is not available as a source for any of the methods above, and a new chat will not be able to show it to you.
How long Anthropic retains data after deletion, and under what circumstances, is a policy question, not a memory question. It is governed by Anthropic's privacy policy and your account's data settings, and the details are the kind of thing that changes. Read the current policy directly rather than relying on a summary in a blog post. If your concern is that something should be gone, How to Make Claude Forget a Conversation covers what you can control.
The more useful lesson is about the other direction. If a conversation was worth recalling, it was worth saving before you deleted it, or before it scrolled out of reach in a long history. Deletion is only a problem for chats you did not keep a copy of.
What About Shared Chats?
Another variant is wanting to pick up a chat someone shared with you, or that you shared from another account. A shared link gives you a view of the conversation; whether and how you can continue it depends on how Claude currently handles shared chats. The details, and the workaround that works either way, are in Can You Continue a Shared Claude Chat?. The workaround is the same as Method 2: copy the parts that matter into a new chat of your own.
Why "Recall" Is the Wrong Mental Model
Most frustration with this comes from expecting recall to work like human memory, where you mention a conversation and the details come back. Claude does not work that way, and neither does any other assistant. Even when a product does offer chat retrieval, what actually happens is a search that pulls some text into the context, which Claude then reads like anything else you paste.
That has two consequences worth keeping in mind.
Retrieval can miss. A search can return the wrong conversation, the wrong part of the right conversation, or nothing. When it misses, Claude does not always say so. It may answer from whatever it did find, which is how you end up with a confident answer built on the wrong chat.
The transcript is rarely what you want. Even perfect retrieval gives you dialogue, and most dialogue is the process of getting to an answer. What you want in a new chat is the answer: decisions, constraints, and state. That is why a short, deliberate handover so often beats any form of automatic recall. It contains the conclusions without the scaffolding.
Making Future Recall Easy
The cheapest time to make a conversation recallable is at the end of it, while you still remember what mattered. A habit that takes a couple of minutes per important session:
- Ask for a handover before you close the chat. Same structure as Method 3. Correct it while the details are fresh.
- Save the conversation itself. Pressing Ctrl+S (Cmd+S on Mac) saves the page as HTML in your browser. That copy survives deletion, history clutter, and account changes.
- Rename the chat after its conclusion, not its opening question. "Chose Postgres over Mongo for reporting" is findable later; "database question" is not.
- Put durable context somewhere persistent. A Project file if the work lives in Claude, or a document you control if it spans tools.
The second step is where MindLock fits, if you want something more structured than a folder of saved pages. You import saved HTML from Claude, ChatGPT, Gemini, or Perplexity, as described in Importing Conversations, and the conversations are stored locally in your browser on the free tier. Semantic search (Ctrl+K) works across your saved conversations and memory documents, so finding the old chat about a topic does not depend on remembering its title.
MindLock can then distil the transcripts into memory documents and package the relevant ones into a context block you paste into a new Claude chat, as described in Generating Context. Nothing is captured automatically and nothing updates on its own: you choose which conversations to save, and memory documents change when you re-run distillation. Free-tier distillation runs locally through WebLLM on a WebGPU-compatible GPU; Pro adds cloud distillation and sync for €5 a month, as listed on the pricing page. The context block is plain text, so the same one works in ChatGPT or Gemini if the work moves there.
Common Mistakes
Typing "continue from last time". Claude cannot see last time unless something put it in the context. Always open with the actual content, not a reference to it.
Pasting the whole transcript. It recreates the long-context problem in the new chat and buries the decisions in the dialogue. Paste the state and the decisions.
Trusting a summary you did not read. A handover written by a chat that had already lost its early messages can drop the one constraint that matters. Read it first.
Leaving the Project file stale. A Project that supplies last month's plan to every new chat is actively misleading. Update the file at the end of any session that changed something.
Assuming retrieval worked. If you use a built-in feature to find an old chat, check one known detail before building on what it returns.
The Short Version
A new Claude chat can only work with what is in front of it, so recalling a previous conversation means putting the relevant parts of that conversation into the new one. Check your settings first in case your account can search past chats, and verify what it retrieves. Otherwise, copy the final state, decisions, rejected options, and constraints from the old chat, or ask the old chat to write a handover and correct it before use. For work you will return to, keep that handover as a Project file and update it each session.
Deleted chats cannot be recovered from your side, and retention after deletion is a policy matter to check with Anthropic directly. The way to avoid needing recall at all is to save conversations that matter, and their conclusions, before they are gone.