# Cursor Blame

Understanding how AI contributed to your codebase helps with review, compliance, and debugging. This page covers how Cursor Blame surfaces AI versus human authorship in git history.

## [Overview](/content/docs/integrations/cursor-blame#overview/index.html)

Cursor Blame extends traditional git blame with AI attribution, so you can see what was AI-generated versus human-written. Available on the [Enterprise plan](/content/contact-sales?source=docs-cursor-blame/index.html), it helps you understand the origin of each line when you review or revisit code:

- **Tab**: Code generated or accepted from Cursor's Tab suggestions
- **Agent**: Code generated by Agent, with model attribution
- **Human**: Code written directly by developers

Hover over AI-attributed lines to see conversation summaries. Click to open the full commit view with detailed AI attribution.

## [How it works](/content/docs/integrations/cursor-blame#how-it-works/index.html)

Cursor Blame analyzes committed code to determine AI attribution. When you view a file or commit, it retrieves attribution data that identifies which lines came from AI assistance, which models were used, and the conversations that produced them.

### AI attribution

See at a glance which lines came from AI assistance and which were written manually.

### Model tracking

Agent-generated code shows which model produced it, helping you understand AI tool usage across your codebase.

### Conversation context

View summaries of the conversations that produced AI-generated code, with links to the full commit details.

### Contribution breakdown

See percentage attribution for each contributor (AI models and human) in the commit view.

## [Using Cursor Blame](/content/docs/integrations/cursor-blame#using-cursor-blame/index.html)

### [Enabling Cursor Blame](/content/docs/integrations/cursor-blame#enabling-cursor-blame/index.html)

Cursor Blame is disabled at the team level by default. A team admin can enable it for all team members in the [Team settings](/content/dashboard/settings/index.html).

### [Line annotations](/content/docs/integrations/cursor-blame#line-annotations/index.html)

1. Open the Command Palette ( `Cmd+Shift+PCtrl+Shift+P`) and search for "Cursor Blame: Toggle editor decorations"

**In-editor ghost text** displays:

- **Author**: The team member who committed the change
- **Subject**: The commit message
- **Time**: When the change was made (relative time)

**Hover over the ghost text** to see:

- Author with AI co-authorship indicator
- Conversation summary (for AI-attributed lines)
- Commit statistics (files, additions, deletions)

**Open the commit view** to see:

- Full AI contribution breakdown by source
- Percentage attribution for Composer, each Agent model, and human edits
- Related conversations with summaries

### [File blame view](/content/docs/integrations/cursor-blame#file-blame-view/index.html)

1. Open a file in the editor
2. Right-click and select **Cursor Blame > Toggle file blame** from the context menu, or use the Command Palette ( `Cmd+Shift+PCtrl+Shift+P`) and search for "Cursor Blame: Open File Blame"
3. The file blame view shows attribution alongside each line

## [Privacy considerations](/content/docs/integrations/cursor-blame#privacy-considerations/index.html)

Cursor Blame caches attribution data locally for performance. When you view files and commits, data is fetched from Cursor's servers. Conversation summaries are retrieved on-demand and show brief descriptions rather than full conversation history.

## [Requirements](/content/docs/integrations/cursor-blame#requirements/index.html)

- Enterprise plan
- Git repository with Cursor-tracked changes

Get Cursor Blame on Enterprise

Talk to our team about enabling AI-aware git blame for your organization.