Version History & Rollback
How version tracking and rollback work in Mobiforge.
Automatic version tracking
Every AI generation and edit creates a versioned snapshot of your app. You can browse the full history, compare versions, and roll back to any previous state with one click. No manual saving, no git commands — versioning happens automatically every time you build or edit.
How versions are created
Every time you send a message in the chat and the AI edits your code, a new version is saved automatically. The snapshot captures the full state of all your files at that moment, along with the prompt that triggered the change.
You can also manually create a snapshot at any time before making a large or risky change — useful as a named checkpoint before a major refactor or before switching features.
Viewing version history
Click the History icon in the top bar of the builder to open the version timeline. You will see every version listed in chronological order with:
- The timestamp of the change
- The prompt or action that triggered the snapshot
- A preview of which files were modified
Click any version in the timeline to preview its code before deciding whether to restore it.
Rolling back to a previous version
Open version history
Click the History icon in the top bar of the builder to open the version timeline panel.
Find the version you want
Scroll through the timeline and click any entry to preview its code. Use the timestamps and prompts to identify the right version.
Click "Restore this version"
Hit the Restore button on the version you want. Mobiforge will confirm the action before proceeding.
Revert completes instantly
Your app code reverts to the selected state immediately. No data is lost — and a new version snapshot is created automatically as a safety record of the rollback.
Version history by plan
Code only — not database data
Version history tracks code changes only, not your Supabase database data. Rolling back your code does not affect the rows, tables, or schema in your database. If you rolled back a migration, you may need to manually adjust your schema to match the restored code.