Undo and checkpoints

Ziva creates a local restore point immediately before each message runs. Undo and Retry use it to return your project to its earlier state.

Undo or retry a turn

1. After a response finishes, choose Undo or Retry from its response controls.
2. Confirm Undo to restore project files, remove that prompt and every later message, and put the prompt back in the composer.
3. Choose Retry on the latest response to restore the project first, then send that prompt again.

Undoing an older response also removes the later conversation and later project changes.

Undo restores the checkpointed project state, so manual or external changes made after that restore point can also be reverted.

Continue without undo

If Ziva cannot save a restore point for a message, it normally stops before running it. Some restore-point failures offer Continue without undo….

Choosing it runs that message without protection. Undo and Retry cannot restore changes from that message, but earlier restore points remain available. The next new or queued message must save its own restore point before running.

Reset damaged checkpoint history

If Ziva reports that checkpoint history is damaged, choose Reset checkpoint history… and stop any running chats before confirming.

Reset keeps your chats, messages, project files, settings, and a local backup of the old checkpoint history. Undo is unavailable for messages from before the reset, but new messages can create fresh restore points.

Privacy

Checkpoint history is stored locally for each project in Ziva’s data folder, outside your project folder. It contains copies of checkpointed project-file contents.

Troubleshooting

Undo is unavailable for an older message. Its restore point may have been skipped or reset. Send a new message to create a fresh restore point.

Slow checkpoints. Imports get 10 minutes; make unavailable cloud files accessible before retrying.

Checkpoint history will not reset. Stop every running chat, then choose Reset checkpoint history again.

Undo, Retry, or a new message fails after a shell command times out. Wait until Godot responds again, then retry the action. Ziva checks that the editor has finished reconciling project changes before it continues. A shell timeout still counts as a failed command; recovery does not run that command again.

If Godot stays frozen or the retry still fails, restart Godot and try again. If Ziva reports a conflict with unsaved edits, inspect the file named in the error before retrying. This recovery runs locally and is available on every plan.