Undo and checkpoints
Ziva saves a restore point before working on your request. Undo and Retry use it to return your project files and folder names, including capitalization, to their earlier state.
Undo or retry a turn
After a response finishes, choose an action from its response controls:
- Undo: confirm to restore project files, remove that request and the later conversation, and put the request back in the message box.
- Retry: on the latest response, restore the project and send the same request again.
Undo can also remove manual changes made since the restore point. Keep a separate backup of work you want to preserve. Undoing an older response removes later project changes as well as later messages.
Large imported assets
To keep restore points fast, Ziva does not save new imported assets larger than 10 MB, such as big models, textures or audio files from an asset pack. Undo and Retry leave those files as they are. Scenes, scripts and resources are always saved, whatever their size, and so are large assets Ziva was already saving.
Keep a separate backup of large assets you plan to edit or replace.
Continue without undo
If Ziva cannot save a restore point, it stops before working on that request. When Continue without undo… is offered, you must confirm it for that message.
That message will not have undo protection. Undo and Retry cannot restore its changes, but earlier restore points remain available. Each later message needs its own restore point. Continuing does not bypass other project safety checks.
Privacy
Restore points are available on every plan and stored locally for each project, outside your project folder. They contain copies of project files and are not uploaded by the checkpoint feature.
Troubleshooting
If Undo or Retry is unavailable, follow the error message. A missing or reset restore point cannot restore an older change. Some interrupted requests can be retried without restoring files.
For failed restore points, damaged history or an unresponsive editor, see AI and restore-point troubleshooting. If a chat is read-only or a response was interrupted by a restart, see Chat history.