Canvases
Documents, sheets, slides, code, boards and more — built inside the conversation.
A canvas is a working surface that opens beside the chat. Ask for a document and one appears; keep talking and it keeps changing. You're not copying output out of a chat window into another tool — the artifact is the conversation.
Available canvases
| Canvas | What it's for |
|---|---|
| Document | Long-form writing — drafts, reports, specs |
| Sheet | Tabular data, calculations, lists |
| Slides | Presentations |
| Code | An editor with a terminal and live preview |
| Preview | The running result of what's in the code canvas |
| Board | Task boards and kanban |
| Planner | Plans and sequenced work |
| Calendar | Scheduling and dated work |
| Image | Generated and edited images |
| Video | Generated video |
| Browser | Web pages pulled into the workspace |
| Database | Structured records |
| Workflow | Automations and custom agents |
Which canvases you can open depends on your plan — see Limits & quotas.
Opening one
You usually don't. Ask for what you want — "write me a launch plan", "build a landing page", "put those numbers in a table" — and the right canvas opens on its own.
To open one deliberately, use the canvas picker in the chat toolbar and choose a type.
Working in a canvas
Chat edits it. Ask for a change in the conversation and the canvas updates. You don't have to describe where — the model can see the whole artifact.
You can edit it directly. Type into it yourself. The next message picks up from what's there.
Changes are reviewable. When a model rewrites part of a canvas, the change is surfaced so you can accept or reject rather than discovering it later.
Several can be open at once. A code canvas and its preview, or a document and the sheet feeding it.
Real-time collaboration
On plans that include it, canvases are collaborative. Two people in the same canvas see each other's cursors and each other's edits as they happen, and so does the model.
Canvases and agents
Canvases are where the agents do their work. Chris builds in the code canvas, Peter runs the board and planner, Victoria fills the image and video canvases, Ava wires up workflows. Asking for the work is usually enough — the right agent picks it up.