Canvas and Inline Editing: Working On Documents and Code Live
The old side-panel Canvas is gone — but the ability to iterate on a draft with targeted edits instead of full rewrites didn't disappear, it moved inline.
What changed, and why it doesn't cost you anything
If you used ChatGPT a year ago and asked it to draft something long — a document, a piece of code — you'd have seen a separate panel open up alongside the chat: Canvas. It gave you a working surface where you could ask for a rewrite, a length change, a tone shift, or a fix, and watch that specific thing update without regenerating the whole document from scratch.
As of roughly late May 2026, that standalone side-panel version was retired from the current GPT-5.5 Instant and Thinking models. If that's the last version you remember, it's worth updating the mental model — not because you lost a capability, but because the capability moved, and knowing where it lives now is what lets you actually use it well.
Where the work happens now: inline blocks
Writing and coding work today happens directly inside the chat response, through what's called a writing block or a code block. You ask for a draft, and instead of a separate panel opening beside the conversation, the draft renders as a distinct block right there in the response — visually set apart from the surrounding chat text, but part of the same thread.
The capability you actually cared about with the old Canvas — targeted, in-place editing instead of full regeneration — is still there. You can ask for a rewrite of one section, a length change, a bug fix, a tone shift, and the block updates in place. You're not starting a new draft from zero every time you want one thing adjusted.
The one-sentence historical note
Here's the honest version of why this changed, in case you're ever explaining it to someone who remembers the old panel: a side-by-side Canvas had to be built and kept rendering consistently across every surface ChatGPT runs on — desktop, mobile, different browsers — and it didn't hold up everywhere the way it needed to. Inline blocks solve that by living in the exact same place the rest of the conversation already renders reliably. It's a practical engineering shift, not a capability downgrade.
There is a narrow exception worth knowing about: paid users can still reach the old side-panel experience for a limited time, but only through older, legacy models that are themselves being phased out. It is not the current mainstream workflow, and it's not worth building a habit around something being actively sunset.
Targeted edit vs. asking for a full rewrite
The single most useful skill in this lesson isn't knowing that blocks are inline now — it's knowing when to ask for a small, targeted change versus when to just ask for a fresh draft. These are genuinely different instructions, and picking the wrong one either wastes your time (re-explaining a whole document's context for a one-line fix) or wastes the model's effort (asking for a "small tweak" when what you actually want is a different direction entirely).
If the core of the piece is right and only a section needs work — a paragraph is too long, a function has a bug, the tone is slightly off in one spot — that's a targeted edit. Point at the specific thing, and let everything else stay untouched.
If you've read the draft and realized the whole approach is wrong — wrong structure, wrong angle, wrong argument — that's not a editing problem, it's a direction problem, and the right move is asking for a full regenerate with a clear explanation of what should be different this time.
What this lesson is not about
To be clear about scope: this lesson is about editing documents and short illustrative code snippets as a consumer feature inside ChatGPT — not about writing real software, connecting to APIs, or building anything that runs in production. If you've asked ChatGPT to help you sketch what a short script would look like as part of a writing task, that's the kind of code-block use this lesson covers. Programming as a discipline, with real projects and real tooling, lives in a different track entirely.
Building the reflex
The habit worth building here is small but compounding: when a draft comes back close-but-not-quite, resist the urge to either accept it as-is or ask for a total redo. Name the specific thing that needs to change, point at it, and let the inline block update in place. That's the entire skill — and it's the difference between three fast rounds of precise iteration and one slow round of "here's a completely new draft, please read the whole thing again."