Keep the original transcript and files, then prepare a task-specific handover using the manual builder or thredly’s supported-file importer. Select the relevant conversation and branch, review the current goal, decisions, output and next action, and paste the checked brief into a new Claude chat. Claude’s native memory import is a separate option for remembered context, not a complete transcript archive or automatic sync.
Claude
How to Continue a Claude Conversation in a New Chat
To continue a Claude conversation in a new chat, paste a reviewed handover of the objective, constraints, decisions and current work, then give the next task. Use the manual template below if you need a fresh start. Claude can manage long conversations automatically on eligible setups; check those options before leaving a working thread.
Moving from ChatGPT? Follow the ChatGPT-to-Claude handover workflow.
Last reviewed: 15 November 2026
Claude Code has separate session commands
This guide covers Claude web and app conversations. To start a fresh Claude Code conversation, run claude without a resume flag, or use /clear in the current CLI session. Anthropic says /clear starts a new conversation with empty context while preserving the previous conversation for resuming. Use claude --continue for the most recent conversation in the current directory, or claude --resume to resume a chosen session. /compact summarizes the current conversation to free context; it does not start a fresh session. See Anthropic’s CLI reference and slash command reference.
Check Claude’s native context-management options first
On paid Claude plans with code execution enabled, automatic context management summarizes earlier messages as a chat approaches its context limit. Anthropic says the full history is preserved and most conversations can continue, although rare limits remain. Context capacity varies by model and product; this guidance is for Claude chat, not an API or Claude Code command. See Anthropic’s context-management guidance.
Claude also offers memory and, on paid plans, search of earlier chats. Availability and organization settings affect these features. They can bring useful context into new conversations, but a reviewed handover lets you choose the exact working brief for one task. See Claude’s chat search and memory guide.
Check which limit Claude is showing. A conversation-length limit concerns the context in one chat; use Claude's available context-management options or move the relevant work into a fresh chat. A session or weekly usage limit applies across your account, so starting another chat does not reset it. Check the reset or usage options shown in Claude. See Claude usage and length limits.
Claude says a chat is available in the new experience
If Claude says, “This chat is available in the new Claude experience. Reopen it there to keep going,” that is consistent with Anthropic’s rollout of one conversation experience for chat and Cowork. Anthropic’s help does not document that exact banner, so it cannot confirm why a particular chat shows it. The guide says chats and longer Cowork tasks now share Recents, and existing Cowork tasks carry over and open as before. Open Recents in the new experience and select the chat or task. If it is missing or will not reopen, preserve any content you can still access and contact Anthropic support; do not assume a new chat or export can restore it. The new experience is rolling out gradually on Pro, Max and Ultra; Team and Enterprise availability depends on the organization enabling it. See Anthropic’s Claude Chat and Cowork guidance.
How to transfer ChatGPT work to Claude
Choose what you need to move: remembered preferences, an original record, or the current state of one task. A memory import, a transcript backup and a reviewed handover serve different purposes.
Personal context: Claude’s native memory import
On the web or Claude Desktop, follow Anthropic’s memory-import instructions: run its prompt in ChatGPT, review the reply, then use Settings → Your Claude → Start import (Settings → Memory in the older layout) and Add to memory. Review the resulting entries. Some organizations have a legacy flow. Anthropic calls import experimental and says it can miss information, particularly personal details unrelated to work. This transfers remembered context; it is not a transcript archive or ongoing chat sync. Documentation checked 12 November 2026.
Original record: keep a transcript backup
Request an eligible ChatGPT data export, download it and check that the conversations you need are present. Keep that original separately and save essential files with their versions. A handover selects useful context; it does not replace the full record.
One task: prepare a reviewed handover
Carry over the current goal, constraints, decisions, latest output, unresolved questions and next action. Include rejected or superseded ideas only when Claude needs to know why they should not be repeated. Check exact names, numbers, quotations and code against the source.
Continue one task in Claude
- Choose the ChatGPT conversation and the branch that contains the work you want to continue. Keep the original transcript and any essential files available for checking.
- Expand the free manual handover builder below and fill it from your source. For an automated draft instead, sign in to the existing thredly web app and choose Import file for a supported text export. Select the conversation and Conversation branch when offered, then review the preview and warnings before applying the text. Alternative branches are not merged. Choose Create summary to draft the handover.
- Review the brief against the selected source. Restore missing constraints or current outputs, flag uncertainty, and remove anything you cannot share. Supply required original files separately in a format Claude accepts; a text brief does not carry the attachments.
- Paste the reviewed handover into a new Claude chat. Ask Claude to restate the goal and constraints and flag missing information before continuing. End with the exact next task. This supplies new context; it does not import the original thread or synchronize future messages.
The manual builder formats your entries in this browser without an account or AI. Importing in the web app only fills the input; it does not create a summary. If you choose Create summary, the confirmed text is sent for processing and the draft still needs review. Check private information and permission to share before either sending text to thredly or pasting it into Claude.
If Claude cannot compact the conversation further
If the chat reports that it cannot be compacted further and no longer accepts messages, use a fresh chat with the working context you can still access. Automatic context management can encounter rare failures, including very large first messages or system errors, as described in Anthropic’s guidance above. A handover is a fallback for continuing the work, not a guaranteed repair for the original thread.
If Claude can still respond, ask it for a handover and check the result. If it cannot, use readable messages, saved outputs or an eligible Claude data export to fill in the template below. thredly can only summarize text you supply or that its supported extension can access; it cannot recover an inaccessible chat.
How to continue a Claude conversation in a new chat
- 1
Open the original Claude conversation
Find the chat you want to continue and identify the work that must carry over.
- 2
Create a structured handover
Write one manually, or use thredly in the web app or optional Chrome extension to create one from the conversation.
- 3
Review the handover
Check for missing instructions, constraints, decisions, current outputs, and anything Claude should not repeat.
- 4
Start a fresh Claude chat
Open a new conversation rather than adding a large transcript to the old one.
- 5
Paste the handover first
Make the handover the first message so the new chat has the working context before it starts.
- 6
State the exact task to continue
End with a direct next action, such as “continue by reviewing the open issues and drafting the next section.”
Manual Claude handover template
A manual handover can be enough when you need to move quickly. Copy this template, fill in only what matters, and paste it into the new chat.
Copy this template, then replace each prompt with the current details from your conversation.
Objective What I am trying to achieve: Background The context the new chat needs: Instructions and constraints Rules, preferences, requirements, and things to avoid: Decisions made What was chosen, and why: Rejected approaches What was ruled out, and why: Work completed Useful drafts, code, research, or outputs so far: Current output or version The latest state to work from: Open issues Questions, risks, or missing information: Next action Continue by doing this:
Build a free manual handover Fill in the essentials, then copy or download
Write your next chat’s working brief
This builder formats text in your browser. It does not upload or save your entries. Copy or download before leaving. It does not check your sources or use AI.
Objective and next action are required. Add other details only when they matter; empty optional sections are omitted. Each field accepts up to 10,000 characters.
Have a long source conversation? thredly can optionally draft an automated summary for you to review. Try an automated summary. Free account required; this manual builder stays free without an account.
What makes a handover useful?
Treat it as a working brief, not a transcript. Keep the details that change what the next chat should do: the objective, current version, decisions that should not be reopened, and the task that remains.
Check the handover against your sources
Try the built-in continuation options described above first. If you still need a separate brief, you can write and check it yourself. Keep the original text beside you: a smooth summary can still contain the wrong name, an old date or a decision nobody approved.
- Save the readable messages and latest work you need. Label useful excerpts S1, S2 and so on. Keep sensitive details out unless the next task needs them.
- For each detail that changes the next task, fill in the worksheet below. Copy names, dates, times, units and amounts precisely. Keep an unspecified year or time zone marked unknown.
- Find the explicit correction or approval before treating a newer statement as settled. Record which earlier choice it replaces. Keep suggestions separate from decisions.
- Check every current claim against its source. If the source is missing, say so. Ask the next chat to resolve essential gaps before doing more work.
Task to continue: Latest output or version: Sources supplied: Sources missing: Repeat for each important fact, instruction or decision: - Current detail: - Status: confirmed / proposed / rejected / superseded / unknown - Source ID and exact supporting words: - Earlier detail replaced, if any: - Correction or approval source: Open questions: Exact next action:
Read this brief and the supplied excerpts. Restate the next task and flag conflicting or missing information before continuing. Keep proposals separate from confirmed decisions. Do not invent details or reopen a rejected choice without asking.
This worksheet checks the material you have. It cannot recover inaccessible messages or prove that missing context has been preserved.
Example of rebuilding a brief after a recap drops details
Invented teaching example. These saved excerpts illustrate a review method, not a claim about how often Claude compacts or what thredly produces.
Suppose you saved these messages before a later recap became incomplete. Use the messages to repair the brief rather than treating the recap as the whole record.
Original excerpts
S1 · User
Draft a workshop brief for the library team. Use a 45-minute session, with Casey as reviewer.
S2 · User
Correction: the session is 30 minutes, not 45. Ari replaces Casey as reviewer. Keep both changes in the next draft.
S3 · User
Use 21 October 2026 at 14:00 Europe/London as the proposed slot. It is not confirmed. Do not send invitations.
S4 · User
The opening paragraph is approved: 'This workshop introduces a practical method for checking AI-generated summaries.' The agenda is still unfinished.
S5 · User
Keep the approved opening. Next, draft a 30-minute agenda for Ari to review.
A later recap to check
Continue the 45-minute library workshop. Casey is reviewing it. The session is confirmed for 21 October at 14:00. Send invitations after drafting the agenda.
Checked handover
Task: draft the unfinished workshop agenda for the library team [S1, S4, S5]. Duration: 30 minutes [confirmed: S2, "30 minutes, not 45"; reinforced by S5]. Forty-five minutes is superseded. Reviewer: Ari [confirmed: S2, "Ari replaces Casey"; reinforced by S5]. Casey is superseded. Suggested slot: 21 October 2026, 14:00 Europe/London [proposed, not confirmed: S3]. Approved opening: "This workshop introduces a practical method for checking AI-generated summaries." [S4]. Keep it unchanged [S5]. Not supplied: venue, attendee list and confirmation of the proposed slot. These are not needed to draft the agenda; leave them unresolved. Next action: draft a 30-minute agenda for Ari to review [S5]. Do not send invitations [S3].
A saved recap is useful, but it can miss an earlier correction. Check it against readable originals or a checkpoint you have already verified. If only the later recap were available, you would need to mark its reviewer and duration unverified rather than claim to have checked them against the original decisions.
How thredly handles the handover
Turn the old Claude thread into a handover you can inspect
The manual method above remains available. thredly automates the first draft, then leaves you in control of what the new chat receives.
- 1. Add the conversation
Paste your Claude conversation into the web app, or use thredly inside the supported chat.
2. Review the handover
Check the objective, instructions, decisions, current work and next action.
- 3. Continue in a fresh chat
Paste the reviewed handover into a fresh Claude chat, then state the exact task to continue.
Why not paste the entire conversation?
Keep the full transcript as a record, but select the current decisions and instructions for the next task. Our AI chat portability case study shows why transferring text and reconstructing the current state are different. Check the handover against your source.
What thredly preserves
A thredly handover is designed to preserve goals, instructions, constraints, decisions, rejected approaches, progress, important outputs, open questions, and next steps.
Claude Projects versus a conversation handover
Claude Projects can organise reusable project knowledge and supporting material. A structured handover is intended to transfer the working state of one specific conversation: its objective, constraints, decisions, outputs, and next action. They can be useful in different situations; choose the approach that fits the work you need to continue.
Related pages
Claude guide
Broader Claude guidance for saving and managing conversations.
Research handover template
Carry checked findings, source references and unresolved research questions into your next chat.
AI coding handover template
Preserve the current code version, failed attempts and checks when restarting a coding task.
Conversation too long
Platform-neutral help for long AI conversations.
Summarize an AI conversation
General guidance for turning an AI chat into a useful summary.
Continue a ChatGPT conversation
The equivalent workflow for a long ChatGPT conversation.
Frequently asked questions
Create the handover before you start the new chat
Keep the important working context clear, review it once, and give the fresh chat a precise next action. Use the web app or the optional Chrome extension when you want thredly to create the structured handover.
