> ## Documentation Index
> Fetch the complete documentation index at: https://docs.entire.com/llms.txt
> Use this file to discover all available pages before exploring further.

# blame

> A git-blame-style command for viewing file history with checkpoint and session context.

`entire blame` is a git-blame-style command for viewing file history with checkpoint and session context.

```bash theme={null}
entire blame FILE[:LINE[-LINE]] [flags]
```

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 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 demo](https://customer-0x5hsk8lh27fm00g.cloudflarestream.com/ab2d696d319f2f9d1643c9e57f8132a2/iframe?muted=true\&loop=true\&autoplay=true\&poster=https%3A%2F%2Fcustomer-0x5hsk8lh27fm00g.cloudflarestream.com%2Fab2d696d319f2f9d1643c9e57f8132a2%2Fthumbnails%2Fthumbnail.jpg%3Ftime%3D%26height%3D600)

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.

```bash theme={null}
entire blame path/to/file.ts
entire blame path/to/file.ts --line 12-20
entire blame path/to/file.ts --long
entire blame path/to/file.ts --json
```

`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 session
* `MX`: the commit mixed AI-attributed and human-attributed work
* `HU`: the commit was made without AI-attributed checkpoint data
* `??`: the line is uncommitted

When available, the output also links lines to their Entire checkpoint metadata. A line never changes tag between `entire blame` and [`entire why`](/cli-reference/why).

See [What do `entire blame` and `entire why` actually tell me?](/faq#what-do-entire-blame-and-entire-why-actually-tell-me) for what these tags do and do not promise.

## Flags

| Flag | Description |
| - | - |
| `--line LINE_OR_RANGE` | Only show a line or range, for example `12` or `12-20` |
| `--long` | Show the full attribution table with agent, model, author, and session columns |
| `--json` | Output attribution as JSON |

## Continue With

> **[Investigate Why Code Exists](/learn/investigate-why-code-exists)**
>
> Trace a surprising line from attribution to checkpoint context.

> **[why](/cli-reference/why)**
>
> Explain the context behind a file or line.

> **[Introducing entire blame](https://entire.io/blog/introducing-entire-blame)**
>
> Read the launch post on the Entire blog.