Create a new version
Versions are started from the launcher, which points you at a workshop first and keeps a guided and a direct path one click away.
In the appVersions
Versions are started from the launcher, which points you at a workshop first and keeps a guided and a direct path one click away.
Versions are numbered iterations of your project (V1, V2, V3…). A project has at most one version in development at a time. Once it is marked done it moves to Ready to Deploy and you can start the next one.
Where creation starts
Open Versions from the project sidebar. The page stacks the version in Development, the ones Ready to Deploy, and the Previous Versions below, with the deployment targets in a rail on the right.
One version in development at a time. Finished ones wait under Ready to Deploy.
The Development card is the entry point.
An empty project shows the same choices as a full-page state instead of a card.
Reading a version card
Under the name and the date, a card carries three durations: total, human, and agent.
The Development card shows the line as soon as there is something to show, and hides it entirely while the total is zero. A Ready to Deploy card always shows the three, with a dash wherever nothing was recorded. Reopening a finished version adds nothing: activity after it was marked done is not counted.
These durations describe the version in front of you and nothing else. They are not what you are billed, not a productivity score, not a service commitment, and not an estimate of what you saved. Billing is in production units, and the same time totalled across the whole project is on the Production units page. See Track production unit consumption.
The values arrive with the page. They are a reading taken when the list loaded, not a counter that ticks: leave the page open while the agent works and the figures stay put. Reload, or come back to Versions, to take a fresh one.
The launcher
The launcher exists because the best brief for a version is one you did not write alone. On the left it lays out the recommended path: Brainstorm in a workshop → Get a version brief → Build it into your app. On the right, your workshops, each with its status, and Start a new workshop under them.
The launcher points at a workshop first. The two shortcuts sit under "Or skip the workshop".
A workshop does more than write the brief: it slices the work into several versions and queues them. See Launch versions from the roadmap.
Or skip the workshop
Under the workshop list, separated by a rule that says so, two shortcuts are always available:
Either one opens the Name your version dialog. Give it a short, recognizable name. Versions carry both a name and a number (
V1,V2…), and the name is what you will recognize in the list. Click Create version and you land on the version.Every create action is disabled while a version is already in development. The launcher says so in a banner rather than letting you try. Mark the current one Done, or cancel it, before starting another.
Cancel a version
Open the version in development and click Cancel version. The dialog asks why (a reason category plus optional details) because that reason is what the agent and your team read afterwards.
Cancelled versions stay visible in the Previous Versions list. A version launched from a workshop roadmap is a special case: cancelling it makes the workshop re-create a fresh draft in the same slot, so the plan keeps its shape and you can edit the brief before relaunching.
Cancelling is destructive for the current iteration only. Specifications, documents and integrations live at the project level, so they survive across versions.