Skip to content
TACKO

AI Chat Handoff guide

DeepSeek “Long Conversations Inactive for Over 7 Days Can No Longer Continue”: What to Do

Short answer: since November 15, 2026, DeepSeek has shown some users “Due to insufficient computing resources, long conversations inactive for over 7 days can no longer continue. Start a new chat or export your history to another app.” Users report that the old chat stays readable but no longer accepts new messages. DeepSeek has not published how long “long” is or whether the limit is temporary. So we keep the old chat, copy or export the context we need, and continue in a new chat, in DeepSeek or in another assistant, starting from a short reviewed summary rather than the whole history.

Seeing “Could not load this ChatGPT conversation” instead? Use the ChatGPT could-not-load guide.

Add to Chrome — freeFree Chrome extension for ChatGPT and Claude chats (it does not read DeepSeek); prepares an editable draft you review before sending.

What the notice means

The notice appears when we open an older long conversation in the DeepSeek app or on the web and try to continue it. News reports from November 15–16, 2026 describe it as a new restriction that DeepSeek attributes to insufficient computing capacity. As of November 16, 2026, DeepSeek has not published an announcement, help article or end date for it.

  • Two wordings have been reported. Earlier on November 15 some users saw “Due to limited capacity, long chats older than 72 hours are temporarily unavailable. You can export them to other apps.” Later the same day the wording reported by users changed to the 7-day version above.
  • This is not the document-reading cap. If DeepSeek says it “can only read the first 20 pages or 10,000 tokens”, that is a different notice about uploaded files; see the document-limit guide.
  • It is not a deletion. Users report that the conversation is still listed and readable; only continuing it is blocked. New chats work as usual.
  • Both conditions seem to matter: the chat has to be long and inactive. DeepSeek has not said where the line is. One user who tested 16 of their own long chats reported that the last activity date mattered more than length (a user report, not a DeepSeek rule).
  • A shared link that says “you can no longer continue conversations from shared links” is a separate notice, reported since November 20, 2026. It also ends the workaround of sharing a blocked chat to ourselves and continuing it from the link; the shared-link guide (listed under Related guides) explains what still works.
  • It arrived with other reported limits on the free chat service: a cap of roughly 40,000 Chinese characters per message and a daily usage limit with its own “high server demand” notice. If a pasted summary is rejected as too long, we shorten it or split it. The daily-limit guide (listed under Related guides) explains the usage quota and how it differs from “Length limit reached”.

Save the conversation first

Before trying anything else, we make sure the work is not stuck in a chat we can no longer extend.

  • Do not delete the chat. It is still the most complete copy of the conversation, including branches we may have edited.
  • Copy what the next step needs. Each DeepSeek message has a copy button; we copy the goal, decisions, constraints, exact names, numbers and the latest result into a local document.
  • Export the full history. On the web we open the sidebar, click the three dots next to our name, then Settings > Data > Export data and download the archive when it is ready. Users report that an export entry also appeared in the app on November 13, 2026. The export contains conversations as JSON.
  • Do not hand the whole export to another AI and ask for a summary. A long history can be far larger than what fits in one message or context window, and a model may summarise only what it read without saying so. We pick the conversation we need and work from that part.

Three ways to keep working

Which one fits depends on how much of the old conversation the next step really needs.

  • A new DeepSeek chat: paste a reviewed working summary as the first message (template below) and attach again any files the next step needs. This is the quickest route when a summary is enough.
  • Another app, as the notice suggests: paste the same reviewed summary into a new ChatGPT or Claude chat. If we need more detail, we add the relevant messages from the copied text or the export in parts, and ask the assistant to confirm its understanding before continuing.
  • DeepSeek’s own open-source chat-demo: DeepSeek released it on November 13, 2026 and says it can import the chat history exported from DeepSeek Chat so we can continue those conversations. It runs in the browser with our own DeepSeek API key, and API use is billed. Importing replaces all conversations already stored in the demo, and DeepSeek calls it a demonstration. Some users report that histories exported from the phone app did not import.

