# Cursor command applied mistakenly

**URL:** <https://forum.cursor.com/t/cursor-command-applied-mistakenly/151681>\
**Category:** Bug Reports\
**Tags:** terminal, auto-run, rules\
**Created:** [February 12, 2026, 2:07pm UTC](https://forum.cursor.com/t/cursor-command-applied-mistakenly/151681 "2026-02-12T14:07:29Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ingvar](https://avatars.discourse-cdn.com/v4/letter/i/9dc877/32.png) [@Ingvar](https://forum.cursor.com/u/Ingvar)\
**Post date:** [February 12, 2026, 2:07pm UTC](https://forum.cursor.com/t/cursor-command-applied-mistakenly/151681/1 "2026-02-12T14:07:29Z")

</div>

### 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

 ![Screenshot 2026-02-12 at 14.56.21.png](https://us1.discourse-cdn.com/cursor1/original/3X/8/c/8cdac1b127c357caa7dbbe3139676ad852d0a4b8.png)

### 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

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [February 12, 2026, 2:16pm UTC](https://forum.cursor.com/t/cursor-command-applied-mistakenly/151681/3 "2026-02-12T14:16:58Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Ingvar](https://avatars.discourse-cdn.com/v4/letter/i/9dc877/32.png) [@Ingvar](https://forum.cursor.com/u/Ingvar)\
**Post date:** [February 12, 2026, 9:06pm UTC](https://forum.cursor.com/t/cursor-command-applied-mistakenly/151681/4 "2026-02-12T21:06:31Z")

</div>

I will try

Command is dumped on the screenshot I’ve attached )

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [March 6, 2026, 9:06pm UTC](https://forum.cursor.com/t/cursor-command-applied-mistakenly/151681/5 "2026-03-06T21:06:31Z")

</div>

Closed on March 6, 2026, 9:06pm UTC

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