Annotate → Adjust: live, stacking text and style tweaks on selected elements, sent to the agent as one batch (Codex parity)

[rescuedfamily]

Problem

When I annotate an element in the browser preview, I can only describe the change ("bigger, less padding on the left, darker blue"). For visual tweaks, describing is slower and less precise than showing. It turns into several rounds of "a bit more… no, less," and each round costs a full agent turn.

Proposal

Add an Adjust panel to the existing Annotate comment box. With an element selected, I can:

• Edit the text inline (click and retype)
• Change color (text and background)
• Change font size, weight, and family
• Change padding and margin, each with separate top / right / bottom / left controls

Changes stack until I send

Adjustments preview live on the page only and persist while I keep working. I can adjust one element, move to another, and come back, and every change builds on the previous ones. The page always shows the combined result of my whole pending batch.

When I send, the agent gets one message with every annotation in the batch. Each has my comment (optional), the element, each property's old → new value, and a screenshot. The agent then makes the real changes in source, using the project's existing tokens or classes rather than hardcoded inline styles.

Why this shape

• Preview-only keeps T3 out of mapping DOM edits back to source files. The agent already does that well when given exact before/after values.
• Batching means one agent turn for a whole round of polish instead of one per tweak. Because the agent sees every change together, it can apply them consistently (e.g. one shared spacing value instead of five one-off overrides).
• It matches how Codex's version works ("Adjust" in Annotation mode), so the interaction is already familiar to people moving between apps.

Details worth deciding

• Reset for each property and for each annotation, plus a "discard batch" option
• What happens to pending previews when the page hot-reloads (see [Bug]: Design-mode annotation is lost when the page hot-reloads while typing #20726: today a reload clears an in-progress annotation)
• Keyboard-accessible controls with labeled inputs
• Optional: let a site register its own controls (e.g. design-token pickers), like Codex's Browser Annotation API

Related

#17059 (annotating inline HTML renders), #18627 (parent selection with \), #20726 (annotation lost on reload)