Skip to content

Version history

Every build Myndlab runs is saved. Browse previous versions, compare what changed between any two builds, and restore in one click.

How versioning works

Every time a build completes successfully, Myndlab automatically creates a snapshot of the full project — frontend source, backend source, database migration files, and environment variable stubs. Think of it as an automatic commit after every successful generation.

Version history is part of the Basic, Plus and Pro plans, and snapshots are kept indefinitely. Failed builds do not create snapshots — only clean, deployable states are saved.

Opening version history

  1. 1

    Open the left rail

    In the Build screen, look for the left navigation rail. If it is collapsed, hover over the left edge of the screen to expand it.

  2. 2

    Click the clock icon

    Find the clock (history) icon in the rail — it is labelled "Version history" in the tooltip. Click it to open the Version history panel.

  3. 3

    Browse your snapshots

    The panel lists every snapshot in reverse chronological order. Each entry shows the timestamp, a short auto-generated label based on what changed, and the build number.

Reading the build log timeline

Each snapshot entry in the timeline can be expanded to reveal the build log for that run. The log is split into three phases:

  1. 1

    Spec

    Myndlab interprets your prompt and produces a structured spec. This phase is instant.

  2. 2

    Code gen

    The AI generates frontend and backend code, migrations, and configuration. Duration depends on project complexity — typically 30 seconds to 2 minutes.

  3. 3

    Deploy

    The generated code is built into a container, database migrations are applied, and the live preview URL is updated.

Timestamps, token usage, and any warnings emitted during generation are all visible inside the expanded log view.

Comparing two versions

To diff any two snapshots, click the checkbox to the left of the first snapshot, then hold Shift and click the second. A Compare button appears at the top of the panel.

The diff view shows a side-by-side (or unified) view of every file that changed:

  1. 1

    Added lines

    Highlighted in green.

  2. 2

    Removed lines

    Highlighted in red.

  3. 3

    Changed files

    Listed in the left sidebar of the diff view. Click any file name to jump directly to its diff.

Files that did not change between the two snapshots are hidden by default. Toggle the "Show unchanged files" switch to see the full file tree.

Restoring a previous version

Click any snapshot in the timeline and select Restore this version. Myndlab will start a new build using the selected snapshot as its base — it does not overwrite or delete the current state.

Tip

Restoring creates a brand-new build entry at the top of the timeline. Your current state is still there as a snapshot below it, so you can always go back again if the restore wasn't what you wanted.

The restored build goes through the normal deploy phase. Once complete, your live preview URL will reflect the restored version.

Version history and GitHub

If your project is connected to a GitHub repository, every snapshot maps 1-to-1 with a commit pushed to your repo. The commit message includes the Myndlab build number and the timestamp, so you can correlate version history entries with your Git log at a glance.

Restoring a previous version also creates a corresponding commit on the connected branch — the repo always stays in sync with Myndlab's snapshot state. To connect GitHub, see the GitHub sync guide.

Next steps

Back to Guide