Version History & Rollback
Every Taskade Genesis app ships with commit-based version history baked in. Every change — whether you typed it, an agent generated it, or the AI fixer applied it — is a new commit. Rollback is non-destructive: you never lose history, and a rollback is itself just another commit.
TL;DR: Taskade Genesis Apps auto-version every change. One-click rollback to any previous state. Rollbacks are non-destructive — they create a new commit on top of history, so you can always undo the undo. Pairs with GitHub Export for git-style workflows. See it →
How Version History Works
Taskade Genesis saves a new version every time you make changes to your app. Each version captures the complete state of your app — code, layout, data connections, and configuration.
- Automatic versioning — Every change is tracked without manual saves
- Complete snapshots — Each version captures the full app state
- Instant rollback — Restore any previous version with one click
- No data loss — Rolling back doesn't delete newer versions
View Version History
- Open your Taskade Genesis app in the builder
- Click the version history icon in the toolbar (clock icon)
- Browse previous versions — each shows a timestamp and summary of changes
- Preview any version before restoring
Roll Back to a Previous Version
- Open version history from the toolbar
- Select the version you want to restore
- Click "Restore" to roll back your app to that state
- Your app instantly returns to the selected version
💡 Tip: Rolling back creates a new version entry, so you can always undo a rollback by restoring the version before it.
When to Use Rollback
- Broken changes — An update introduced a bug? Roll back instantly
- Experimentation — Try different approaches without risk
- Client feedback — Restore a version the client preferred
- Accidental deletion — Recover deleted components or pages
Tips
- Non-destructive by design — Rolling back never deletes newer versions. Every restore creates a new version entry, so your full history is always preserved.
- Preview before restoring — Always preview a version before clicking "Restore" to confirm it contains the state you want.
- Combine with publishing — After rolling back, you can immediately republish your app to push the restored version live.
- Use for A/B testing — Build two different versions of a page or feature, switch between them using rollback, and compare results with your team.
See also
- Publishing Taskade Genesis Apps — Make your app live on the web
- Custom Domains — Give your app a professional web address
- Taskade Genesis FAQ — Common questions about Taskade Genesis apps, pricing, and features
How Rollback Really Works
Rolling back creates a new commit — it doesn't delete history. This means you can always undo a rollback by restoring the commit right before it. Your full change log is preserved forever.
Notice: after rolling back at v4, you land on v5 — not back at v2. v2, v3, v4 all still exist in history. You can roll back again to any of them.
Related guides
- Publishing Taskade Genesis Apps — Republish after a rollback
- Custom Domains — Rollbacks apply to whichever version is serving your domain
- GitHub Export & Import — Commit history also syncs to a real git repo
- Real-Time Collaboration — Every co-edit is a new commit