Checkpoints and design review
How larger builds pause for your review, and how design quality is enforced.
Why checkpoints
Larger projects don't build in one long run — the plan splits into checkpoints, each a coherent slice of the product. The agent builds the first checkpoint, pauses for your review, and continues when you start the next one. You always see and steer the work in progress instead of waiting for a single big reveal.
Reviewing a checkpoint
The workspace shows the setup roadmap with each checkpoint's status. When one is ready, look through the built pages in the live preview, ask the agent for any changes in chat, and choose Start next checkpoint when you're happy. The roadmap tracks pending, building, awaiting review, and accepted stages.
Design review
Every build is checked against your brief: agents capture evidence of the built pages and verify each promised feature works. By default there is no separate design judge — the agent ships its first honest build. Turning on strict design review (below) adds the judge and rework cycles.
Strict design review
When you've attached page designs, the Plan step offers a strict design review switch (off by default). With it on, the agent keeps reworking each checkpoint until the built pages match the designs you agreed on — the judge re-scores after every pass.
Strict review means agents iterate until the build matches the design — expect additional build time and cost at every checkpoint.