Skip to content

Rollback

Every agent message in your conversation is a checkpoint. If the AI takes your app in the wrong direction, you can roll back to any previous checkpoint and try a different approach.

Each agent message in your chat history has a “Revert this” button. Click it to revert your project to the state it was in right before that message was processed. A confirmation dialog appears:

“All changes made after the selected checkpoint will be permanently lost and cannot be recovered.”

Confirm to roll back. Your app’s code and preview revert to that earlier state, and you can immediately send a new prompt to continue from there.

  • The AI went in the wrong direction. You asked for a settings page and got something completely different. Roll back and rephrase.
  • A large change broke things. A refactor or multi-screen update caused unexpected issues across your app.
  • You want to try a different approach. Roll back to a known-good state and describe an alternative direction.
  • The AI is stuck in a loop. It keeps trying to fix something and making it worse. Roll back to before the issue started.

For smaller issues, a follow-up prompt is usually cheaper and faster than rolling back:

  • Small mistakes: “The button color should be blue, not red” or “Move the title 20px down.”
  • Incomplete results: “Continue where you left off” or “You missed the settings page — add it now.”
  • Minor bugs: “The list items overlap on small screens — fix the spacing.”

These targeted corrections save tokens compared to rolling back and re-describing everything from scratch.

Build incrementally and check results after each prompt. If you ask the AI to build five screens at once and the third one goes wrong, you have to roll back and lose the fourth and fifth screens too. One feature per prompt gives you more granular rollback checkpoints.

See Prompting Fundamentals for more on structuring your prompts effectively.