Git Commit as reference in Cursor IDE not working anymore?

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

back before we were able to reference a git commit like this: @git → commit

Now we can’t.

Steps to Reproduce

write @git

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.69 (user setup)
VSCode Version: 1.99.3
Commit: 63fcac100bd5d5749f2a98aa47d65f6eca61db30
Date: 2025-11-07T18:21:29.650Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

Yes - Cursor is unusable

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.

1 Like

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.