entire blame is a git-blame-style command for viewing file history with checkpoint and session context.
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 tells you the intent behind how the code was created: the prompt that asked for it, the session it came from, and the checkpoint that saved it.
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
Runentire blame from an Entire-enabled repository, then pass the file you want to inspect.
FILE:12 and FILE:12-20 are equivalent to passing --line.
Attribution Tags
Each line shows the attribution status of the commit that introduced it. Tags are commit-level signals:AI: the commit was attributed to an AI agent sessionMX: the commit mixed AI-attributed and human-attributed workHU: the commit was made without AI-attributed checkpoint data??: the line is uncommitted
entire blame and entire why.
See What do entire blame and entire why actually tell me? for what these tags do and do not promise.
Flags
Continue With
Investigate Why Code Exists
Trace a surprising line from attribution to checkpoint context.
why
Explain the context behind a file or line.
Introducing entire blame
Read the launch post on the Entire blog.