Axer

Blog/Product

Checkpoints — go back to any turn

A snapshot of every file is saved before the agent moves. Restore is one click, and it can be undone.

Axer Team · 15 November 2026

Safety
Checkpoints

An agent that edits a real repo needs a way back. Checkpoints are that way back. They are not a git history substitute, and they are not a marketing badge. They are the button you reach for when a turn went somewhere you did not mean.

When a snapshot is taken

Axer writes a checkpoint automatically before each agent turn. You can also take one by hand. Each snapshot is the full set of project files at that moment, with a short label: an agent turn, a manual save, or the state just before a restore.

Restore, then undo

Restoring a checkpoint puts the files back to that point. Before that happens, the current tree is saved as its own checkpoint, so you can undo the restore if you were wrong about which point you wanted.

This is the safety net for longer sessions — especially when Auto is on, or when two pieces of work are moving in parallel. The conversation can stay; the files can go back.

Next to git

Commits are still yours. A checkpoint is faster and more frequent than a commit, and it does not require a message. When the work is ready to keep, you commit and push as usual, through the agent or on your own.

Back to the blog