fromscratch
Help center

Versions: undo anything

Every change the agent makes is saved as a version. Learn to read the « Version history », name a version and go back to any earlier state safely.

Updated 3 min read
On this page
  1. Open the version history
  2. Name an important version
  3. Go back to an earlier version
  4. What the agent knows after a restore
  5. Versions and the step-by-step plan
  6. What versions don't include
  7. Related

You can't really break your project in FromScratch. Every time the agent changes your site, a version is saved automatically, and you can go back to any of them in two clicks. Going back is itself reversible: your current state is saved first. This makes it safe to try bold ideas — if you don't like the result, undo it.

Open the version history

In your project, click Versions in the top bar. The panel Version history lists your project's versions, newest first, each with how long ago it was saved. The one your site is on right now carries the Current badge.

You'll see several kinds of versions:

Label When it is created
Project created The starting point, when the project was created
The agent's summary, or Agent change After each reply in which the agent changed something
Published version When you publish or republish
Autosave (before going back) Just before you restore an older version — your unsaved state, kept safe
Back to "…" The restore itself

A version marked « same as current » contains exactly what your site has now.

Name an important version

Before a risky change — a redesign, a new section, a big import — give the current state a name you'll recognise:

  1. Click Versions.
  2. Type a name in Name the current version… (for example « Before the redesign »).
  3. Click Save. A message confirms « Version "Before the redesign" saved ».

If nothing changed since the last version, the name is simply attached to it — no duplicate is created.

Go back to an earlier version

  1. Click Versions and find the version you want.
  2. Click Go back here.
  3. Confirm. The message reminds you: « Your current state is saved in the history first, so you can return to it. »
  4. The preview reloads on the restored site and a short note appears in the chat.

Changed your mind? Open Versions again and go back to the Autosave (before going back) entry: you're exactly where you were.

Note

you can't restore while the agent is working. Wait for the reply to finish, or click Stop first.

What the agent knows after a restore

After you go back, the agent is told that the site was restored, so on your next message it works from the restored files — not from the changes you just undid. You can simply continue the conversation: « Let's try the header again, but with a smaller logo. »

Versions and the step-by-step plan

When you follow a plan, each finished step is also a checkpoint. In the plan panel, Go back here on a done step returns your site to how it was right after that step; the following steps go back to To do and the later changes stay in the version history. See Approve the plan, step by step.

What versions don't include

Versions cover your site's own files: pages, styles, content, images and code. They deliberately leave out a few things that are rebuilt or kept elsewhere:

  • Installed packages and build caches, which are recreated automatically.
  • Your secrets in Variables: restoring a version never brings back or wipes a key.
  • Data typed into the site in the preview (for example test bookings stored by the app) may live outside the versioned files.

Warning

going back does not change your live site by itself. If the site is published, click Republish after restoring to put the restored version online.

Was this page helpful?