Stop describing UI fixes to Claude Code. Just click them

EditUI turns point-and-click feedback on a running website into structured context you can paste into Claude Code, Cursor, Codex or another coding agent.

Instead of typing “make the second button in the pricing section smaller and align it with the card above,” you click the exact element, attach the change, keep reviewing, and export the whole batch when you are done.

The export can include the selected DOM element, visible text, classes, computed styles, nearby elements, page URL and viewport size. That is more precise evidence than a screenshot or a vague description.

Visual review happens in the browser, but the agent needs enough context to find the right component. EditUI is the handoff layer between the two. It could help when reviewing a Base44 app, a landing page, a local dev server or a client site, and a nontechnical reviewer can collect changes without writing CSS selectors.

A practical test:

1. Open a non-sensitive app in a separate Chrome profile
2. Collect five specific visual changes and export them
3. Ask the agent which files it expects to change, and review the plan
4. Inspect the diff and compare before and after
5. Repeat with a text-only prompt and count clarifying questions and wrong guesses

The catch: DOM context can include page text, attributes and URLs, so avoid pages with customer data, credentials or financial details until you have reviewed its permissions. Precise context still does not guarantee a correct change. Check the diff and test desktop and mobile.