After a chat conversation has started, typing / in the Cursor chat input no longer shows the list of available slash commands. This makes it hard to discover or select commands/skills once there is already conversation history.
Steps to Reproduce
Open Cursor IDE and start a new chat.
Send any prompt so the conversation has at least one assistant response.
Click the chat input again and type /.
Observe that the available slash-command suggestions do not appear.
Expected Behavior
Typing / in the chat input should always open the slash-command suggestions menu, including after the conversation already has messages. The same available commands should be discoverable during an active conversation as they are at the beginning of a new chat.
Operating System
MacOS
Version Information
Cursor IDE version: 3.2.11 (from /Applications/Cursor.app/Contents/Info.plist)
OS: macOS / Darwin 23.5.0
I do not have the full Menu → About Cursor → Copy output available from automation, but can provide it if needed.
For AI issues: which model did you use?
N/A - slash-command picker UI issue
Additional Information
This was observed in an active Cursor agent conversation. It appears specific to conversations after they have started, not to a blank/new chat. The visible effect is that typing / leaves the user without the usual command picker/suggestions list.
Thanks for reporting this with the detailed steps.
Could you clarify what type of conversation you’re in when this happens? Specifically:
Are you using a cloud agent (background agent) or a standard local agent?
After starting the conversation, is the chat running in the standard Cursor sidebar, or in a separate panel/window?
We’re tracking a known issue where slash commands don’t load properly in cloud agent conversations, and your description sounds like it could be related. Knowing the agent type will help us confirm.
In the meantime, you can access the same commands through the Command Palette (Cmd+Shift+P) as a workaround.
@bernatfortet, thanks for the screenshots and clarification.
Slash commands and skills are specific to the chat input and don’t appear in the Command Palette.
Looking at your screenshots, it seems the slash commands are appearing in both the new and existing conversation. Is the issue intermittent — i.e., sometimes the / menu shows up and sometimes it doesn’t? Or is there a specific sequence of steps that consistently makes it disappear?
If it is intermittent, this matches a known class of issue we’re tracking with the slash command menu where commands can drop out during a session. Starting a new chat typically brings them back. We’re actively working on improving the reliability here.
Thanks for clarifying – that’s helpful. The menu opening but missing specific configured commands (user/project commands) intermittently is a narrower issue than the whole menu disappearing, and it matches what we’ve been tracking.
Since you haven’t seen it today, it’s possible a recent update addressed it. If the missing commands come back, could you note:
Which specific commands were missing (user commands, project commands, or skills)?
Whether restarting the chat or restarting Cursor brought them back?
That would help us narrow it down further. For now, glad it seems to be working!
That’s really helpful, thanks for narrowing it down. The trigger, being a skill that uses multitasking, matches what we’ve been seeing internally. Restarting Cursor clearing it up also lines up with what we expect from this bug.
This is actively being tracked and investigated. A couple of quick follow-ups to help us narrow it further:
Which specific skill triggers this? (The one that uses multitasking.)
Do the commands come back if you just start a new chat (without restarting Cursor)?
Developer: Reload Window (via Cmd+Shift+P) should also bring them back without a full restart, if you want a faster workaround.
I created an adverserial review skill that composes /multitasking.
One issue I see is that when I trigger that skill it seems to send a message but it doesn’t.
e.g. I usually send a message that will take a while to run and move on to the next message.
With this particular skill it never fully sends on the first try, I have to run it twice and then it works. Maybe that’s a hint?
>Developer: Reload Window (via Cmd+Shift+P) should also bring them back without a full restart, if you want a faster workaround.
The problem with this is that I always have agents running. I can’t do this all the time because I need to wait for all the agents to run.
Thanks for the details. The /multitasking composition and the “have to run it twice” behavior are both useful clues. The first invocation silently failing lines up with a race condition we’re tracking. I’ve passed that along.
Good point about Reload Window interrupting running agents. One more thing to try: does starting a new chat (without reloading or restarting Cursor) bring the commands back? That would let you keep your other agents running.
Thanks for confirming that, and sorry this keeps coming up.
Based on what you described, your best workaround right now is starting a new chat when commands disappear. That won’t interrupt your running agents, unlike Reload Window.
The regression you’re seeing with the latest update (commands dropping in random conversations, not just the multitasking skill) is a useful data point. I’ve passed that along. Could you share your current Cursor version? (Cursor > About Cursor > Copy or Cmd+Shift+P > About.) That helps us pin down which build introduced the regression.
