Version history
Every turn is a checkpoint. Here's how to use them.
Every agent turn auto-snapshots the workspace. You can roll back to any prior state without losing later turns (we keep them — they go forward from the rollback point).
Viewing versions
/studio//visualize shows a timeline of turns:
- Turn number
- Summary (what the agent did)
- Files changed
- Token cost
- Optional checkpoint label
Rolling back
Click any version → Restore. Workspace files revert. The chat history is preserved, but the "current code" pointer moves to that version.
You can continue forward from a restored version — the agent will work on top of the restored state.
Manual checkpoints
Hit Checkpoint in the project toolbar to label the current state with a name like "before refactor" or "v1 demo". Easier to find than scrolling 40 turns deep.
What's snapshotted
- All workspace files
- The package.json + lockfile state
node_modulesis NOT snapshotted (we re-install as needed)- Database state from attached services is NOT snapshotted — Studio is for code, not data
Diff view
Click any version → Diff to see what changed compared to the prior version. Useful for code review of agent output.
Deleting versions
Old versions auto-expire after 30 days on the free tier, 90 on Starter, indefinitely on Pro+. You can also manually delete a version — useful if a turn captured sensitive data you don't want saved.
Branching (advanced)
Restore an old version → keep iterating → you have a "branch" off that point. The Studio UI doesn't formalize branches as a tree (the forward turns are linear from restore), but you can build the same project two different directions by restoring and iterating separately.