Skip to main content
Every change in the builder can be taken back. This page shows the two ways you will use most:
  • Undo this turn takes back one AI request. Images and uploads stay as they are.
  • Restore points in Project history take your pages, code and images back to a moment you saved.
In this example we asked the AI to make the Northwind Shop Beans button green, decided we liked orange better, and undid it.

​
Undo an AI request

1

Look at the change

We asked: “Make the Shop Beans button in the top menu green.” The AI did exactly that:
The Northwind menu with a green Shop Beans button

The Shop Beans button after the request

2

Click Undo this turn

Above each request in the chat there is a bar that says Before this request, with an Undo this turn button. Scroll up to the request you want to take back and click Undo this turn.
The bar above the request reading Before this request, with the Undo this turn button outlined

The Undo this turn button above the request

The builder with the Undo this turn button outlined at the top of the chat and the green Shop Beans button in the preview

Where it is in the builder

If the bar says Getting undo ready…, wait a moment. Hiveku is still saving the version it will go back to.
3

Check what will be undone, then confirm

A box opens: Undo this turn? Your site goes back to how it was before this request. It tells you what will change back (here, the menu) and how many files. Click Undo this turn to go ahead, or Cancel.
The Undo this turn box listing what goes back, with Cancel and an outlined Undo this turn button

The Undo this turn box

4

Done

After a few seconds you see Turn undone. Newer versions are kept. Click Close. The button is orange again, and the chat marks the request This turn was undone.
A box reading Turn undone. Newer versions are kept., with Show in Branches and Close

The undo is finished

Good to know:
  • Nothing is lost. Your site is saved as a version before the undo, so you can change your mind again later.
  • Later changes go back too. If you made other changes after that request, undoing it takes those back as well. The box tells you when that will happen.
  • Your live site does not change unless you choose it. If visitors already see the change you are undoing, the box offers Also put this version on the live site now.
  • If a later request brings back something you undid, say so in the chat, for example “We undid the green button; keep it orange.”
For every detail, see Undo an AI Turn.

​
Save a restore point before a big change

A restore point is a snapshot of your pages, code and images that you can go back to later. Hiveku saves one for you each time you publish, and you can save your own before a big change, such as a redesign. The ones you save are kept longer than the automatic ones, up to about 90 days.
1

Open Project history

Click the clock icon, Project history, in the row of icons above the preview. It lists your restore points, newest first.
The Project history panel listing restore points, each with Compare with now, Preview and Restore, and the clock icon outlined

Project history

The builder with Project history open on the right, listing restore points

Project history in the builder

2

Click Save restore point

At the top right, click Save restore point. Give it a name you will recognize later (for example, “Before publishing the FAQ page”) and click Save restore point.
The Save a restore point box with the name Before publishing the FAQ page and the Save restore point button outlined

Naming the restore point

It appears at the top of the list, marked Pinned.
The message Restore point saved. above a pinned restore point named Before publishing the FAQ page

The new restore point

To use a restore point later, open Project history and find it:
  • Compare with now shows which code files are different. Images are not compared.
  • Preview starts a separate copy of your site as it was then (it takes about a minute). It uses your live database, so a form sent or a purchase made in it is real.
  • Restore puts your files and images back the way they were, after you confirm. Your current site is saved as a restore point first. Pages created after the restore point are kept, so remove any you no longer want. Your pages and code reach visitors the next time you publish.
See Project History for more.

​
Next

7. Publish your changes

Put everything you changed on your live site.