Prototypes
Start from the screen you actually shipped, not a blank artboard.
Read the prototypes docs
Olive
Codebuff
Attensira
Assemble
Opennote
Stratify
Gatekeep
Olive
Codebuff
Attensira
Assemble
Opennote
Stratify
Gatekeep
Olive
Codebuff
Attensira
Assemble
Opennote
Stratify
GatekeepThe workspace
Because the SDK already recorded your product, a prototype can start from the real screen — the real copy, the real states, the real density — instead of a fresh artboard.
Start from a capture
Pick a route and viewport from what was actually rendered to users, and edit that.
Wayback
Move back through captures by day to work against how the screen looked before a change, not only how it looks now.
Figma import
Bring a design in when the starting point is a comp rather than a shipped screen.
Select an element
Click a node in the preview to aim your next instruction at it, instead of describing which button you mean.
Preview or code
Switch between the rendered result and the markup behind it, and export the code when you want it elsewhere.
Multiple threads, one canvas
Several conversations can share the same prototype, so exploring an alternative does not mean starting over.
Handoff
Chat against the screen
Describe the change. The UI agent edits the captured screen in real time and the preview updates as it goes.
Apply or fork
Keep the version you like. In-progress edits are mirrored locally so a refresh does not cost you the work.
Give it to the coding agent
Hand the result off to be implemented against your repository as a branch and a pull request.
Keep going
Everything here reads from the same recorded session — there is nothing to stitch together between surfaces.
One SDK, one afternoon. We will walk your team through it on a call and leave you with the recording of your own product.