What happens inside a version

A version is a numbered iteration of your project (V1, V2…). It lives inside a project, so create one first if you have not. It is where the agent builds. A project has at most one version in development at a time. Finish it, or cancel it, before starting the next.

Getting one started

Two routes, both covered in Create a new version:

• From a workshop roadmap: the recommended one. The workshop already wrote the brief and sliced the work, so you press start and the version opens with its brief injected.
• From the launcher's escape hatches: Guided version or Direct version, when you already know exactly what you want.

The two workflows

The steps are tabs in the step switcher, in the breadcrumb at the top of the version page.

What each step is for

Design

Shape the look and feel by chatting with the agent. No specs, no code yet. The preview runs against a mocked API so iterating stays fast.

Specifications

Review the functional and technical plan the agent will build from. This is the cheapest place to fix anything that is off: a wrong spec costs minutes here and a rebuild later. Mark what you want changed and send the batch; see Refine specifications with the agent.

Development

The agent writes the code. You stay in the conversation on the left; the workspace on the right lets you follow along and act on what you see:

A pill floats over the preview with two controls:

• Auto-pilot: the agent chains Design, then Specifications, then Development, and waits there for your feedback. Turned off, you advance each step yourself.
• Sample data: your app is pre-filled with test data so it is usable from the first screen. Load sample data tops it up, Reset data wipes it back to a clean slate (only the login accounts remain). It shows up once the preview runs the real database, so on Development and on a direct version.

Done

Mark the version done. It moves to Ready to Deploy on the versions list, where you promote it to a deployment target. See Promote a version to a deployment target.

Going back is free

The step switcher lets you return to any step you have already passed. Design assets, specs and generated code live on the version, not on the step, so going back to Specifications does not roll back the code the agent already wrote. Earlier steps stay clickable unless the agent is busy; hovering a disabled tab tells you why.

Going back adds ?openedStep=design-step or ?openedStep=spec-step to the URL. Paste that URL to a teammate and they land on the same step.