Mark up the running app. Hand your agent the batch.

Comment on the element itself.

Hold ⌥ and move the pointer over the page: the element under it is outlined. Click one to write a note on it. The mark carries that element to your agent, not a description of it.

The file and line come from whatever your dev tooling already emits: the Vue, React, Astro and Svelte inspectors, or a data-tailr-source you set yourself. With none of them present the mark carries its selector, its text and its route instead, which is the fallback rather than a failure.

⌥ click

Cross it out.

Hold ⌥ and right-click any element to stage it for removal. It goes red, and it stays on the page until your agent takes it out.

⌥ right-click

Rewrite it in place.

Hold ⌥, double-click any text, and type over it. It stays in the type the page already sets it in, so you are editing the words rather than a copy of them.

⌥ double-click

Point at where something should be.

Add Shift and the pointer becomes a dot you can drop anywhere, including on empty space. Ask for something new or simply note a spot.

⌥ ⇧ click

Ask for options and compare them live.

Set a comment to 2×, 3× or 4× and the agent builds that many versions at once. Hover a tab to see that version on the running page; click it to keep it. Turn the slider on instead and the agent makes the value itself adjustable, so you scrub it and keep the number you land on.

1× 2× 3× 4× slider

Send once.

Everything you staged goes as one batch. Marks live in the browser and span routes and pages, so a review of a whole flow persists. You can also continue marking while the agent is working.