Version History

Definition: Version History in Taskade Genesis tracks changes to your app over time, letting you view previous versions and restore an earlier state when needed.

Why Version History Matters

Without Version History:

• Made a change you regret? Start over
• Broke something that was working? Debug for hours
• Want to see what changed? Good luck remembering

With Taskade Genesis Version History:

• Changes are saved as you iterate on your app
• You can view previous versions of your app
• Restore an earlier version when needed

Version History Features

Automatic Saving:
As you iterate on your Genesis app through conversation, versions are saved along the way. You do not need to manually save checkpoints.

Version Tracking:
Each version captures the state of your app at a point in time, including what changed and when. This gives you a timeline of how your app evolved.

Restore Previous Versions:
If you want to go back to an earlier state, you can restore a previous version. This is useful when an experiment does not work out or when you want to undo a series of changes.

Using Version History

View History:
Open Version History from your app's menu to see saved versions with timestamps.

Restore a Version:
Select a previous version to restore your app to that state. Your current state is preserved as a new version, so you do not lose anything permanently.

Experiment Freely:
Knowing you can restore a previous version makes it safe to try different approaches. If the new direction does not work, roll back.

When Version History Helps

Safe Experimentation:
You want to try a completely different layout or feature set. With Version History, you can experiment knowing the previous version is still accessible.

Recovering from Issues:
Something broke after a series of changes. You can go back to a version where things were working and try a different approach.

Tracking Progress:
Version History gives you a record of how your app evolved through conversation, which can be helpful for understanding what changed and when.

Best Practices

• Review before restoring - make sure you understand what the earlier version looked like
• Use for experimentation - try different approaches without risk
• Note milestones - remember which versions represent significant states of your app

Related Wiki Pages: Hot Reload, AI Error Fixing, App Builder