Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Desktop 1.2773.0 slash palette omits all user skills and installed plugins [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#49258•Fetched 2026-04-17 08:46:23
View on GitHub
Comments
1
Participants
2
Timeline
11
Reactions
1
Author
mdevkmdevk
Participants
github-actions[bot]github-actions[bot]mdevkmdevk
Timeline (top)
labeled ×7cross-referenced ×3commented ×1

Fix Action

Fix / Workaround

Key observations

  • The skills are loaded into the session — the model sees them via the Skill tool system registry, and typing the full name (e.g. /my-skill) dispatches correctly.
  • So this is a UI discovery bug, not a backend load failure.
  • Process tree confirms Desktop launches ~/Library/Application Support/Claude/claude-code/2.1.92/claude.app/Contents/MacOS/claude with --setting-sources=user,project,local plus 16 --plugin-dir flags covering skills-plugin/* and every ~/.claude/plugins/cache/* directory. Those plugin dirs are passed but their commands never surface in the palette.
  • Regression: older Desktop session logs (Claude Code 2.1.78) show user skills were autocompleting and dispatching — the palette was populated. Something changed between 2.1.78 and 2.1.92 / Desktop 1.2773.0.
  • Local edits to skills-plugin/.../manifest.json are wiped on restart, suggesting the palette is cloud-allowlisted rather than enumerating the local --plugin-dir flags.

Impact

Users can't discover their own skills or plugin commands from the UI. Workaround is typing the full name, which defeats the purpose and creates confusion that the feature is broken.

RAW_BUFFERClick to expand / collapse

## Summary

In Claude Desktop 1.2773.0 (bundled Claude Code 2.1.92), the Claude Code tab's / palette shows only schedule plus built-in chat controls (btw, rewind, clear, export). No user skills from ~/.claude/skills/ and no commands from any installed plugin in ~/.claude/plugins/cache/* appear — not even the official Anthropic ones (claude-md-management, code-review, github, figma, etc.).

Repro

  1. macOS + Claude Desktop 1.2773.0.
  2. Have any standalone user skill at ~/.claude/skills/<name>/SKILL.md with valid frontmatter.
  3. Have any official plugin installed (e.g. claude-md-management@claude-plugins-official), visible in ~/.claude/plugins/installed_plugins.json.
  4. Open a new Claude Code tab (local session, non-Cowork), type /.

Expected: palette includes the user skill, plus plugin commands (revise-claude-md, etc.). Actual: palette shows only schedule, btw, rewind, clear, export. (Screenshot to be attached.)

Key observations

  • The skills are loaded into the session — the model sees them via the Skill tool system registry, and typing the full name (e.g. /my-skill) dispatches correctly.
  • So this is a UI discovery bug, not a backend load failure.
  • Process tree confirms Desktop launches ~/Library/Application Support/Claude/claude-code/2.1.92/claude.app/Contents/MacOS/claude with --setting-sources=user,project,local plus 16 --plugin-dir flags covering skills-plugin/* and every ~/.claude/plugins/cache/* directory. Those plugin dirs are passed but their commands never surface in the palette.
  • Regression: older Desktop session logs (Claude Code 2.1.78) show user skills were autocompleting and dispatching — the palette was populated. Something changed between 2.1.78 and 2.1.92 / Desktop 1.2773.0.
  • Local edits to skills-plugin/.../manifest.json are wiped on restart, suggesting the palette is cloud-allowlisted rather than enumerating the local --plugin-dir flags.

Env

  • macOS, Apple Silicon
  • Claude Desktop: 1.2773.0
  • Bundled Claude Code: 2.1.92
  • CLAUDE_CODE_ENTRYPOINT=claude-desktop, CLAUDECODE=1, no CLAUDE_CONFIG_DIR set.

Impact

Users can't discover their own skills or plugin commands from the UI. Workaround is typing the full name, which defeats the purpose and creates confusion that the feature is broken.

<img width="498" height="404" alt="Image" src="https://github.com/user-attachments/assets/1e90dadd-1da0-4e0d-9a90-6ed03c2dcd02" />

extent analysis

TL;DR

The issue can be addressed by investigating the changes between Claude Code versions 2.1.78 and 2.1.92 to identify the cause of the UI discovery bug that prevents user skills and plugin commands from appearing in the / palette.

Guidance

  1. Review changelogs: Examine the release notes for Claude Code versions 2.1.78 and 2.1.92 to identify any changes related to skill discovery or plugin command handling.
  2. Verify plugin configuration: Confirm that the --plugin-dir flags are correctly set and that the plugin directories are properly configured, ensuring that the skills and commands are being loaded.
  3. Investigate cloud-allowlisting: Research how the palette is populated, focusing on the cloud-allowlisting mechanism, to understand why local edits to skills-plugin/.../manifest.json are being wiped on restart.
  4. Test with older version: Attempt to reproduce the issue with an older version of Claude Code (e.g., 2.1.78) to confirm the regression and gather more information about the cause.

Example

No code snippet is provided as the issue is related to a specific version of Claude Code and its interaction with plugins, and there is not enough information to create a relevant example.

Notes

The issue seems to be specific to the interaction between Claude Desktop and Claude Code, and the exact cause may require further investigation into the changes between versions 2.1.78 and 2.1.92.

Recommendation

Apply a workaround by typing the full name of the skill or command until the root cause of the issue is identified and addressed, as upgrading to a fixed version is not currently an option.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#output truncation#response parsing#generation error#database connection#vector store

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING