Skip to content

Versions — go back to an earlier state of your app

In shortEvery build that changes your app, every edit you save in the Code tab and every restore saves a version of your app's code. Open Versions in the workspace header and click Restore to go back to one. Restoring replaces the code only — your app's data, uploaded files, chat and feature plan stay as they are — and it is saved as a new version, so you can undo it.

Not every change turns out the way you hoped. Because MonstarX saves a version of your app’s code after each change, you can always step back to how it was before — one click, no code involved.

A new version is saved whenever your app’s code changes:

  • After a Build request that changed files — named after your request, such as Add a newsletter sign-up to the footer. A request sent from Edit mode is named Visual edits (2): …, and one with only attachments is named Changes.
  • When you save a file in the Code tab — Edit src/routes/index.tsx.
  • When you restore a version — Restored: … (see below).
  • When changes arrive from GitHub — From GitHub: …, if your project is linked to a repository.
  • When a coding agent pushes changes — Pushed from …, such as Pushed from Claude Code. See Your coding agent.
  • When a project starts — an imported app starts with Imported from …, and a duplicated project with Copied from ….

Chat and Plan requests never change the code, so they never save a version.

Click Versions in the workspace header. The number beside it is how many versions the project has.

The list is newest first. Each version shows its name, how long ago it was saved and how many files the app had. The newest is marked latest saved — that is your app as it is now.

  1. Wait until MonstarX has finished working on the project — restoring is not possible during a build.

  2. Click Versions in the workspace header.

  3. Find the version you want to go back to and click Restore.

  4. Confirm: Restore “Add a newsletter sign-up to the footer”? This replaces the current project code. App data is unchanged.

The code goes back to that version, the preview updates, and a new version called Restored: … is added to the top of the list. If your project is linked to GitHub with automatic pushing on (the default), the restore is pushed there as a commit too.

What does restoring undo — and what not?

Section titled “What does restoring undo — and what not?”

Restoring puts back your app’s code: every page, component, style and server file, exactly as they were in that version.

It does not change:

Stays as it isWhy it matters
Your app’s data — sign-ups, bookings, orders, anything saved in the databaseNothing your users or you entered is lost.
The database tablesChanges to the database structure that a later build made stay in place. If the restored code expects different tables, ask MonstarX in the chat to check the app.
Uploaded files and drawn picturesFiles people uploaded and photos MonstarX drew stay in storage.
The chat and the feature planThe conversation and the checklist are not rewound. Mark features as not built with Reopen if needed — see The feature plan.
Settings, secrets and connectorsProject settings and the services you connected stay as they are.
Your published appThe live app keeps running as it was published. Publish again to put the restored version online.

The project’s owner and people the project is shared with to edit. People with view access see the list of versions but no Restore buttons.

How do I undo the last change MonstarX made?

Open Versions and click Restore on the second version from the top — the one saved before the latest change.

Why is the Restore button greyed out?

MonstarX is working on the project. Wait for the build (or QA fix) to finish, then try again. If there are no Restore buttons at all, the project is shared with you to view only.

Will restoring delete bookings or sign-ups made since then?

No. Restoring only changes the code. Everything saved in your app's database stays.

Does a stopped build save a version?

If it had already changed files when you stopped it, yes — so you can restore the version before it to undo what it did.

Is there a limit on how many versions are kept?

Versions are kept with the project. They are deleted only when you delete the project.