Hey, thanks for the report. This is actually an intentional change in Cursor 2.0, not a bug.
The @git and @commit context sources were removed because they weren’t working correctly. With the improved terminal integration, the agent can now query git history on its own.
Workarounds:
Ask the agent directly, for example:
“Analyze commit b4aa676 and explain the changes”
“Show what changed in my last commit”
For repetitive workflows, create custom commands
I understand this changes your workflow, and other users have shared similar feedback as well. If you can share specific scenarios that are now harder to do, that feedback would be very helpful for the team.
this change and proposed workarounds is confusing. why not bring back the commit tagging and make the workaround work under the hood? from the workarounds, it seems that the agent is still capable of referencing a commit. so, a bit confused about the ux change.