## What is a checkpoint?

A checkpoint is an addressable record of the context behind an AI-assisted change. After you [enable Entire](https://docs.entire.io/quickstart) in a repository, the [CLI](https://docs.entire.io/platforms/cli) uses Git hooks and [agent hooks](https://docs.entire.io/agents/overview) 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](https://docs.entire.io/glossary#entire-checkpoint) and stores checkpoint metadata on the [`entire/checkpoints/v1` branch](https://docs.entire.io/security#where-your-data-lives). 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](https://docs.entire.io/guides/sessions/sessions-in-entire-io#files-and-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](https://docs.entire.io/guides/checkpoints/review-checkpoints) to choose the right surface and see the common review flows. Use the [CLI reference](https://docs.entire.io/cli-reference/checkpoint) when you need exact command syntax.