Versions and checkpoints

Every save is a numbered revision. When an agent overwrites a revision, or you save over an agent's work, the studio keeps the previous document as a checkpoint, and you can name checkpoints yourself. Your own autosaves leave none; undo covers them.

Open in Puni↗ and choose a scene to see its history.

#Saving

The studio saves as you work. The label at the top reads Saving, then Synced. Press ⌘S to save now. If the connection drops, the label reads Offline and your edits stay open until it returns.

#History

Choose Version history from the scene menu. The list shows saved checkpoints with their time. Choose one to see what changed since, then press Restore, or press Save checkpoint to keep the current state. Restoring is itself a new revision, and the state before it is saved too.

#Two places at once

A scene can be open in the studio, in a terminal and in an agent at the same time. Each write names the revision it expects. If the scene moved on, the write is refused and the studio says Changed elsewhere. Press Retry to put your edits back on top of the new revision, or Take theirs to adopt it.

#From the command line

puni project checkpoints PROJECT_ID --base-url https://puni.design --json
puni project checkpoint PROJECT_ID --name 'Before colour' --revision 8 --base-url https://puni.design --json
puni project restore-checkpoint PROJECT_ID --checkpoint CHECKPOINT_ID --revision 8 --base-url https://puni.design --json

Local files have their own checkpoints. puni checkpoint create writes one file; puni checkpoint restore brings it back. Each carries the document's SHA-256 and the assets it needs.

#Archiving

Archiving a scene takes it out of the library and suspends its links. Restoring brings both back. Nothing is deleted.

Read Scenes and the library for where versions show up in the library.