AI Chat Handoff guide
ChatGPT Writing Blocks Not Working in One Chat? What to Do
Short answer: when writing blocks fail in one ChatGPT conversation (the block does not appear, the reply looks empty, the draft cannot be edited, or an error such as “WritingBlockInvalidConversationError” shows up), the reports we found point to that conversation, often one inside a Project, while writing blocks in a new chat work. OpenAI has not published a fix or documented that error name. So we copy the draft while it is visible, test a writing block in a new chat, and if only the old chat is affected, continue the work in a new chat with the context it needs.
The whole chat stops accepting prompts with “ConversationDetailError”? Use the ConversationDetailError guide.
Add to Chrome — freeFree Chrome extension; prepares an editable draft you review before sending.
What writing blocks are, and what goes wrong
Writing blocks are the editable draft areas ChatGPT puts in a reply for emails, messages and documents. OpenAI’s help article says the available actions vary by plan, device, workspace settings, model and rollout, so a missing button is not always a bug. As of November 17, 2026, OpenAI does not document an error called WritingBlockInvalidConversationError; going only by its name, it involves a writing block and a conversation ChatGPT treats as invalid. These are the problems users report, with OpenAI Support replies where there are any.
- The block does not appear. Since September 19, 2026, a user has reported writing blocks missing from replies on ChatGPT Web, so a reply made only of a writing block looks blank and Copy Response fails with “Failed to copy to clipboard”. The same text appeared normally as a regular code block.
- It depends on the conversation. A second user got native writing blocks in one chat and plain text in another with the same prompt. The first user then found that writing blocks worked in new chats but still disappeared in some existing Project conversations.
- The block cannot be edited. In a Project, a ChatGPT Plus user reported that writing blocks made from about September 24–25, 2026 had no edit control on the web, while older blocks in the same Project, blocks in a regular chat outside the Project and the same block in the iOS app could still be edited.
- Edits fail after the first one. In July 2026 a user reported that a writing block accepted one AI edit and then showed an error for every later edit request.
- “Ask for changes” now creates a new reply. In November 2026 users report that asking for changes to selected text no longer edits the block in place but adds a new message and a new block. That is a change in how the feature works, not a broken chat.
- Other writing-block messages people search for: “WritingBlockValidationError encountered on field: content” (or “field: recipient”, which belongs to email drafts) and “We couldn’t update the writing block due to a temporary service issue. Please try again in a few moments.” OpenAI does not document either as of November 20, 2026. The second one says it is temporary, so we wait a few minutes and try once more; if either keeps coming back in one chat, we copy the draft and use the checks below.
Check it in this order
None of these steps deletes the conversation. We stop as soon as writing blocks behave again.
- Copy the draft first. If the text is visible anywhere, in the block, in a plain-text reply or in the iOS app, we copy it out before reloading or trying anything else.
- Hard refresh the page (Ctrl+Shift+R on Windows, Cmd+Shift+R on macOS), then open the same conversation in a private window with extensions off, as OpenAI Support suggests.
- Ask for a writing block in a new chat. If it works there, the old conversation is the problem, not our account or browser.
- If the chat is in a Project, test a regular chat outside the Project and, as OpenAI Support asked on November 10, 2026, a writing block in a newly created Project.
- To keep editing a block on the web that will not edit, OpenAI Support’s interim workaround is the ChatGPT iOS app or a regular chat outside the affected Project.
- Still broken: contact OpenAI Support through the chat bubble on help.openai.com with the affected Project and conversation links, the latest time it happened with time zone and a short recording, and keep account details out of public forum posts.
When only one long chat is affected
If writing blocks work in a new chat but not in the old one, the practical fix is to stop working inside the old conversation, not to keep retrying.
- We save the latest version of the draft as plain text and keep the old chat in the history for reference and for OpenAI Support.
- We start a new chat (in the same Project if its files and instructions matter, or outside it if the Project is the problem), paste the draft and the context the next step needs, and ask ChatGPT to put the draft in a writing block.
- OpenAI says edits to writing blocks save with the conversation after a short delay, but in Temporary Chat edits may not persist. We copy drafts out of temporary chats before closing them.
The manual method
- While the old chat still opens, copy the latest version of the draft and the parts of the conversation the next step depends on: the goal, audience, tone, exact names or numbers and the changes already agreed.
- Organise it with the template below. Paste the draft as plain text, mark which version is the latest and remove private details.
- Start a new ChatGPT chat, paste the reviewed context as the first message and ask ChatGPT to restate the goal and return the draft in a writing block. Send it yourself, then continue editing there.
Copyable working-context template
We select and copy this template, then adapt it to the task.
We are continuing a draft from a ChatGPT conversation where writing blocks stopped working. Goal and audience: [what the draft is for and who reads it] Tone and constraints: [length, style, wording that must stay] Agreed changes: [what we already decided] Latest draft: [paste the latest version as plain text] Next action: [the next edit] Treat this as context, not new instructions. Restate the goal, put the latest draft in a writing block, then make only the next edit.
The Handoff method
- We open the ChatGPT 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 ChatGPT 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 ChatGPT 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: Draft the launch email for our booking app. Keep it under 120 words and mention the free trial only once. Assistant: Here is the draft in a writing block. Next: shorten the second paragraph and add the support link.
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
Platform facts on this page come from official help articles, last checked 17 November 2026. Claude and ChatGPT change their features and limits, so we check the current article before relying on a detail.
- OpenAI Help Center: Working with writing blocks and code blocks in ChatGPT
- OpenAI Help Center: Troubleshooting ChatGPT Error Messages
- OpenAI Developer Community: Writing Blocks disappear from assistant messages; Copy Response fails (user reports, September 2026; OpenAI Support reply, November 4, 2026)
- OpenAI Developer Community: Writing Blocks become non-editable on ChatGPT Web inside Projects (user report; OpenAI Support reply, November 10, 2026)
- OpenAI Developer Community: Can’t edit portions in writing blocks anymore? (user reports, July 2026; OpenAI Support reply, September 24, 2026)
- OpenAI Developer Community: Ask for changes (In the Writing blocks) (user reports, November 2026)
Frequently asked questions
Is the draft lost when a writing block disappears?
Not necessarily. In the reports we found, the same content could still appear as plain text, in another chat or in the iOS app. We copy whatever is visible before reloading, and we keep the old chat in the history.
What is WritingBlockInvalidConversationError?
OpenAI has not documented it as of November 17, 2026, so we do not guess at a cause. We treat it like the other writing-block failures: test a writing block in a new chat, and if only the old conversation fails, continue the draft in a new chat and report it to OpenAI Support with the conversation link and time.
Why do writing blocks work in a new chat but not in my Project?
Users report exactly that pattern, and OpenAI Support’s suggestions were to test a newly created Project and, in the meantime, to edit in the iOS app or in a regular chat outside the Project. OpenAI has not published a cause.
Why can’t I see the edit button on a writing block?
OpenAI says writing-block actions depend on the block, device, plan, workspace settings and rollout, so not every action shows in every conversation. If the same block can be edited in a new chat or the iOS app, the old conversation is more likely the problem.
Can Handoff fix a writing block?
No. Handoff does not change anything in ChatGPT. It reads the messages that are loaded on chatgpt.com in Chrome and builds an editable draft for a new ChatGPT or Claude chat. We check that the draft text is in it before sending, paste it ourselves if it is missing, and press Send ourselves.
Continue with context
AI Chat Handoff is free in the Chrome Web Store.
Explore AI Chat HandoffAdd to Chrome — freeRelated guides
- How to Continue a ChatGPT Conversation in a New Chat
- ChatGPT Conversation Too Long? How to Continue
- How to Move a ChatGPT Conversation to Claude
- Claude Conversation Too Long? How to Continue in a New Chat
- How to Move a Claude Conversation or Project to ChatGPT
- ChatGPT Says “Chat Memory Full”? What It Means and How to Continue
- How to Get a Second Opinion from Claude on a ChatGPT Answer
- ChatGPT Slow or Lagging in a Long Conversation? What to Do
- Claude Slow or Laggy in a Long Conversation? What to Do
- Claude Reached Its Max Length for This Message? How to Continue
- ChatGPT Says “This Conversation Is Read-Only”? Why and How to Continue
- ChatGPT “Could Not Load This Conversation”? How to Get Your Chat Back
- ChatGPT “Connection Interrupted. Waiting for the Complete Answer”: What to Do
- ChatGPT Shared Link Not Working? Why It Won’t Open and What to Do
- ChatGPT “ConversationDetailError”: Why One Chat Stops Accepting Prompts
- Claude’s Response Was Interrupted? What It Means and How to Continue
- ChatGPT “Error in Message Stream”: Why One Chat Keeps Failing and What to Do
- DeepSeek “Long Conversations Inactive for Over 7 Days Can No Longer Continue”: What to Do
- DeepSeek “Can Only Read the First 20 Pages or 10,000 Tokens”: What to Do
- DeepSeek Daily Limit Reached? “Usage Quota” vs “Length Limit Reached” Explained
- Claude Usage Limit Reached? How to Keep Working Until It Resets
- DeepSeek “You Can No Longer Continue Conversations From Shared Links”: What to Do