Iterate in Canvas, Not in the Chat Scroll

Canvas opens a document or code file in a side panel you edit directly and in place, instead of regenerating the whole thing in the chat every time you want a change.

In a normal chat, each revision reprints the entire artifact and buries the previous version in scroll. Canvas keeps one living document, lets you target edits to a selection, and shows changes in context — so 'tighten this paragraph' or 'rename this function' stays surgical instead of rewriting everything.

Anything you'll revise more than once: an essay, a cover letter, a function, a SQL query. The moment you're on your second 'now change…', move to Canvas.

Short, single-shot answers you won't iterate on. Opening Canvas for a one-line reply is friction with no benefit.

Ask ChatGPT to open Canvas explicitly, then edit by selection:
"Open this in canvas."
Then highlight a section and instruct locally:
"Make just this paragraph more concrete — add a real number."
Or for code: "Add error handling to the selected function only."

Drafting a landing page, you select only the hero headline and say 'make this punchier, under 8 words' — Canvas rewrites just that line while the rest of the page stays put, so you can compare options without losing your work.

Use Canvas's targeted controls (adjust length, reading level, or add comments for code) as review passes: first get the structure right, then do a single 'tighten' pass, then a final 'proofread' pass — each as a discrete edit rather than one muddled request.

• Staying in the chat and regenerating the whole artifact for every tweak, losing prior versions in scroll.
• Giving a whole-document instruction when you meant one section — select first, then instruct.
• Treating Canvas as write-only; its real value is iterative, targeted editing.