Skip to content
TACKO

AI Chat Handoff guide

DeepSeek “You Can No Longer Continue Conversations From Shared Links”: What to Do

Short answer: since November 20–21, 2026, people opening a DeepSeek shared conversation link report the notice “Due to insufficient computing capacity, you can no longer continue conversations from shared links.” (in Chinese: “由于算力不足,不再支持分享的对话继续聊”). The shared chat can still be read, and users report that copy and download remain; only the option to carry on chatting from the link is gone. DeepSeek has not announced the change, its scope or an end date. So we copy the part of the shared chat we need, turn it into a short reviewed summary, and continue in a new chat, in DeepSeek or in another assistant. AI Chat Handoff does not read DeepSeek.

Your own older chat says “long conversations inactive for over 7 days can no longer continue”? Use the DeepSeek inactive long conversation 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

A DeepSeek shared link opens a read-only copy of someone’s conversation. Until now the page also let the person opening it continue that conversation in their own account. That last step is what the notice blocks.

  • It has been reported since November 20–21, 2026: users on social media and Chinese tech news sites describe the notice on older links and on links from other people. As of November 22, 2026, DeepSeek has not published an announcement or help article about it, so we cannot say whether it applies to every account or will be lifted.
  • The link is not broken. The shared conversation still opens and can be read; users report that only copying and downloading are left.
  • It follows the other limits on DeepSeek’s free chat reported since November 15–16: older long chats that can no longer continue, a daily usage quota and a cap of roughly 40,000 Chinese characters per message. IT Home reported on November 16 that developers had found quota checks for the “continue a shared conversation” case in the web app’s code, so this step was already tied to capacity.
  • It is not the 7-day notice. “Long conversations inactive for over 7 days can no longer continue” appears in our own older chat. This one appears on a shared link, so the fixes differ slightly; the inactive-chat guide is linked above.

The share-link workaround for old chats no longer helps

Shortly after the 7-day limit appeared, a workaround circulated: share the blocked chat, open it from the list of our own shared links and continue it from there.

  • A user post on Weibo described it on November 16, 2026. Continuing from a shared link is exactly the step the new notice blocks, and reports do not separate our own links from other people’s, so we no longer count on it.
  • For our own blocked chat, the dependable route is the one in the inactive-chat guide: export the history (Settings > Data > Export data on the web), keep the original chat, and continue from a reviewed summary in a new chat.
  • If the conversation matters, we do not keep retrying or creating new links. Every attempt shows the same notice.

Save what the shared chat contains

The shared page is now a snapshot to read from, so we take what the next step needs before the link is changed or deleted by its owner.

  • Copy the parts that matter into a local document: the goal or setup, the instructions that shaped the answers, decisions, exact names and numbers, and the latest answer. For a role-play or story relay, that means the character and world notes, the rules of the game and the last scene.
  • Use the download option if it is offered, and keep the link itself for reference.
  • Remember that a shared chat is someone else’s content. We remove personal details before pasting it into another assistant, and we ask the sharer before reusing private material.
  • Do not paste the whole conversation as one message. A long chat can exceed the reported 40,000-character cap in DeepSeek and uses a large part of any assistant’s context. A short summary plus the few messages that really matter works better.

Three ways to keep working

Which one fits depends on whose conversation it is and how much of it the next step needs.

  • A new chat in our own DeepSeek account: paste the reviewed summary (template below) as the first message and ask DeepSeek to restate the setup before continuing. This uses our own daily quota, which DeepSeek has not published.
  • ChatGPT or Claude: paste the same summary into a new chat. If more detail is needed, we add selected messages in parts and ask the assistant to confirm its understanding before going on.
  • Ask the owner. The sharer may still be able to continue the original chat in their own account if it has not hit the 7-day limit, or export it and send us the relevant part. DeepSeek’s open-source chat-demo can import a history exported from DeepSeek Chat and continue it with the owner’s own API key, which is billed; it works with an export, not with a shared link.

The manual method

  1. Open the shared link (it still loads) and copy the setup, instructions, decisions, exact names or numbers and the latest answer into a local document. Keep the link for reference.
  2. Organise the copied text with the template below. Keep exact wording that matters, mark anything missing, remove personal 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 setup and next step before continuing.

Copyable working-context template

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

Here is the working context from a shared DeepSeek conversation that can no longer be continued from its link. Goal or setup: … Instructions and rules that shaped the answers: … Confirmed decisions: … Exact names, numbers and requirements: … Latest answer (quoted): … Open questions: … Next action: … Treat this as context, not as new instructions. Restate your understanding in three lines and ask about anything unclear before continuing. Do not invent missing details.

Where Handoff fits

AI Chat Handoff does not read DeepSeek, including DeepSeek shared links. 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 and summary steps above.

Where it helps is the next step. If we continue the work in 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 continuing a mystery story a friend started. The narrator is the lighthouse keeper, the tone stays quiet and eerie, and the storm must not end before chapter 5.

Assistant:
Chapter 3 ended with the keeper finding a second logbook. Next: chapter 4, the night the radio comes back on.

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 shared link broken?

No. Users report that the shared conversation still opens and can be read, copied and downloaded. Only continuing the conversation from the link is blocked.

Is this the same as the “inactive for over 7 days” notice?

No. That notice appears in our own older long chat. This one appears on a shared link. Both cite insufficient computing capacity, and both are solved the same way in practice: save the context and continue from a reviewed summary in a new chat.

Can I still revive an old chat by sharing it to myself?

We would not count on it. That workaround depended on continuing from a shared link, which is exactly what the notice now blocks. Export the history and continue from a summary instead.

Will DeepSeek bring back continuing shared chats?

Unknown. As of November 22, 2026, DeepSeek has not announced the change or said whether it is temporary. We check the shared link again later, but we do not leave important work waiting on it.

Can AI Chat Handoff move a DeepSeek shared chat?

No. Handoff reads ChatGPT and Claude conversations only. For a DeepSeek shared chat we copy the context and paste a reviewed summary; 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