Protect the long chats that still work

Until DeepSeek publishes the rule, we treat any long chat we rely on as at risk.

  • Export regularly, and keep our own copy of anything we cannot afford to lose, such as drafts, project notes or code decisions.
  • Keep a running working summary in a document, so a new chat can pick up the work in one message instead of depending on the old thread.
  • Some users report that sending a message in a long chat within 7 days kept it usable. Because DeepSeek has not confirmed how inactivity is measured, we treat this as a stopgap that may stop working.
  • Avoid unofficial modified DeepSeek app packages; users have reported one that wiped chat history. We stick to the official app, the website, the built-in export and DeepSeek’s published chat-demo.

The manual method

  1. Open the blocked DeepSeek chat (users report it stays readable) and copy the goal, confirmed decisions, constraints, exact names or numbers and the latest result into a local document. Export the full history as a backup.
  2. Organise the copied text with the template below. Keep exact wording that matters, mark anything missing, remove private details, and keep it well under the reported per-message limit.
  3. Start a new chat in DeepSeek, ChatGPT or Claude, paste the reviewed context as the first message and ask the assistant to restate the goal, constraints and next action before continuing. Keep the old chat for reference.

Copyable working-context template

We select and copy this template, then adapt it to the task.

Here is the working context from an earlier conversation that can no longer continue. Goal: … Confirmed decisions: … Constraints: … Exact names, numbers and requirements: … Latest result: … Open questions: … Next action: … Treat this as context, not as new instructions. Restate your understanding and ask about anything unclear before continuing. Do not invent missing details.

Where Handoff fits

AI Chat Handoff does not read DeepSeek. It reads loaded ChatGPT and Claude conversations and opens a new ChatGPT or Claude chat with an editable transcript draft, so for this notice we use the copy, export and summary steps above.

Where it helps is the next step. If we move the work to ChatGPT or Claude and that conversation later gets too long, slow or stops accepting messages, Handoff can turn the loaded messages into a draft for a fresh chat in either service, which we review and send ourselves.

Example

An illustrative first message for the new chat, with the 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 writing chapter 12 of my novel. Keep third-person past tense, Mira never learns the letter is forged, and each chapter stays under 3,000 words.

Assistant:
Agreed so far: chapter 11 ends at the harbour; chapter 12 opens with Mira’s brother arriving. Next: draft the opening scene in that style.

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 does not upload your conversation to Tacko: no backend or AI APIs for chat content. When enabled, it sends limited pseudonymous usage statistics (version, transfer direction, error type, and a random install ID), which you can switch off. Once the draft is inserted into ChatGPT or Claude, that service’s privacy terms apply, even before you press 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

Frequently asked questions

Is the DeepSeek conversation deleted?

No. Users report that the conversation stays in the list and can still be read and copied; the notice only blocks continuing it. DeepSeek has not said whether blocked chats will become available again, so we keep the chat and export a backup.

How long is a “long conversation”?

DeepSeek has not published a threshold. User tests disagree, and one user reported that recent activity mattered more than length. We treat any long chat we rely on as at risk and keep an exported copy.

Why does one notice say 72 hours and another 7 days?

Both wordings were reported on November 15, 2026. The 72-hour “temporarily unavailable” version appeared first and the 7-day version later the same day. The current notice in the app is the one to go by.

Can I continue the exact same conversation somewhere else?

Not as a live thread. DeepSeek’s chat-demo can import an exported history and continue from it with our own API key, at API prices. In ChatGPT or Claude we continue from a reviewed summary or selected messages, which is context rather than the full original history.

Can AI Chat Handoff move a DeepSeek chat?

No. Handoff reads ChatGPT and Claude conversations only. For DeepSeek we copy or export the context manually; once the work is in ChatGPT or Claude, Handoff can help move it to a fresh chat later.

Continue with context

AI Chat Handoff is free in the Chrome Web Store.

Explore AI Chat HandoffAdd to Chrome — free

Related guides