Checkpoints: undoing what the agent did

A snapshot before each edit, so any change can be rolled back. What they cost, and when to turn them off.

Updated September 2, 2026

Before the agent edits a file, ToolsXpo Code snapshots your workspace. If a change was wrong, you restore rather than reconstruct.

On by default.

Restoring

Every message that changed files carries a restore control:

Restore workspace — files go back, the conversation stays. Use this when the agent went the wrong way and you want to redirect it.
Restore task and workspace — both go back, as if that turn never happened.

How it works

A shadow git repository, separate from yours. It does not touch your working tree, your index, your branches or your history — you can restore a checkpoint with uncommitted work in progress and your own git state is untouched.

Your .gitignore is respected, so node_modules and build output are not snapshotted.

What it costs

Disk, and a little latency on each edit. On an ordinary project this is unnoticeable. On a very large monorepo it is measurable — that is the case where turning it off is a reasonable trade.

Settings → Editor → Checkpoints.

Why it stays on by default

The cost is disk. The benefit is being able to undo a change you did not want.

An agent that edits confidently is more useful than one that asks about everything — but only if a wrong turn is cheap to reverse. Checkpoints are what make the confident behaviour safe, which is why every autonomy preset keeps them on, including the most autonomous one. The more freedom the agent has, the more the undo matters.

Not a replacement for commits

Checkpoints are scoped to the task and cleaned up over time. They are a working safety net, not history. Commit as you normally would.