Skip to main content
Use the Entire CLI when you want to work from a terminal, explain a checkpoint or commit, read transcript output, compare token usage, or export checkpoint data as JSON.

​
Find a Checkpoint

List checkpoints on the current branch:
Add --json for a machine-readable listing, or --session ID to narrow the list to one session. When you do not know which checkpoint you want, search by phrase, meaning, or context:

​
Explain a Checkpoint or Commit

Explain a checkpoint by ID, or by an unambiguous prefix of one:
A commit-ish works too, and resolves through the commit’s Entire-Checkpoint trailer:
Add --full for the whole parsed transcript, --raw-transcript for the JSONL file, or --short for the summary alone.

​
Generate a Summary

Generate an AI summary for the checkpoint:
The --generate flag requires the configured provider CLI to be installed and authenticated.

​
Measure Token Usage

Report token usage and optimization recommendations for a checkpoint:
The report names the checkpoint, the sessions and agents behind it, the models they used, and the branch, followed by the usage breakdown and the recommendations drawn from it. It reads committed checkpoint metadata through the same resolution path as entire checkpoint explain, so an ID prefix or a commit-ish works here as well, and metadata missing locally is fetched from the checkpoint remote. Compare a checkpoint against an earlier one to see how usage moved:
The comparison reports total tokens, input, cache and context replay, cache write, output, and API calls as a delta against the baseline, and qualifies whether the change counts as an observed reduction or increase. --json and --agent-brief are mutually exclusive.

​
Continue With

Inspect in entire.io

Open checkpoint details, sessions, and file diffs visually.

checkpoint

See the full checkpoint command reference.