Prototypes

Take a screen a real user struggled with and redesign it with the UI agent.

Prototypes closes the loop that usually ends in a ticket. Instead of writing "checkout is confusing" and moving on, you take the actual captured screen and change it.

From a real screen, not a blank canvas

Because sessions are recorded as DOM rather than video, a screen someone actually saw can be lifted out and made editable. You start a prototype from a captured screen and chat with the UI agent to change it in real time.

That matters because the starting point is real: your live markup, your styles, the state that user was actually in — not a designer's reconstruction of it.

What it is for

  • Trying a fix for the friction you just watched in a replay.
  • Showing a teammate what you mean, on the real screen, instead of describing it.
  • Getting a concrete option in front of people before anyone opens the codebase.

Prototypes live in a grid with previews, so a set of options can sit side by side.

A prototype is a proposal

It is a design surface, not a deploy target. Nothing you change here reaches your users — it is for deciding what to build.

Start from the session that prompted it: find the moment in Replays, then bring that screen here.