Desktop app Code tab does not discover plugin commands (only skills)

Resolved 💬 2 comments Opened Apr 16, 2026 by charl-astrohive Closed May 26, 2026

Environment

  • Claude Code desktop app (macOS), Code tab
  • Plugin installed via marketplace (claude plugin marketplace add + claude plugin install)
  • Plugin has both commands/*.md and skills/*/SKILL.md components

Expected behavior

Typing /my-command in the desktop app Code tab should discover and execute commands/my-command.md from the installed plugin, the same way it does in the CLI terminal.

Actual behavior

The desktop app routes /my-command through the Skill tool as my-plugin:my-command, which only searches skills/*/SKILL.md. Since my-command is registered as a command (in commands/), it returns:

Unknown skill: my-plugin:my-command

The same /my-command command works correctly in the CLI terminal.

Impact

Plugin commands are a core component type per the plugin architecture. Any plugin that separates user-invoked commands from model-invoked skills hits this gap in the desktop app.

Workaround

Run commands from the CLI terminal instead of the desktop app Code tab, or duplicate commands as skills (which violates the intended component type separation).

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