Cursor command applied mistakenly

[Ingvar]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I have noticed that Cursor started to commit and push automatically after each change.
I have explicit rule to not do that. I also have a command /push specifically for that.
If I to believe Cursor agent - it seems command stuck and being added to context each time.

Steps to Reproduce

I am not sure how to reproduce this reliably

Expected Behavior

Do not execute commands I didn’t instruct to execute

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 2.4.35
VSCode Version: 1.105.1
Commit: d2bf8ec12017b1049f304ad3a5c8867b117ed830
Date: 2026-02-10T02:46:56.793Z
Build Type: Stable
Release Track: Early Access
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 25.2.0

For AI issues: which model did you use?

Opus 4.6

For AI issues: add Request ID with privacy disabled

b6d5c3ba-b24a-402b-bb00-c6992c152966

Does this stop you from using Cursor

No - Cursor works, but with this issue

[deanrie]

Hey, thanks for the report. Based on your screenshot, the Cursor /push command you used at the start of the conversation got “stuck” in the <cursor_commands> section and was automatically attached to every message after that. Because of this, the agent ran commit and push after every change, even though your rules say it shouldn’t.

This looks like a real bug in how Cursor Commands are passed through a conversation. I’ll share it with the team.

For now, a workaround is to start a new chat if this happens again. That should clear the “stuck” command. We also want to understand if this happens every time or if it was only in that session.

A couple questions to help us debug:

1. Can you share the contents of your /push command definition?
2. Can you reproduce this by starting a new chat and running /push once?

Let me know what you find.

[Ingvar]

I will try

Command is dumped on the screenshot I’ve attached )