HelpComment, mark, and revise with AI

Comment, mark, and revise with AI

Attach feedback to an element or a visible region, choose when to send it, and verify what the agent actually changed.

Choose an element comment or a marked region

Comment is useful when the request belongs to a specific heading, button, image, or card. Mark is useful when you need to draw, frame several elements, or explain spacing with a screenshot. Edit changes the artifact directly; feedback asks the agent to change it.

Add a comment to an element

  1. Open the HTML file in Preview and choose Comment. Click the element on the canvas.
  2. Check the element label and outline so the request points to the right place. Write the expected change and the details to keep. Attach an image if a visual reference helps.
  3. Choose Comment to save the feedback, or Send to chat to hand it to the agent. Saving a comment alone does not start a generation task.
A precise element comment combines a location with a small, testable request.
Make this accent word coral. Keep its italic font, size, and position.

You can save an image-only comment when you have attached a reference. Add a short instruction whenever the intended change would otherwise be ambiguous. For an overall request, use a file-level comment from the comment panel rather than attaching it to an unrelated element.

Return to saved feedback

Open Comments in the preview toolbar to show saved markers, then click a marker to revisit its feedback. Choose View all comments to open the list. Select the comments you want the agent to address, then use Send to chat to submit them together. Select all includes every comment in the list. Expand the conversation panel first if it is collapsed.

A file-level comment applies to the whole artifact; an element comment carries a position. If a major redesign makes a marker lose its location, check the current file and attach the request to the correct element again.

  1. Review the selected comments before sending: Select all can include requests you do not want to process together.
  2. Use reply or ordering controls when provided to keep the feedback understandable. A marker’s number identifies its canvas location; rearranging the list does not necessarily renumber that marker.
  3. After Send to chat, check that the request reached the conversation and wait for the agent’s result. Saving or selecting comments alone does not change the artifact. A viewer may be able to comment but lack permission to start an agent task.

Mark a region of the preview

  1. Choose Mark in the preview toolbar. Use Box select to frame a region, Pen for a freehand indication, or Text to add a label.
  2. Add a short instruction. A box says where; the note says what should change. You can attach a reference image.
  3. Use Undo or Redo in the mark toolbar to revise the mark. In this mode, Cmd/Ctrl+Z undoes a stroke and Cmd/Ctrl+Shift+Z redoes it; Escape exits.
Mark captures a visual region. It does not itself edit the HTML.
ToolHow to make the feedback legible
Box selectFrame the affected region with enough neighboring context to identify it.
PenDraw a short line or outline to explain direction, spacing or a boundary; avoid covering the content to be changed.
TextAdd a short label beside the target; use the written instruction for the exact desired result.

Send now, draft, or queue

ActionUse it when
SendThe instruction is ready and you want the agent to work on it now
Add to inputYou want the screenshot and note in the composer before adding more context
QueueYou want to schedule the request behind an active task

After Add to input, expand the conversation pane if necessary and check the attached screenshot and text. Nothing runs until you send the message. If a task is already running, Send can be unavailable while the draft or queue actions remain available.

Review the draft before sending; Add to input is separate from Send.

Queue places the request behind active work; it is not confirmation that the change has already been made. Before sending another version of the same request, check the conversation and pending queue to avoid conflicting duplicates. After any of these paths, inspect the newly produced artifact rather than judging success from the submitted screenshot.

Inspect the changed artifact

  1. Wait for the agent to finish and open the changed file. Read the result in Preview.
  2. Check both the requested change and the details you asked to preserve. For a dynamic page, switch views or reload to make sure the new value remains.
  3. Return to the saved feedback to compare it with the result. Update a shared link only after checking the new version.
Manual edit: taste, was changed to craft, and survived reload. The comment request is separate.

The screenshot shows a saved manual edit, not a completed agent task. After sending your own feedback, inspect the new file and repeat the relevant interaction tests.

Local feedback and shared comments

Local comments, messages sent to the agent, and comments synchronized from a shared link are separate states. A viewer can have permission to comment without permission to edit the source or start an agent task. See sharing and collaboration for audience controls and publishing updates.