A project in 1DesignTool isn't one result — it's a timeline of states, one per turn. The History drawer and the version chips let you look at any earlier state, restore it, or fork off it, so steering is always safe to try.
The History drawer
The History button in the composer tools opens the drawer — a list of snapshots, newest first, each with the turn that produced it. Open an entry to see that state in the preview, and restore to make it the current state. Restoring doesn't destroy the newer states — they stay in the timeline.
Version chips
The v-chips in the composer tools mark named versions — the points you
told the project to remember, like v1, v2. They're the fast path between
the states you care about rather than every intermediate turn. Click a chip to
inspect that version; the popover shows what it captured.
Versions are numbered lanes, not just bookmarks — see Versions: mark, fork and compare for branching off one and comparing two states side by side.
Restore vs fork
- Restore — roll the project back to an earlier state and keep working from there. The newer states remain in history, so it's a rewind, not a delete.
- Fork — branch a new version off an earlier point, keeping both directions alive. Fork when you want to try a direction without giving up where you are; restore when the direction you're on is done.
What a snapshot captures
Each snapshot is the project folder's state at that turn — the result files, the design-kit knowledge the project had, and the version metadata. It's the same files you'd see in the folder itself, so a restored project is honest state, not a cached render.
Tip: Mark a version before a risky steer — one click on the v-chip button pins the current state, and you can come straight back if the steer goes wrong. It's cheaper than re-running a lost direction.
Where history lives
Snapshots ride with the project — they're recorded in the project's own folder metadata, not a remote store. Restores are local and instant; nothing leaves your machine to recover an earlier design.