Committing and pushing when asked not to

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After the agent finished implementing code changes, I said:

“Do it and let me review.”

That was a request to leave the work for me to inspect. It was not a request to commit or push. There was no “commit”, “push”, “PR”, or “ship” language.

The agent still:

  1. ran git commit
  2. ran git push to the existing PR branch

I also have a user rule that says only create commits when explicitly asked, and not to push unless explicitly asked. The agent ignored that.

“Let me review” should never be treated as approval to publish. Review means the user inspects the diff; commit/push are separate, explicit steps.

This overlaps older reports about unsolicited git commit/push (several of those threads are now closed to replies). The important failure mode here is instruction-following: clear review language + an explicit no-commit-unless-asked rule were both overridden.

Related closed threads:

Steps to Reproduce

  1. In Agent mode, ask the agent to implement a code change.
  2. When it finishes, say: “Do it and let me review.”
  3. Observe that the agent runs git commit and git push without an explicit commit/push request.

Expected Behavior

Leave changes uncommitted (or at most local) so the user can review. Do not commit or push unless the user explicitly asks.

Operating System

MacOS

Version Information

Version: 3.12.30
VSCode Version: 1.128.0
Commit: 63a2996a10d9e476b6c28e951dd7691d9c0cf480
Date: 2026-07-21T22:50:03.568Z
OS: Darwin arm64 25.5.0 (macOS 26.5.1)

For AI issues: which model did you use?

Cursor Grok 4.5

Additional Information

Settings that may matter:

  • Auto-Run mode: <Off / Run in Sandbox / Run Everything — fill from Settings → Agents>
  • git commit / git push on Command Allowlist?: <yes/no>
  • Legacy Terminal Tool: <on/off>

Even if sandbox/allowlist behavior is involved, the model should not treat “let me review” as ship approval when user rules forbid unsolicited commits.

Does this stop you from using Cursor

No - Cursor works, but with this issue

Request ID:

7852df0a-0e68-4e00-8a3e-0a9dd4fda82f
a17d1841-04d1-4d9d-836a-4c058a154d97

5

Hi @DaveAWRE!

Thanks for sharing this. Your request is a great example of Grok not fully grasping user intent, and I’ve passed your Request ID along to the team.

These cases are genuinely tricky. “Do it and let me review” doesn’t explicitly say “don’t commit and push to the PR” ar!! after all, you could review it in the PR! But a human reading your request would likely infer what you meant. This is an area where Grok needs to improve.

In the meantime, adding a rule like “only push and commit when explicitly told to” might help avoid this in future runs. And hopefully, this model behavior will improve very soon!

8

I agree that one statement is ambiguous, but I have a rule about this in my global Cursor setup and the AGENTS.md discuss not writing/modifying in a external resources without explicit direction and verification. So this is definitely a bug and major concern rather than just my incorrect use of AI tooling.

9

This happened to me also.
I have also put in rules saying “Do not push or make a pull request unless i ask”.