Versions are named lanes inside a project — the states you told it to
remember (v1, v2, v3…). A version is a full snapshot: its own files, its
own state, restorable and forkable. They're the answer to "keep this direction
and try that one" — where history is a rewind, a version is a branch.
Mark a version
The v-chip in the composer tools marks the current state as a version. Click it and the chip popover shows what that state captured — the files, the steering that produced it, where it sits. It's one click before a risky steer, or after a result worth keeping: the version pins the state so later turns can't write over it.
Fork
Fork a version to branch it: the forked lane starts from that state, and the lane you were on keeps going untouched. Fork when two directions both deserve a real shot — the alternative is a restore, which rewinds the project to one state and loses the other. Each live version counts against the free tier's versions cap; archiving a lane frees its slot.
Compare
Open two versions side by side to see how the directions differ — the same project, the same brief lineage, different outcomes. Where blind compare judges variants built in parallel, version compare measures the states you chose to keep — a before-and-after across steering.
Versions vs variants vs history
- Versions — lanes you mark and fork: named, durable, few
- Variants — parallel builds of one brief: anonymous, judged, promoted or discarded
- History — every turn's state: automatic, browsable, restorable
Variants answer "which direction?"; versions keep the directions that mattered; history is the raw tape underneath both. See History and restore for the snapshot drawer.
Where versions live
Versions ride with the project — the lanes and their snapshots are project state, not remote objects. Restore is local and instant; a project carries its lanes wherever the folder goes.
Tip: Mark
v1right after the first result you like — it's the clean floor you can always come back to, and it costs nothing until you fork it.