New in Cursor! · Full changelog · Main announcement
We’re introducing Cursor Blame, extending traditional git blame with AI attribution, so you can see exactly what was AI-generated vs. human-written.
How it works
Cursor Blame distinguishes between code from Tab completions, agent runs (broken down by model), and human edits.
When reviewing or revisiting code, each line links to a summary of the conversation that led to it, providing context and reasoning for the change.
Cursor Blame also lets you track AI usage patterns across your team’s codebase.
We’d love your feedback!
- How could AI attribution help your code review process?
- What additional insights would be useful in the blame view?
If you’ve found a bug, please post it in Bug Reports instead, so we can track and address it properly, but also feel free to drop a link to it in this thread for visibility.