Building Apps

Versions & Undo

Every change to your app's code is saved as a numbered version: v1, v2, v3. You can go back to any of them. Going back never deletes anything, so a restore can itself be undone.

What Makes a Version

A new version is recorded whenever the code changes:

  • First build — the code Webase wrote from your description.
  • Chat — each chat turn that changes files.
  • Hand edit — saving a file in the Code tab.
  • Test fix — each round of fixes from the Test button.
  • Settings — changing the theme in Settings, under Appearance.
  • Restore — going back to an earlier version.
  • AI tool — changes made by an AI tool connected over MCP.
  • Template — the code copied when you remix a template.

If a change leaves the code exactly as it was, no version is recorded.

Saves close together merge. Code saves you make within about 2 minutes of each other become one version, not one per save. (Once a version has been pushed to GitHub it's fixed, so the next save starts a new one.)

Only Code Is Versioned

A version holds your app's source files. It doesn't hold your data models, their fields or their records. Restoring brings back the code. Your data stays as it is.

Going Back to a Version

There are two places to do it.

1

From a Chat Turn

Under each AI reply in the chat you'll see the version it made, like v7, and how many files changed. The latest one says current. Click Restore next to any other version to bring it back.

2

From the History List

Just above the chat box is a button with your current version, like v12 · History. Click it to see your recent versions, newest first. Each shows its summary, where it came from (Chat, Hand edit, Test fix and so on) and how long ago it was made. Click Restore on the one you want.

If you have unsaved edits in the Code tab, Webase asks before restoring, because they'd be lost.

How a Restore Works

Restoring doesn't rewind the history. It records a new version that holds the old code. Say you're on v12 and restore v9. Webase saves v9's code as v13. Versions 10, 11 and 12 are still there.

The chat shows a note like Restored v9 as v13. While v13 is still your latest version, the note has an Undo button. Undo restores v12, the version you were on before. You can also restore v12 from the History list at any time.

The preview rebuilds as soon as the restore finishes.

Versions and Publishing

Restoring changes your draft, not the published app. Visitors keep seeing the version you published. To roll the public app back, restore the version you want and then publish it. See Publishing Your App.

If you've connected GitHub, every version, including a restore, is pushed to your repository as a commit. See Download Your Code & GitHub.

Tips

  • Try things freely. If a chat change goes wrong, restore the version before it rather than asking the AI to undo it.
  • Theme changes are versions too. To undo a theme change, restore the version before it.
  • Data changes aren't undone. If a change also changed your data models, restoring the code won't change them back.