Skip to main content
Vybe automatically saves a checkpoint of your app’s code every time the AI finishes making changes. If something goes wrong, you can restore to any previous checkpoint directly from the chat.

​
How checkpoints work

Every time the AI modifies your app’s files and finishes responding, Vybe saves a checkpoint — a snapshot of all your source files at that moment. You’ll see a confirmation appear below the AI’s message:
Your progress has been saved.
Each checkpoint is tied to a specific AI response in your conversation. This gives you a restore point for every set of changes the AI makes. You do not need to manually save your work. Checkpoints are created automatically whenever the AI modifies files.

​
Restoring to a checkpoint

If the AI makes a change that breaks your app or produces an undesired result, you can restore to any previous checkpoint.
1

Find the checkpoint in the chat

Scroll through the conversation to find the checkpoint you want to restore to — the last point where your app was in a good state. Each checkpoint appears directly below the AI message that created it.
2

Click Restore

Click the Restore button on the checkpoint. A confirmation dialog appears showing what will happen.
3

Confirm the restore

Review the confirmation and click to proceed. The restore:
  • Reverts all source files to their state at that checkpoint
  • Deletes all chat messages in the current thread that came after that checkpoint
Restoring to a checkpoint is irreversible. All chat messages after the selected checkpoint are permanently deleted from the current thread. Make sure you have selected the right checkpoint before confirming.

​
What restore affects

Restored:
  • All source files — code, components, pages, API routes, and configuration files are reverted to their state at the checkpoint
  • File structure — files added after the checkpoint are removed; files deleted after the checkpoint are brought back
Not restored:
  • Database data — if the AI created tables, ran migrations, or inserted data after the checkpoint, those changes remain in your database. You may need to ask the AI to adjust the database separately after restoring
  • Published deployments — restoring does not affect your live deployed app. If you want the deployed version to reflect the restored code, you need to publish again after restoring

​
Best practices

  • Restore early — if you notice an issue, restore before the AI makes additional changes on top of the problem. This keeps your conversation clean and avoids compounding errors
  • Build in small steps — making one change at a time means each checkpoint captures a focused set of changes, making it easier to identify exactly where something went wrong
  • Re-publish after restoring — if your app is deployed and you restore to a previous checkpoint, remember to publish again so the live version matches your restored code

​
What’s next