Agent
Planning & execution
For larger jobs the Agent may plan first, then execute step by step. Pages render in parallel; you can run only part of a plan. Learn when your confirmation is needed and current limits.
Multi-step plans
When you ask for work that spans several stages—organize sources, draft an outline, render the first slides—the Agent may outline a plan in chat first, then read and write across brief, outline, design, and canvas. You can ask for a plan before execution, reprioritize mid-flight, or say “run only the first two steps.”
- Plans appear as task cards so you can see what the Agent intends to do.
- You can run part of a plan—e.g. “Do not render any slides yet.”
- Refine scope anytime: “Only change the title on slide 3.”
- Cross-tab work is common: update the outline from the latest brief, then render specific pages.
Parallel rendering
When generating many slides from an outline, pages render in parallel so you wait less. Finished slides show up in the canvas thumbnail rail first—you can preview and flip through while the rest completes.
- Thumbnails appear on the canvas as each page finishes.
- While the Agent is generating or batch-rendering, some canvas actions (e.g. drag reorder) may pause—wait until done, or describe the new order in chat.
- Output mode (code vs image) is chosen at project creation and shapes how the Agent renders and how you revise later.
- Concurrent batches per project depend on your plan: Free allows one; paid plans up to four. Plus / Ultra get higher queue priority. See Pricing.
When you confirm
Not every step runs to completion without you. These cases usually need a choice, approval, or explicit go-ahead:
- New project: the Agent may ask about topic, audience, aspect ratio, and output mode (Clarify).
- Multi-step plans: review the plan first, or approve only some steps.
- Export: when you ask for PDF or PPTX in chat, the Agent starts export—you confirm before the browser downloads.
- Share links: not created via chat; use Share in the canvas header.
Limits
- Closing or refreshing the page does not interrupt the current chat turn—streaming reply, parsing documents, drafting an outline all keep running on the server, and you see the saved result when you return. If you reopen or switch tabs mid-turn, the in-progress output replays from the start and keeps streaming. Only the ■ button beside the composer stops the turn.
- Batch slide rendering continues on the server: when generating many pages from an outline, chat may finish first; the canvas tray and composer show background rendering or queued status—reopen the project to resume progress.
- Switching Brief, Outline, Design, or Canvas inside the workspace is usually fine.
- Models differ in speed, quality, and Credits—see Choose a model.
- Canvas refine and right-rail Tweak do not use the Agent or chat allowance.
Example prompts
Parse the PDF in my sources, organize brief → draft a 10-slide outline → render the first three slides—plan first, then execute step by step after I confirm.
The Agent shows a plan card, then runs each step.
Run only the first two steps—organize brief and draft the outline. Do not render any slides yet.
Generate all slides from the outline.
Pages render in parallel; thumbnails appear as each finishes. Batch renders continue on the server—reopen the project to see progress.
Update the outline from the latest brief, then re-render only slides 2 and 3—leave other slides unchanged.
Export this deck as PDF.
The Agent starts export; your browser downloads after you confirm. See Export.