Workspace
Versions & Revisions
Every Build prompt produces a new revision. The Versions menu lets you browse, switch and fork them.
Last updated
What counts as a revision
A revision is a snapshot of your product's geometry. New revisions are created when:
- • You create a new product (the first Build prompt).
- • You send a Build prompt that succeeds in modifying the model.
Ask prompts do not create revisions — they read the current state without modifying it.
Browsing versions
Open the Versions menu from the project header (the history icon on desktop, or the hamburger → Versions on mobile). The menu lists every revision of the current product:
- • Each row shows the revision's title.
- • The currently active revision is highlighted with a green dot and a colored background.
- • If a product has no extra revisions yet, the menu shows “No versions available”.
Switching to a different version
Click any version in the menu to switch to it. A confirmation dialog appears titled “Switch Version?” with the following note:
“After confirmation, your workspace will switch to this revision. All subsequent prompts and edits will apply to this revision's state. You can change revisions at any time.”
Confirm with OK. The viewer updates in place — you stay on the same product page; only the active revision changes. You'll see a toast like “Switched to {title}”. Cancel to keep your current revision.
Full Revision (forking into a new product)
Use Full Revision when you want to take the current revision and continue iterating on it independently. Open the lifecycle / branch control in the header (the GitBranch icon) and click Full Revision.
A confirmation dialog titled “Create Full Revision?” explains what will happen:
“You are about to create a full revision from {product}. This will create a new product with the current code duplicated over.”
After confirmation:
- • A brand-new product is created with the duplicated geometry.
- • You are navigated to the new product's URL (
/products/<new-id>). - • A success toast confirms the new product's name.
- • The original product is unchanged. Both products evolve independently from here.
Use this when an existing product has gone in two directions and you want to commit to both, or when you want to experiment without affecting your original.
Versions vs Lifecycle vs Traceability
| Concept | What it represents | Where it lives |
|---|---|---|
| Revision | A geometry snapshot inside one product. | Versions menu in the workspace. |
| Lifecycle stage | A high-level status (Draft → Released → …). | Product Lifecycle board. |
| Lineage | Chronological history of every revision. | Traceability page. |