Cursor 2.0 removes token and git commit references in chat

Bug Reports
21

Thanks, but I was hoping that I wouldn’t have to spend advanced model tokens on such seemingly trivial tasks as “look up a commit” :frowning:

1 Like
22

If this is the beginning of the task, then collect the context via GCF, and then switch to GPT-5 or Claude 4.5.

23

@Artemonim what are we doing here? The regression is a regression. This is just polluting the report with ultimately subpar, non deterministic and pointless suggestions. “Use an expensive model”, “Ask pretty please”, “Just git gud”, that’s the tone of all these (not just you, as I’m sure you’re only trying to be helpful; but the Cursor team officially).

Either this feature is not going to be brought back, and we complain with the hope that we get a resolution, or the Cursor team messed up and are fixing it. Offering subpar solutions isn’t the right spirit here. I appreciate a good workaround, but that was provided and it doesn’t work.

6 Likes
24

Totally with you here. For me Cursor 2.0 is a completely flawed update.
I disabled auto-updates and I’m using 1.7.

25

I’d rather not downgrade. Curious about new features. Just giving my feedback as a user, that I’m very upset that such a convenient way to guide agents to the recent code updates was deprecated for some reason. It was one of the most used features for me :sob:

26

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

We used to be able to tag git commits, this was very very handy - was this intentionally removed?

Steps to Reproduce

attempt to use @ to add a commit to a prompt

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.63
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: Darwin arm64 24.6.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

27

One more thing that upsets me with this ‘tell the agent to look git commit in the terminal’ is that more often than not, when I tell the agent to look for a commit in the terminal, it runs some git commands in the terminal for a really, really long time without any results.

28

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