entire checkpoint is also available as entire cp and entire checkpoints.
checkpoint list
List checkpoints on the current branch.checkpoint explain
Show human-readable context for checkpoints, sessions, and commits. Add--generate for an AI-written summary.
The
--generate flag requires the configured provider CLI, such as Claude CLI, to be installed and authenticated.Machine-Readable Output
--json emits metadata only. With no target it lists checkpoints; with a target it emits a single checkpoint envelope, including its subagent task records under tasks and the full session token breakdown (subagent_tokens, subagent_tokens_complete, api_call_count). Transcript bytes are never embedded in that envelope.
To get the transcript itself, use --transcript, which streams the stored checkpoint transcript bytes to standard output:
Explain a Checkpoint in Another Repository
--repo reads a checkpoint owned by a different repository through that repository’s Entire API. It takes a forge-qualified reference — gh/OWNER/REPO or et/PROJECT/REPO, or a full entire:// URL — and refuses a bare owner/repo. This is the drill-down for a cross-repo entire search hit. Nothing is written to the current repository.
--checkpoint, and a checkpoint that has been pushed.
checkpoint tokens
Show token usage and optimization recommendations for a checkpoint.--json and --agent-brief are mutually exclusive.
The report resolves its target through the same path as checkpoint explain: an unambiguous checkpoint ID prefix, or a commit-ish carrying an Entire-Checkpoint trailer. Metadata missing locally is fetched from the checkpoint remote.
checkpoint search
Search checkpoints using semantic and keyword matching.entire checkpoint search is an alias for entire search. See that page for the flags, inline filters, code search, and the interactive result view.