Slash command prompt includes stale text not present in .cursor/commands/<name>.md

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

It seems to remember what prompts I used with a slash command previously and include them without me telling it to or typing it.

I have a /commit command that commits my code for me and sometimes I pair it with pushing to dev or merging to main so I can quickly patch something

this time I just did my /commit and it decided to merge to main as well and after asking why it said there was instructions to do so in my message not the /commit command itself

Steps to Reproduce

make a /command
use it with some extra instructions at the end a couple times
use it without and it uses those extra instructions

Expected Behavior

its supposed to do what I say now not in previous conversations

Screenshots / Screen Recordings

commit
commit1618×1264 276 KB

not_in_command.png
not_in_command.png1644×870 109 KB

Operating System

MacOS

Version Information

Version: 3.5.8 (Universal)
VSCode Version: 1.105.1
Commit: 0e849a87c83c8c4b4095649fcdd17164192ff680
Date: 2026-05-18T01:44:21.944Z (1 wk ago)
Layout: editor
Build Type: Stable
Release Track: Nightly
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 24.6.0

For AI issues: which model did you use?

composer 2.5

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

It seems to be affecting all chats as in another completely unrelated chat it then had this at the bottom

image
image532×195 23.8 KB

after quitting and restarting the app it seems to have fixed itself but the fact that it happened in the first place is not great and could have caused a lot of issues

7

Thanks for reporting this. We’ve seen this issue reported by several users, and the code path that could cause it is identified. However, we haven’t been able to trigger it reliably ourselves yet, which is making it harder to get a fix prioritized.

To help us reproduce it on our end, could you share a few details?

  1. The request ID from the chat where the leak happened (the /commit that unexpectedly pushed to main). You can copy it from the three-dot menu at the top right of the chat. How to find your Request ID

  2. How many times had you used /commit with “push origin and merge main” before the leak occurred? Was it something you’d done many times over days/weeks, or just once or twice?

  3. How did you open the chat where the leak happened? Was it Cmd+N, the “New Agent” button, or did you restart Cursor before that session?

  4. Had you restarted Cursor at any point between your last intentional “push and merge” use and the leaked invocation, or had Cursor been running continuously?

You already found the right fix: fully quitting and relaunching clears the stale state. We’re working on a permanent fix so this doesn’t happen in the first place.