Know When Plain Chat Beats Canvas
What it is
A judgment rule for when to open Canvas versus stay in chat: Canvas wins for a single long artifact you'll revise repeatedly; plain chat wins for questions, brainstorming, and short one-off outputs.
Why it works
Canvas adds an editing surface that only pays off when there's a persistent document worth editing. For quick answers, exploratory back-and-forth, or anything you won't revise, it's overhead — an extra pane and mode-switch for no benefit. Matching the surface to the task keeps you from forcing Canvas where a chat reply is faster.
When to use it
Deciding how to start a task: reach for Canvas when you can already see you'll iterate on one evolving piece of writing or code.
When not to use it
Brainstorming, asking questions, comparing options, or generating many short variants — all of which flow better in the chat stream.
Prompt
I want to <task>. Is this better done in Canvas or plain chat? Assume Canvas is worth it only if I'll revise one document across several turns. Recommend one and start there.Example
Drafting and refining a 1,500-word cover letter → Canvas; asking 'give me ten subject-line ideas' → plain chat, where the list scrolls naturally.
Common mistakes
- Forcing brainstorming into Canvas, where short variants feel cramped.
- Doing a long, multi-revision draft in chat and drowning in versions.
- Switching to Canvas for a one-line answer that never needed editing.