Every turn in a project starts at the composer — the input at the foot of the project screen (and on the home screen for a new project). What you put in it decides the run more than any setting: this page covers its controls and how to brief the agent well.
The controls
- Input — the brief itself. One message per turn; Enter sends, Shift+Enter breaks a line.
- Agent chip — the CLI and model this turn runs on (Claude Code · Default). Click to switch agents or models per run.
- Effort — how hard the agent works the problem; Fast for iteration, higher for polish.
- Quality mode — Fast, Reviewed or Council — how the result is checked before it lands (see Quality modes).
- Attach — drop files or video references into the turn (see Attachments and video references).
- History — restore an earlier state of the project (see History and restore).
- Send — kicks the turn off. While a turn runs, it becomes Queue or Steer depending on the mode you pick (see below), with Pause and Stop beside it.
Brief anatomy
A good brief carries three things, usually in one or two sentences:
- What it is — "a landing page", "the pricing section", "an empty state"
- Who or what it's for — "for a coffee subscription", "for first-time users"
- The feel — "dark, editorial, confident type", "quiet, expensive-feeling"
Skip the spec-sheet details (exact pixels, exact hex) — the design system owns those decisions, and overriding them piecemeal produces worse results than a clear direction applied consistently.
Follow-ups are steering, not restarts
After the first turn the composer is a conversation. Each follow-up edits the same files in place — "swap the hero image for a product shot" or "make the nav feel lighter" — so you refine instead of regenerating. For a different direction entirely, branch a version or run variants instead.
Tip: When a fix is about a specific element, don't describe it — pin it. ⌥-click the element in the preview and the comment lands attached to the exact node. See Pick, comment and draw.
While a turn is running: Continue or Steer
You don't have to wait for a turn to end before saying something. While a turn runs, two chips sit above the input:
- Continue (the default) queues your message. The input reads Queue a follow-up — it sends when this turn ends… and the send button says Queue. Queued messages send in order once the turn finishes.
- Steer checkpoints the running task and resumes it with your instruction. The input reads Adjust the current task… and the send button says Steer. Completed work is kept; the instruction applies to what's left. The agent resumes with the original task and your new instruction side by side.
Steer needs text, since it has to say what should change. Anything attached in the composer rides along. If the pause or the resume fails, your instruction stays in the queue rather than disappearing.
Steer isn't the same as Pause. Pause checkpoints the job and frees its slot until you press Resume (text you type while paused becomes the resume note), and Stop cancels the turn. Steer pauses and resumes in one move.
Edit, apply or remove a queued message
Each queued message sits above the composer with Edit, Steer now and a remove button.
- Edit (or click the message) opens it in place with Cancel edit and Save. ⌘⏎ (Ctrl+Enter) saves, Esc cancels. The message keeps its position in the queue while you edit, and the queue won't send a message whose editor is still open.
- Steer now interrupts the running turn and resumes it with that queued instruction. The message keeps its own attachments. The composer's current attachments don't replace them, and the rest of the queue keeps its order.
- Remove drops the message from the queue.
Pins, comments and references ride along
Comments you placed with ⌥-click, Designer Talk notes and attached files are folded into the next brief automatically — the agent sees the steering in context, not as a bare instruction. Resolve or clear pins when a fix lands so the next turn isn't re-reading stale notes.