Skip to main content

​
What is a checkpoint?

A checkpoint is an addressable record of the context behind an AI-assisted change. After you enable Entire in a repository, the CLI uses Git hooks and agent hooks to capture session data as you work. When you or your agent commit, Entire saves that captured context as a checkpoint and links it to the commit.

​
Why checkpoints matter

  • Review agent work without guessing what happened
  • Trace a commit back to the prompt, transcript, and session that produced it
  • Understand what changed, why it changed, and who edited what
  • Search past agent work later

​
How checkpoints connect to Git

Each checkpoint has a 12-character ID. Entire adds that ID to the commit message with an Entire-Checkpoint trailer and stores checkpoint metadata on the entire/checkpoints/v1 branch. Your normal Git history stays clean. Entire does not add extra commits to your working branch.

​
What a checkpoint stores

A checkpoint stores the available context behind the change, including:
  • the linked Git commit
  • the agent session or sessions behind the change
  • prompts and transcript
  • tool activity
  • changed files
  • token usage, when available
  • AI attribution for the changed lines in the checkpoint

​
Where to review checkpoints

You can review checkpoints from the CLI or in Entire.io. Use Review Checkpoints to choose the right surface and see the common review flows. Use the CLI reference when you need exact command syntax.