Skip to main content

Checkpoints and Rewind

Save a labelled point before risky work, see what changed since, and put the folder back as it was if the work went wrong. Made for AI coding assistants, useful for anyone.

Updated
On this page

A checkpoint is a backup point saved right before you, or an AI assistant, change a lot of files: a refactor, a clean-up, a script that renames things. It has a label ("before the auth refactor") and is kept for 7 days whatever the job's thinning would do. If the work goes wrong, you see what changed since the checkpoint and put the folder back as it was.

Taking a checkpoint#

An AI assistant connected to GBM AI (see AI assistants) takes one when you ask it to: "take a checkpoint of D:\projects\shop before you start". It can also be told to do it before every large edit; for Claude Code, add a line like this to the project's CLAUDE.md:

Before large edits, call the gbm_checkpoint tool for this folder with a short label.

The folder's backup job saves the point:

  • A continuous job (Pro and Server) saves its changes as a point within seconds. If nothing changed since its newest point, that point becomes the checkpoint.
  • Any other job runs an incremental backup, and its point is the checkpoint.

A folder no job backs up has no checkpoint. The assistant can ask you to approve a new job for it.

Seeing what changed#

The assistant's gbm_changes_since tool, and Restore in the app, compare the checkpoint with the folder as it is now. They list what was added, changed and deleted, with sizes. Only files the job backs up are compared, so build output and caches its rules skip do not show.

In Restore, a checkpoint has a plum mark on the timeline and its label under the time: Checkpoint: before the auth refactor · asked by Claude Code.

Putting the folder back#

Ask the assistant to put the folder back ("rewind D:\projects\shop to the checkpoint"). Or, in Restore, open the checkpoint and choose Put back as it was.

When an assistant asks, it is a request: Home shows a card, and Review lists what changed since the checkpoint before you click Put it back. Nothing is overwritten:

  • files that are the same are left alone;
  • files that differ now are first moved into a folder beside it, shop (before put back 2026-10-25 14:10), and then the checkpoint's version is put back;
  • with remove what was added (when the assistant asked for it), files made since the checkpoint are moved there too.

So even putting back is reversible: what was there is in the folder beside it until you delete it.

How long a checkpoint is kept#

7 days from when it was taken. After that it is an ordinary point again, and the job's thinning keeps or merges it like any other.

Was this article helpful?