Every committed build of your game becomes a version. Nothing is ever lost to a bad prompt: you can always roll back to any earlier state.

​
Version history

Open version history from the clock icon in the Studio’s chat header. The timeline shows every version — initial generation, each follow-up build, and past reverts — with what changed in each.

​
Reverting

1

Pick a version

Click the version you want to return to and review its details.
2

Revert

Hit Revert and confirm. Your game’s files roll back to exactly that version.
3

Keep building

A fresh session starts from the restored state — prompt away as normal.

​
What revert does (and doesn’t do)

  • Game files roll back completely to the chosen version. When a stored build exists for that version, the playable preview swaps instantly; otherwise the engine rebuilds that state (you’ll see it work for a moment).
  • Later versions are marked reverted, and the chat messages after that point show under a “Reverted changes” divider — the history stays visible, it just no longer describes the live game.
  • Reverting is not undo-able by another revert forward in the general case — but since reverted versions stay in the timeline, you can revert “back to the future” by picking a later version from history.
  • Credits are not refunded by reverting — the AI work in the abandoned versions still happened. See How credits work.

​
When to revert vs when to fix forward

  • Revert when a build took the game somewhere you fundamentally don’t want — wrong direction, broke lots of things at once, or you preferred how it played before.
  • Fix forward (a follow-up prompt describing the problem) when the build was mostly right and needs adjustment. See Debugging your game.
Reverting one step back right after a bad build, then re-prompting with a clearer instruction, is often cheaper than three rounds of “no, not like that” fix-forwards.