StageDesigner

Version history with the team and AI

How to read the history when several people and the AI assistant work on a project, how to find a specific change and go back to it safely.

4 min read
Documentation contents ▾

Every save of a project to the cloud creates a version. The basics of the panel are described in Version history. Here we focus on team situations: who changed what, when, and how to undo one person’s or the AI assistant’s change without losing everyone else’s work.

DockProjectVersion history
⌘+0
Version history panel (Windows: Ctrl + 0; in the browser ⌥ + 0).
⌥+H
Version history from the Project menu (Windows: Alt + H).
⌘+⇧+S
Name version (Windows: Ctrl + Shift + S).

Who changed what

A version row has the time, the author’s avatar, the author’s name ("You" for your saves) and a summary of changes worked out by the server, e.g. who added or removed which objects. Versions are grouped by day. Consecutive autosaves by one person with gaps of up to 30 minutes collapse into one session ("14:05–15:20 · 12 saves"). Click a session to see the individual saves.

Dot
Autosave.
Flag and label
Version named manually (Name version…) or by the AI assistant.
"restore"
Version created by restoring an older state.
"from file"
Project moved from a .stageview file to the cloud.
"current"
The current state of the project.

Filters above the list: All, Named and chips with author names. The author filter shows only one person’s saves, which makes it easier to find their changes. Show older loads more versions.

Preview and restore

  1. Hover over a version and click Preview. The scene switches to the state from that version in read-only mode, and a bar appears at the top: "Previewing version from … · read-only".
  2. Click Compare with current to see the difference in the number of screens, furniture and equipment items and solids.
  3. If it is the right state, click Restore this version and confirm.
  4. If not, click Back to current or press Esc.

Restoring deletes nothing: the current state stays in the history, and the restored one becomes a new version marked "restore". The version menu (⋯) also has New project from this version…, which creates a separate project from the older state and leaves the current one untouched.

AI assistant changes in the history

The AI assistant acts on your behalf, so its saves show your name as the author in the history. Every saving call creates a separate version (it is not merged with other saves). The server stores a label with it in the form "AI: description of changes", which the assistant sees in the version list.

AI actionHow it looks in the history
Editing the scene or a technical moduleSave with your name and a summary of changes. The "AI: …" label is visible to the assistant.
Creating a projectVersion labeled "Created by AI (<app>)".
Saving a version on requestVersion labeled with the label given by the assistant.
Restoring a versionFirst a "Restore point" with the previous state, then a "restore" version.

The simplest way to find an AI change is the AI integration panel → Recent activity section. Each action has a description, time and version number (e.g. "14:32 · v. 87"). With that time, go to the version history and open the preview of the save just before it.

Good team habits

  • Before handing the project to the client, name a version, e.g. "Option A for approval". It is easy to go back to after further edits.
  • Before a big change (new room layout, lighting rebuild), name a version, and ask the AI assistant to run save_version before it starts.
  • You can edit (Rename label) or remove (Remove label) the labels of named versions from the ⋯ menu.
  • Keep client options as separate projects (New project from this version… or Duplicate project…), so you do not jump between them by restoring.
Did not find the answer?
Describe the problem and we will reply with a solution or add an article.