Annotate the visible design with pen, boxes, arrows, text, picks, notes, and attachments, then send the marks and rendered screenshot together as one actionable request.
Where: Designer top bar → Draw.
Key ideas
- Drawing has separate history: Marks belong to the Draw layer and have their own undo/redo. They do not become page elements or consume the page document’s undo stack.
- Send preserves visual and structural context: One Send creates a real assistant turn containing the note, structured mark descriptions, a screenshot of the visible band with ink, and every attachment. The screenshot is first so the assistant sees what the marks reference.
- Attachments match chat: Draw accepts the same image, video, audio, PDF, and document channels as the composer. A badge and marks list expose the complete outgoing packet.
Steps
- Choose Draw, then select Pen, Box, Text, Arrow, or Pick.
- Place one clear mark around each requested change.
- Use Draw undo/redo to correct markup without undoing document edits.
- Review the marks list and add a shared note describing the desired result.
- Attach any reference images, clips, audio, PDFs, or documents for the same request.
- Choose Send. Designer creates one turn with the note, structured marks, visible-stage screenshot, and attachments, then exits Draw.
- Review the result against every mark. Use Clear instead when you want to discard the markup and exit.
Draw tools
- Pen — freehand emphasis
- Box — rectangular region
- Text — located note
- Arrow — directional callout
- Pick — rendered target
What Send includes
- Shared note, or the default apply-the-marked-changes request
- Structured descriptions of every mark
- Visible page-band screenshot with ink as first image
- Every image, video, audio, PDF, and document attachment
Failure-safe behavior
- Screenshot capture failure does not discard the note, marks, or attachments.
- Draw and document histories remain separate.
- Send exits after creating a turn; Clear exits without one.
Tips
- State the result in the note; marks identify where, but should not be expected to explain why.
- Keep the marked area visible before sending.
Limitations and important notes
- Marks are review context, not persistent vector elements.
- The screenshot covers the visible band, not content far outside the viewport.
- The active assistant mode, role, and tool table still govern edits.
Troubleshooting
Undo changed marks but not the page.
That is expected. Leave Draw and use page undo for document changes.
A mark below the fold was missed.
Bring the region into view before Send or split the review into smaller visible batches.
Send continued after screenshot capture failed.
Designer preserves the note, structural marks, and attachments; retry only when rendered appearance is essential.