I tried everything, but to no avail. Nor local plugins, nor even marketplace plugins work properly.
Skills. subagents and MCP commands do appear on the / slash menu; it’s just commands that won’t show up.
The commands are listed in the plugin settings page, together with all other plugin resources, but simply won’t show up on the / popup menu.
Installing a plugin local to a project or globally both has the same issue.
Note that commands installed in ~/.cursor/commands/ or ./.cursor/commands/ do show up. This just affects plugins.
Steps to Reproduce
Install a marketplace plugin that has commands, or create a local plugin at ~/.cursor/plugins/local
Hey, thanks for the detailed report. The fact that skills/subagents/MCP show up, but commands don’t, is a helpful signal.
First, check one thing: open Settings and make sure the toggle Include third-party Plugins, Skills, and other configs is enabled. Plugin commands depend on this toggle, but skills/subagents/MCP don’t. So if the toggle is off, you’ll see exactly what you’re seeing now, everything except commands. After enabling it, reload the window using Cmd+Shift+P then run Developer: Reload Window, or use Cmd+Shift+R.
If the toggle was already enabled and commands still don’t appear in / after a reload, then it’s likely a bug on our side, and I’ll file it internally. Let me know what you see, and please confirm the toggle status before and after.
I wasted hours trying to work around that problem, and ended up converting my plugin’s commands into skills with disable-model-invocation: true just so they could be invoked.
By the way, the name of the setting is very misleading:
Include third-party Plugins, Skills, and other configs
Automatically import agent configs from other tools
It caused a lot of confusion because:
I assumed it referred to automatically importing skills and other tools installed globally on my machine from third-party tools like Claude Code, Codex, etc. That’s something I definitely don’t want, so I kept it disabled.
It conflates importing a plugin’s capabilities with importing configurations from external, non-Cursor tools.
It suggests that it affects Skills and other configurations alike, but Skills still showed up, and the plugin itself was recognized. That made this look like a legitimate bug. Why would Skills be imported but Commands not? That doesn’t make much sense.
May I suggest one of these changes?
Reword the setting to make its purpose clearer, or
Split it into two settings: one to control importing plugin capabilities (Commands, Hooks, Rules, etc.), and another to control importing configurations from external, non-Cursor tools such as Claude Code.
Anyway, thanks for the tip!
I can finally revert those skills back to commands now.
On the naming, that’s fair feedback. The fact that skills/subagents/MCP still load, but commands quietly stop working when the toggle is off is definitely confusing, and the description Automatically import agent configs from other tools doesn’t make it clear that it also affects the capabilities of Cursor plugins themselves. I’ll pass this to the team as a suggestion to either reword the setting or split it into two, one for importing plugin capabilities and one for importing configs from external tools like Claude Code or Codex.
I won’t promise an ETA for changes, but this is solid, on-point feedback. Thanks for laying it out so clearly.
By the way, are Cursor Commands going to be discontinued?
If I develop commands now, do I risk them stopping working in the short to medium term?
I’m using Commands because they aren’t fully equivalent to Skills, even when using disable-model-invocation: true. For example, Skills don’t support $ARGUMENTS or positional arguments like $1, $2, etc.
I noticed the official documentation doesn’t have a dedicated Commands page, and the Skills page seems to encourage migrating Commands and Rules to Skills, that’s why I decided to ask.
There haven’t been any deprecation announcements for Commands. They’re still supported, so it’s safe to report issues with them now without worrying they’ll break anytime soon.
I won’t comment on the long term roadmap since I don’t want to promise anything I’m not sure about. But your point is valid. Commands and Skills aren’t functionally equivalent right now. $ARGUMENTS and positional arguments $1, $2 are exactly what Skills don’t have, so Commands still have their own use case, and you can’t replace them with Skills one to one.
I also agree that not having a dedicated Commands page in the docs is confusing and can look like a migration signal, even though that’s not the case.
There is a big difference between “import configs from other tools” and “enable capabilities from installed Cursor plugins.” If skills still appear while commands are hidden, it makes the setting feel even less connected to the behavior.