Version History

Every time you Save changes, Frontend records a version of the project: the files as they were, who saved them and when. Versions are stored with git, so the history is complete and nothing is overwritten.

Saving creates versions

Agents and the code editor make changes freely; nothing becomes part of the project until you save. When you click Save in the toolbar, all unsaved changes become one new version. Click Clear instead to throw them away. See Saving changes.

This makes it easy to try things: let an agent attempt a change, look at the preview, and either save it or clear it.

Browse versions

Open Versions in the project’s sidebar to see the history, newest first. Each version shows its message, who saved it and when.

Restore a version

Click Restore on any version to bring the project’s files back to how they were. The restore is added as a new version, so the versions after it stay in the history and you can go back to them.

Restoring changes the project’s saved files. To put the restored version live, deploy again.

Versions and GitHub

If the project is connected to GitHub, git commit and push sends your saved versions to the repository, with a commit message written from them.