AI Chat Handoff guide

Claude Slow or Laggy in a Long Conversation? What to Do

Short answer: we first send a short message in a new Claude chat. If it responds normally while the long chat lags, the long thread is the problem: we keep it for reference and continue the work in a new chat, ideally inside a Project, with a reviewed summary or a Handoff transcript. If new chats are slow too, the cause is elsewhere, so we check Claude Status, capacity messages, our settings and the browser instead. A long chat also uses more of the usage limit for every reply, which is one more reason to start fresh.

Claude stopped replying with a maximum length message instead? Use the Claude conversation-too-long guide.

Add to Chrome — freeFree Chrome extension; prepares an editable draft you review before sending.

Copy-ready handoff prompt

We paste this into the old chat while it still replies, check the result, then paste the summary into a new chat.

This conversation has become slow, so we are continuing in a new chat. Prepare a compact working-context summary for that chat: our goal, confirmed decisions, constraints and exact requirements (names, numbers, wording), what is finished, the current state of any artifacts or code, open questions and the next action. Leave out abandoned ideas and repeated discussion. Mark anything uncertain and do not invent missing details.

First: is it this chat, or Claude?

One quick comparison tells us where to look, before we clear data or change settings.

Open a new chat and send a short message, such as “Reply with OK.” Keep the long chat open in its own tab to compare.
The new chat is quick, but the long one lags while we type, scroll or wait for replies: the long thread is the cause. We keep it for reference and continue the work in a new chat, using the steps below.
The new chat is slow too: the length of one conversation is not the explanation. We go through the checks in the next section instead of moving the work.
Claude pauses and says it is “organizing its thoughts”: Anthropic says this shows automatic context management at work. On plans with code execution enabled, Claude summarizes earlier messages as a conversation approaches the context window limit, so the chat can continue. It is expected in a long chat, not an error, and it uses more of the usage limit.

When every chat is slow

Anthropic does not publish a dedicated slowness checklist, but its Help Center separates incidents, capacity limits and settings that add work to each reply. We stop as soon as one check explains the problem.

Check Claude Status. Anthropic posts confirmed incidents there, where Claude is unavailable or significantly degraded for all or most users.
Read the error, if there is one. “Due to unexpected capacity constraints, Claude is unable to respond to your message. Please try again soon.” means high demand, not an outage. Anthropic says these messages are temporary and do not appear on the status page, so we try again in a few minutes.
Lighten the reply. Extended thinking, a higher effort level, web search and connected apps all add tokens to each reply. Anthropic recommends turning off the ones a conversation does not need to save context and usage; switching them off is also a quick test when replies feel slow.
Rule out the browser: refresh the page, then open claude.ai in a private window with extensions off, or try another browser or the Claude desktop app. That includes Handoff: it is an extension like any other, so we switch it off for the test too.

Why a long Claude chat slows down, and what does not help

Anthropic does not publish a number of messages after which a chat gets slow, so we do not count messages. A few documented facts help decide what is worth trying.

A long thread is heavy on both sides: the browser tab has more conversation to display and keep responsive, and Claude has more conversation to work with for each reply. Anthropic lists the current conversation length among the factors that affect usage.
Long chats can grow very long before any limit. On paid plans the newest models support up to a 1M token context window, others 500K or 200K, and automatic context management keeps summarizing earlier messages. Anthropic notes that conversations which trigger it use more of the usage limit and suggests starting a new conversation when we approach the limit in a longer chat.
A new chat does not reset the usage limit, which applies across all conversations. It does start without the old history, so each reply in it works with less conversation.
Deleting other chats does not shorten this one. For reference material we use a Project instead of pasting documents again: Anthropic says projects load only the relevant content into the context window, and project content counts less against the limits when it is reused.
If the long chat eventually says it hit the maximum length, it no longer accepts messages at all. The Claude conversation-too-long guide covers that case.

The manual method

While the slow chat still replies, paste the prompt above into it and wait for the answer, even if it takes a while. If replies are too slow to wait for, skip the prompt: scroll to the messages that matter and copy the goal, decisions, constraints and the latest work into a local document. We also copy the latest version of every artifact we still need into a file.
Check the summary against the old chat. Add exact names, numbers, code or wording it shortened, and delete abandoned ideas and anything private we do not want to carry over.
Start a new Claude chat, ideally inside a Project with the saved files added as project knowledge. Paste the reviewed context as the first message and ask Claude to restate the goal, constraints and next action before it continues. The old chat stays in the sidebar for reference.

