What's Wrong?
In a Claude Code Windows desktop app window, the / command picker lists only five built-in commands: schedule, model, workflows, usage, config.
Everything else is absent:
- All 10 user-defined commands from
~/.claude/commands/*.md
- All commands from 7 enabled plugins (
code-review, feature-dev, frontend-design, github, playwright, asana, claude-code-setup)
- Standard built-ins such as
/clear and /help
The same user commands render correctly in the main Claude Code window on the same machine, same user profile.
What Should Happen?
The picker should list user commands from ~/.claude/commands/ and commands from enabled plugins, consistently across windows/surfaces — as it does in the main window.
Evidence that user configuration is not the cause
I verified the following before filing:
- Command files are present and valid. 10 files in
~/.claude/commands/, each with valid description: frontmatter. Modification dates range 2026-06-12 to 2026-07-28.
- No config suppresses them.
~/.claude/settings.json has no deny entry, permission rule, or plugin override affecting them.
- The session itself loads them successfully. In the affected window, the agent's available-skills registry contains all 10 commands by name, matching the 10 files exactly. So the command loader works — only the picker UI omits them.
- Not an
/ido-prefix or naming issue. Plugin commands and stock built-ins (/clear, /help) are missing from the same picker, so the omission spans every non-listed source.
The affected window is flagged non-interactive by the harness (it cannot run the OAuth flow, and terminal-dialog commands like /permissions are reported unavailable there). That may be the differentiating factor between this window and the main one.
Steps to Reproduce
- On Windows, have user commands defined in
~/.claude/commands/*.md and at least one plugin enabled in ~/.claude/settings.json.
- Confirm they appear in the
/ picker in the main Claude Code window.
- Open the secondary/non-interactive desktop window on the same project.
- Type
/ in the chat input.
- Observe: only
schedule, model, workflows, usage, config are listed. No user commands, no plugin commands, no /clear or /help.
Impact
The commands remain invocable by typing the full name, but they are undiscoverable in that window. Users with a large set of custom commands lose the primary means of finding them, and there is no in-window signal that anything is missing or misconfigured — the natural conclusion is that one's own setup broke.
Related Issues
Claude Code Version
2.1.219 (bundled with the Windows desktop app, at %APPDATA%\Claude\claude-code\2.1.219)
Note: claude --version on PATH reports 2.1.72 from a separate npm install; the desktop app runs the bundled 2.1.219.
Platform
Claude Code desktop app (Windows)
Operating System
Windows 11 Pro 10.0.26200
Additional Information
The project directory is on a Google Drive mount (G:). Command files themselves are on the local C: drive under ~/.claude/commands/, so cloud-sync latency is not a factor.
What's Wrong?
In a Claude Code Windows desktop app window, the
/command picker lists only five built-in commands:schedule,model,workflows,usage,config.Everything else is absent:
~/.claude/commands/*.mdcode-review,feature-dev,frontend-design,github,playwright,asana,claude-code-setup)/clearand/helpThe same user commands render correctly in the main Claude Code window on the same machine, same user profile.
What Should Happen?
The picker should list user commands from
~/.claude/commands/and commands from enabled plugins, consistently across windows/surfaces — as it does in the main window.Evidence that user configuration is not the cause
I verified the following before filing:
~/.claude/commands/, each with validdescription:frontmatter. Modification dates range 2026-06-12 to 2026-07-28.~/.claude/settings.jsonhas nodenyentry, permission rule, or plugin override affecting them./ido-prefix or naming issue. Plugin commands and stock built-ins (/clear,/help) are missing from the same picker, so the omission spans every non-listed source.The affected window is flagged non-interactive by the harness (it cannot run the OAuth flow, and terminal-dialog commands like
/permissionsare reported unavailable there). That may be the differentiating factor between this window and the main one.Steps to Reproduce
~/.claude/commands/*.mdand at least one plugin enabled in~/.claude/settings.json./picker in the main Claude Code window./in the chat input.schedule,model,workflows,usage,configare listed. No user commands, no plugin commands, no/clearor/help.Impact
The commands remain invocable by typing the full name, but they are undiscoverable in that window. Users with a large set of custom commands lose the primary means of finding them, and there is no in-window signal that anything is missing or misconfigured — the natural conclusion is that one's own setup broke.
Related Issues
/picker on Remote Control" (closed). Same class of bug on different surfaces (Remote Control, VS Code). This report covers the Windows desktop app, and additionally shows that plugin commands and stock built-ins are omitted too, which suggests the picker is populated from a restricted source list rather than dropping user commands specifically./create-prruns instead of project custom command" (open). Related Windows-desktop custom-command resolution problem, distinct symptom.Claude Code Version
2.1.219 (bundled with the Windows desktop app, at
%APPDATA%\Claude\claude-code\2.1.219)Note:
claude --versionon PATH reports 2.1.72 from a separate npm install; the desktop app runs the bundled 2.1.219.Platform
Claude Code desktop app (Windows)
Operating System
Windows 11 Pro 10.0.26200
Additional Information
The project directory is on a Google Drive mount (
G:). Command files themselves are on the localC:drive under~/.claude/commands/, so cloud-sync latency is not a factor.