2.0 - Cannot Access Git Commit

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cannot Access Git Commit using @Git, previous version got this features.

Steps to Reproduce

Type @Git

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.63 (user setup)
VSCode Version: 1.99.3
Commit: 505046dcfad2acda3d066e32b7cd8b6e2dc1fdc0
Date: 2025-11-05T18:56:58.213Z
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.26100

Does this stop you from using Cursor

No - Cursor works, but with this issue

2

Hey, thanks for the report. This is an intentional change in Cursor 2.0, not a bug.

The @git and @commit context sources were removed because they were not working correctly. With improved terminal integration, the agent can now query git history on its own.

Recommendation - ask the agent directly, for example:

  • “Analyze commit b4aa676 and explain the changes”
  • “Show what changed in my last commit”
  • “Use git show for commit abc123”

For repetitive git workflows, you can create custom command shortcuts.

Explanation: Unable to add specific commits to chat - #6 by danperks

Let me know if this helped!

3

thanks for suggesting this workaround! this will do for now. it’s still making the user experience worse than before. instead of selecting a commit in a dropdown in the chat, I now need to pull up a different tool window, copy the commit hash from there and then paste it into the chat? :slightly_frowning_face:

2 Likes
4

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