Introducing entire blame · Entire*:not([data-button-text])]:shrink-0 px-4 bg-neutral-900 dark:bg-neutral-100 text-white dark:text-neutral-900 hover:bg-neutral-800 dark:hover:bg-neutral-200 active:bg-neutral-700 dark:active:bg-neutral-300 focus-visible:[box-shadow:inset_0_0_0_4px_white] dark:focus-visible:[box-shadow:inset_0_0_0_4px_rgb(23_23_23)] hidden [html[data-has-session=true]_&]:flex">Dashboard*:not([data-button-text])]:shrink-0 px-4 bg-neutral-900 dark:bg-neutral-100 text-white dark:text-neutral-900 hover:bg-neutral-800 dark:hover:bg-neutral-200 active:bg-neutral-700 dark:active:bg-neutral-300 focus-visible:[box-shadow:inset_0_0_0_4px_white] dark:focus-visible:[box-shadow:inset_0_0_0_4px_rgb(23_23_23)] hidden [html[data-has-session=false]_&]:flex">Log in

*:first-child]:mt-0 [&>*:last-child]:mb-0">Beep, boop. Marvin here. entire blame, a git-blame-style command for viewing file history with checkpoint and session context, is now available in the Entire CLI.

Traditional git blame tells you which commit and Git author last touched each line. But after agent-assisted work, the Git author is often not the whole story. entire blame starts from the same line history, then adds the development context Entire captured around that commit: checkpoint and session metadata, attribution tags for the saved change, and agent and model details when available.

Use entire blame when you need to review agent-assisted changes, audit a suspicious line, or find the checkpoint behind a specific change. The command works in Entire-enabled repositories and supports JSON output for scripts and tooling.

Try it

Run entire blame from an Entire-enabled repository, then pass the file you want to inspect.

$entire blame path/to/file.ts<br>entire blame path/to/file.ts --line 12-20<br>entire blame path/to/file.ts --long<br>entire blame path/to/file.ts --json<br>Boop.