@Commit and @Branch commands cause the agent to search the codebase instead of executing the intended action

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When using @Commit or @Branch in the chat, Cursor’s agent doesn’t recognize them as built-in commands. Instead, it searches through the project files for text matches like “@Commit” or “@Branch”. This makes it impossible to use those commands for actual Git actions.

The behavior feels like the agent has lost awareness of its integrated version control commands and is falling back to generic code search. It happens consistently, even in clean workspaces with Git properly initialized.

Steps to Reproduce

Open a Cursor workspace connected to a Git repository.

In the chat, type something like @Commit add logging feature or @Branch feature/add-logs.

Observe that instead of committing or branching, the agent starts a code search for those terms.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.34
VSCode Version: 1.99.3
Commit: 45fd70f3fe72037444ba35c9e51ce86a1977ac10
Date: 2025-10-29T06:51:29.202Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0

For AI issues: add Request ID with privacy disabled

f78c388e-8c16-4a38-92e4-0b162a28f45f

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

2

hi @Kazopl and thank you for the detailed bug report.

Please provide following info so we can try to reproduce the issue:

  • Which AI model have you have been using.
  • Could you check if typing @Commit shows you the same options like in my screenshot below?
  • Ensure your workspace is properly connected to a Git repository and the Git integration is active.
  • Try a new chat thread in case issue was related to the thread.
  • Try restarting Cursor to reset the agent’s state.

image
image498×106 8.73 KB

1 Like
3

After the latest update I noticed that all the MCPs were automatically enabled. That seems to have reduced the available context size for the model, which might explain why it can’t fully read larger commit diffs or branch diffs anymore.