Skip to content

Using StudPilot

Checkpoints and undo

Every run saves a checkpoint first, so any run can be undone in one click.

You should never have to worry about what the agent might do to your place. Before a run changes anything, StudPilot saves a checkpoint of the parts of your place the run is about to touch. If you do not like the result, undo the run and the place is back exactly as it was.

Undo a run#

Every run that changed your place has an Undo button under its reply. Click it, confirm, and StudPilot restores the checkpoint taken before that run. Instances the run created are removed, instances it deleted come back, and properties and scripts it changed return to their earlier values.

Undo works best newest first. Later runs are often built on top of earlier ones, so if you want to go back several runs, undo them in order from the latest.

Undo in Studio#

Each change the agent makes is also recorded as an ordinary undo step in Studio. So Ctrl+Z (Cmd+Z on macOS) in Studio steps back through the agent's changes one at a time, just like your own edits. This is handy for taking back one small change from a larger run.

How long checkpoints are kept#

StudPilot keeps the 25 most recent checkpoints for each project. Taking the 26th removes the oldest one. Checkpoints are kept with the project on StudPilot's side, so they survive closing Studio, restarting your computer or reconnecting the place.

What a checkpoint covers#

A checkpoint is a snapshot of what the run was about to change, not a copy of your whole place. That keeps it quick to take and quick to restore. It means:

  • Parts of your place the run did not touch are not in its checkpoint, and undoing the run leaves them alone.
  • If you edited something by hand after the run and that same thing was part of the run, undoing the run returns it to its state before the run, so your later edit to it is replaced.

If an undo does not go through, see Undo failed.