[BUG] plugin skill invoked by its bare name shows a false "isn't a recognized command here" warning
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
In the Claude Desktop Code tab, invoking a plugin skill by its bare name shows an orange
warning saying the command isn't recognized and that "some commands only work in the Claude
Code terminal." The command then resolves and runs correctly. The warning is false, and its
wording points users somewhere they don't need to go — the command works in exactly the
place it claims it doesn't.
The trigger is solely whether the submitted text is the namespaced form. Accepting the
autocomplete rewrites the input to /orclab:orc-version and no warning appears; dismissing
the menu submits the bare /orc-version and the warning fires. It is not timing-dependent,
and it is unrelated to how the plugin is structured or named.
What makes it surprising is that the autocomplete menu itself displays the bare form as a
secondary label — orclab:orc-version (orc-version). The UI offers the bare name, then
rejects it when it's submitted without the menu's rewrite.
Environment:
- Claude Desktop 1.46388.2 (deb), Linux Mint 22.3
- claude-code 2.1.241
- Plugin installed from a local-path marketplace
What Should Happen?
No warning should appear for a command that resolves and runs.
Either:
- include the bare form in the command entry's
aliaseswhen it's unambiguous, so bare
invocation matches the same entry the autocomplete menu already displays; or
- suppress the warning when the command resolves successfully, rather than deciding from a
name-match check performed before resolution.
Separately, the message text is misleading even in the cases where a command genuinely
isn't available. "Some commands only work in the Claude Code terminal" sends users to a
different surface, when here the command works fine in Desktop.
Error Messages/Logs
On-screen warning (Claude Desktop Code tab):
/orc-version isn't a recognized command here. Some commands only work in the Claude
Code terminal.
Message i18n id: +9dhXtDFu6
Nothing is written to the logs — the warning is client-side only, and the command
succeeds, so there is no error to capture.
The check appears to be an exact name/alias match, paraphrased from the minified desktop
UI bundle:
let p = e => { let t = e.toLowerCase();
return !!d?.some(e => e.name.toLowerCase() === t
|| e.aliases?.some(e => e.toLowerCase() === t)) }
with the warning firing on `!p(name)`. Plugin skill entries appear to carry only the
namespaced `name`, so a bare-name submission fails the check even though resolution
afterwards succeeds.
Steps to Reproduce
- Install any plugin that provides a skill. Example: a skill named
orc-versioninside a
plugin named orclab, which is invocable as /orclab:orc-version.
- Open the Code tab in Claude Desktop.
- Type
/orc-version— the bare skill name, without the plugin prefix. - Press Escape to dismiss the autocomplete menu.
- Press Enter.
Result: the warning "/orc-version isn't a recognized command here. Some commands only work
in the Claude Code terminal." appears, and the command then resolves and runs normally.
Contrast case, for comparison — same command, no warning:
- Type
/orc-versionagain. - Accept the autocomplete entry instead of dismissing it. The input is rewritten to
/orclab:orc-version.
- Press Enter.
Result: no warning. The command runs identically.
Claude Model
Opus
Is this a regression?
No, this never worked
Last Working Version
_No response_
Claude Code Version
2.1.241 (Claude Code)
Platform
Anthropic API
Operating System
Ubuntu/Debian Linux
Terminal/Shell
Other
Additional Information
<img width="329" height="286" alt="Image" src="https://github.com/user-attachments/assets/ac20f8fe-ae52-48f7-96dd-2fc5215562a1" />
<img width="354" height="448" alt="Image" src="https://github.com/user-attachments/assets/6d0a3207-a2bf-4aae-8b00-ac2631d0ecec" />