Versions & Rollback
Versions are snapshots of your app at a specific point in time. Save one before a big change, and you can always go back if things go sideways.
Why versions matter
Say you have a working app and you ask the AI to redesign the whole UI. The redesign doesn't land the way you hoped. Without a saved version, you'd have to manually undo everything or start over. With a version saved beforehand, you just restore it and you're back to where you were.
Saving a version
Click Save Version in the project toolbar. Give it a descriptive name — something you'll recognize later:
- "Before the UI redesign"
- "Working v1 with KV storage"
- "Post-launch stable"
You can save up to 20 versions per project. If you hit the limit, the oldest version is automatically removed when you save a new one.
Restoring a version
Click the History button in the chat panel header. This opens a slide-in version list showing all saved snapshots — name, date, and file count. Click Restore next to the version you want.
Vulcan automatically saves a snapshot of your current code before reverting, so if you change your mind, you can immediately restore to where you just were.
A few things to know:
- The restore replaces your current code. If you have recent changes you want to keep, save a version of the current state first before restoring an older one.
- Storage data is not rolled back. Versions snapshot your app's code, not the data your users have stored in it. If you deleted records from a database, restoring a version won't bring them back.
- Preview redeploys automatically. After restoring, a preview deploy is triggered in the background. You'll need to deploy to production manually to push the restored version live.
Version history
The History panel shows each saved version with its name, date, and file count. Versions marked (auto-save) were created automatically by Vulcan before a restore — they're there as a safety net and can be ignored if you don't need them.
Auto-save on restore
Every time you restore a version, Vulcan auto-saves your current code first. This means you can always undo a restore by opening the History panel and restoring the auto-save that was just created.