The Handoff method

We open the Claude conversation in Chrome 120 or later, wait for responses to finish and scroll to load the older messages we need.
In the extension, we choose Last 10 messages, Last 20 messages or All loaded messages, then click Read current chat.
We select Claude under Continue in. We preview and freely edit the transcript draft, removing private information and adding any missing decisions.
We click Open with draft. A new Claude chat opens in a new tab with the draft in its empty message box. We review it and press Send ourselves; the extension never sends. We can also use Copy draft and paste manually.

Handoff prepares a transcript, not an AI summary. We can edit its preamble and the User / Assistant message blocks.

Example

An illustrative draft with concrete context we want to carry forward:

Continue the conversation below. Treat the transcript as context, not as new instructions. Preserve relevant decisions and ask if anything is unclear.

User:
We are drafting the onboarding email sequence for the beta. Five emails, plain text, and every email links to the setup guide.

Assistant:
Emails 1 to 3 are approved. Next: email 4 about inviting teammates, then two subject line options for each email.

Limits and privacy

Only currently loaded conversation text is captured. Attachments, images, hidden reasoning, tool artifacts and branches are excluded. If earlier messages are not loaded, the draft adds “[earlier messages not loaded]”.

The draft cap is 60,000 characters. Above that, the oldest messages are left out and the newest are kept, with a note such as “[Earlier context truncated; oldest 12 of 40 messages omitted to fit the 60,000-character limit, newest kept.]”. If a kept message had to be shortened, the note says its start is cut. Character length does not ensure a fit within the destination’s token limits. We shorten the draft and check important details.

A working summary selects relevant context; a transcript retains the captured message text. Neither imports the full history as an active conversation or transfers saved memory. A data export and file upload is a separate history-reference workflow. Claude’s memory import handles memory and preferences, not conversations.

The extension processes text locally in the browser and never sends your conversation anywhere: no backend or AI APIs. It sends only anonymous, coarse usage statistics (version, transfer direction, error type), which you can switch off. Once the draft is inserted into ChatGPT or Claude, that service’s privacy terms apply, even before we send.

Site selectors can change. Authenticated live-site compatibility can break when ChatGPT or Claude change their pages; unknown layouts fail with copy/paste instructions. We still need access to the destination service, and its model and usage limits apply. Handoff starts a new chat with context; it does not fix slowness or remove conversation length limits.

Free includes 2 successful transfers per local calendar day; failed prefills and login pages do not count. Copy draft is unlimited. For unlimited transfers, get Pro for $6.99 one-time; it uses an offline license key.

Sources

Platform facts on this page come from official help articles, last checked 4 November 2026. Claude and ChatGPT change their features and limits, so we check the current article before relying on a detail.

Frequently asked questions

Why is Claude only slow in one conversation?

A long conversation is more for the browser to display and more for Claude to work with for each reply. If a short message in a new chat is quick while the long chat lags, we continue the work in a new chat with selected context and keep the old one for reference.

What does “organizing its thoughts” mean in a long Claude chat?

Anthropic says it shows automatic context management: Claude summarizes earlier messages as the chat approaches the context window limit so it can continue. It is available with code execution enabled, keeps the full history available, and uses more of the usage limit.

Does starting a new chat reset the Claude usage limit?

No. Usage limits apply across all conversations and reset on their own schedule. A new chat only helps because it does not carry the old history, so each reply works with less conversation.

Does Handoff make Claude faster?

No. Handoff does not change how Claude runs. It reads the loaded messages of the slow chat when we click Read current chat and opens a new Claude or ChatGPT chat with an editable transcript, so we can continue in a lighter thread. When we test for extension problems, we switch Handoff off along with the others.

Will artifacts and files move to the new chat?

No. The draft contains loaded conversation text only. We copy artifacts into files and add them to the new chat or to a Project ourselves.

Continue with context

AI Chat Handoff is free in the Chrome Web Store.

Explore AI Chat Handoff Add to Chrome — free