Cursor execute git alone and commit his changes

Describe the Bug

I have “yolo” mode enabled.
cursor has done after his changes a git add and commit and I loose the control over the changes he made. As a solution I put “git” in the commands black list.
But “git” commands should only executed by the IDE.

Steps to Reproduce

I can’t tell you it is not deterministic

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.1.6 (Universal)
VSCode Version: 1.96.2
Commit: 5b19bac7a947f54e4caa3eb7e4c5fbf832389850
Date: 2025-06-25T02:16:57.571Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

hi @jger and welcome to Cursor Forum.

This should not be happening so its important to unerstand what is happening in detail. Please share a few more details so the issue can be analyzed.

As you mention git is in the denylist so it should not be happening.
I assume AI (not Cursor) might be using some workarounds.

  • Which model are you using?
  • Can you share a request ID where this happened (with privacy mode disabled if possible otherwise Cursor Team cannot analyze the AI communication)
  • Please post the command Agent used in chat to commmit to Git, it might give clue to developers what to adjust. (please redact any sensitive part of the command).
  • Is any git command in the Allowlist? (there might be a conflict?)

I didn’t have git in either the whitelist or blacklist initially. Later, I added it to the Command Deny List to make sure it never happens again. However, I believe git should be in the deny list by default when a user launches Cursor for the first time.

This is very user dependent and thank you for the feedback.

As many who use auto-run prefer frequent git commits by Agent this is not a bug but could be a feature request.
With pushing to repo that also prevents accidental deletions of local data.

Actually as many new users do not use git by default this should not be disabled as they need to start using git frequently to avoid unnecessary data loss, since those new to coding are not aware of best practices. When they encounter data loss then its hard to restore it if no backups/commits etc were made. Blocking commits would be harmful in such cases.

Since commits are local you can still ask Agent to make commits but block any other action (like git push). Then before you push you can squash the commits with your own commit message into your preferred commit structure.

Your usage is understandable and Denylist allows you to set your preference.
Let me know if there are issues with git in denylist.