Skip to main content

Checkpoints

Create a checkpoint before a refactor, dependency change or another round of agent edits. A checkpoint gives you a saved point to compare with current work and return to when needed. Checkpoints work with or without Git.

UnfoldAI checkpoint review beside a comparison of saved and current code

A saved checkpoint beside the current file comparison.

Create a checkpoint​

  1. Open Checkpoints in the UnfoldAI sidebar.
  2. Choose + Create.
  3. Select the project if prompted and follow the save options for unsaved files.
  4. Review the completed checkpoint and any coverage notices.

Checkpoints preserve supported saved files, including eligible untracked files. Review any omitted-file or storage notices before relying on a checkpoint. Creating one leaves your normal Git workflow intact.

An agent can request a checkpoint through MCP. Review its request in VS Code, or manage project approval preferences when you want agents to create checkpoints on your behalf.

Compare saved work​

Open a checkpoint and select a file to compare it with the current version. You can also compare two checkpoints to understand the work between them.

Use these comparisons before another round of edits or when deciding which saved point to recover.

Review a restore​

  1. Pause agents and other tools that are editing the project.
  2. Open the checkpoint and select the files you want to restore.
  3. Review a fresh preview and resolve any blockers shown.
  4. Confirm the restore in VS Code.
  5. Review the reported results before resuming work.

UnfoldAI keeps a safety checkpoint for the restoration. If the operation is interrupted, some files may already have changed. Review the results and safety checkpoint before trying again.

An MCP restore request opens a review for you; it does not restore files directly. Local checkpoint capture and manual restoration do not require an AI request.

For Git inspection before committing, see Precommit Review.