# Cursor Blame Cursor Blame is an AI-aware version of `git blame`. Regular git blame tells you which commit and author last touched a line. Cursor Blame goes one step further and labels whether a line was written by a human or generated by AI. It shipped in v2.4 (January 2026) as an Enterprise feature. ## Why it exists As agents write more of a codebase, "who wrote this" stops being a clean question. Cursor Blame gives a team a way to see how much of a file is AI-generated. That matters for where reviewers spend attention, for audit trails, and for accountability. ## Notes - It measures, it does not control. Cursor Blame reports the ratio of AI to human code; it does nothing about how the code got there. - The practical use is as a review signal. A file that is mostly AI-written may deserve a closer human read, especially given failure modes like [[Reward Hacking|reward hacking]]. ## References - Changelog v2.4: https://cursor.com/changelog/2-4 - Changelog: https://cursor.com/changelog ## Related - [[Cursor.com]] - [[Cursor Agent Mode]] - [[Reward Hacking]] - [[AI Agents]]