Versions and history

Highwind keeps every step of your project as numbered versions (v1, v2, v3…). If you don’t like a change, you go back in two clicks. Nothing is ever lost: even a restore creates a new version.

What creates a version

Action	Description in the history
An agent reply in Building mode	The summary of what the agent did.
A stopped or interrupted run, if it had already changed files	“Run cancelled midway” or “Run stopped by an error”.
An editing session in Design mode’s Element tab	“Visual edits:” followed by the files changed.
A settings session in the Theme tab	“Theme changed (colors, fonts)”.
A save in the Code tab	“Manual edit:” followed by the files.
A restore	“Back to version N”.
A project created from a template	“Project created from the “…” template”.

These do not create a version: replies in Discussion mode (they don’t change anything), and uploading, renaming or deleting images in the Images tab: those changes go into the next version.

The history

The version badge, next to the project name at the top of the editor, shows the current version (for example v12). Click it to open the History: the list of all versions, from newest to oldest, each with its number, its description, how long ago it was created, and the Current tag on the latest.

You can also click the version badge (v7) shown below each agent reply in the chat: it opens the version created by that reply directly.

View an old version

1. Open the History and click the version you want to view.
2. A banner shows above the preview: Version N · … ago · read-only. The preview shows “Preparing version N…” while that version starts, then you can browse it.
3. Look at what interests you in the Preview or the Code tab.
4. To go back, click Current version in the banner (or the version marked Current in the history).

While you’re viewing an old version, everything is read-only:

• the Code tab shows “Version N · read-only”;
• the Images tab stays on the images of the current version;
• Select an element, Edit directly and Design mode are unavailable;
• the preview’s error banner has no Fix button, and the server logs button is hidden;
• Download the code (.zip) downloads the code of the version you’re viewing.

Sending a message to the agent brings you back to the current version: the agent always works on the latest version.

Restore a version

1. View the version you want to go back to (see above).
2. Click Restore this version in the banner.
3. Highwind creates a new version identical to that one, which becomes the current version. A message confirms it in the chat: “Back to version N: the project is back to that state (new version M).”

Later versions aren’t erased: if you change your mind, you can restore the version from before the restore the same way.

Caution

• Your app’s database isn’t restored: its tables and data stay as they are. Only the code goes back. See The database.
• Unsaved code changes are lost when you restore: save them first in the Code tab if you want to keep them.
• You can’t restore while the agent is working (“Wait for the agent to finish”).
• Restoring doesn’t change your live app: to put the restored version online, click Update in the Publish menu. See Update your live app.

The Changes tab

The Changes tab shows what a version changed in the code, file by file and line by line.

1. Open the Changes tab at the top of the editor, or click Show changes below an agent reply to open it straight on the right version.
2. Pick the version in the first list. By default, it’s compared to the previous version; you can pick another version in the second list (for the very first version: “nothing (first version)”).
3. At the top, a summary: the number of lines added (in green) and deleted (in red), and the number of files.
4. On the left, the list of files touched, each with its status (Added, Modified, Deleted) and its lines added and deleted. Click a file to show the details.
5. Choose the Side by side view (before on the left, after on the right) or Inline (changes one below the other).

Good to know:

• Your app’s files (src/) are listed first; automatically generated files (such as package-lock.json) last, greyed out.
• For an image or a very large file, details aren’t shown: “binary or too large to show the details.”
• From Show steps below an agent reply, clicking a file opens its changes directly.

Tip

You don’t read code? Changes are still useful: the names of the files touched tell you which parts of the app moved. And you can always ask the agent in Discussion mode: “Explain simply what you changed in version 8.”

See also

The codeRead, edit and save the code.

Design modeEdits grouped into one version.

Update your live appPublish a new version.

TroubleshootingWhen something goes wrong.