[BUG] Plugin skills not appearing in `/` menu after v2.1.110 update — only `schedule` shows

Status Fixed / completed

Reported on v2.1.110

Maintainer reply None cached

Activity 10 comments · opened Apr 16, 2026 · closed Apr 16, 2026

Description

After updating to Claude Code v2.1.110 (released 2026-04-16), the Claude Desktop app on macOS stops showing most plugin-provided skills in the / command menu. Only schedule (from the scheduled-tasks built-in) appears. Skills from enabled plugins (codex, claude-hud, frontend-design, etc.) are no longer surfaced in the Desktop UI.

CLI (claude command in terminal) works correctly — all skills from enabled plugins load as expected.

This is a regression — skills were visible in the Desktop app's / menu on 2026-04-15 (prior version). Only appeared after the 04/16 auto-update to v2.1.110.

Environment

Claude Code version: 2.1.110
Platform: macOS (Darwin 25.4.0), Claude Desktop app
Enabled plugins:
claude-hud@claude-hud
codex@openai-codex
frontend-design@claude-plugins-official
github@claude-plugins-official
context7@claude-plugins-official
~/.claude/skills/ is empty (all skills come via plugins)
~/.claude/commands/ does not exist

Expected Behavior

The / menu in Claude Desktop should list skills from all enabled plugins, e.g.:

codex:setup, codex:rescue
claude-hud:setup, claude-hud:configure
frontend-design:frontend-design
etc.

Actual Behavior

Only schedule appears in the / filter. No plugin-namespaced skills are shown. Plugin tools (MCP-backed, like context7 and github) still work correctly — only skill discovery is broken.

Steps to Reproduce

Install Claude Desktop app, update to v2.1.110
Enable several plugins that provide skills (e.g., codex@openai-codex, claude-hud@claude-hud)
Open a new chat in Desktop app, type /
Observe: only schedule appears; plugin-namespaced skills are missing
Switch to CLI (claude in terminal) — all skills load correctly

#48820 — Global commands from ~/.claude/commands/ not appearing in slash command menu (same root cause likely — skill/command discovery broken in Desktop app after v2.1.110)

View original on GitHub ↗

10 Comments

Poshisfat · 4 months ago

Exact same issue!!!

github-actions[bot] · 4 months ago

Found 3 possible duplicate issues:

This issue will be automatically closed as a duplicate in 3 days.

If your issue is a duplicate, please close it and 👍 the existing issue instead
To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

phillmorgan28 · 4 months ago

I can confirm - post update this morning all of my custom slash commands are gone.

DidiLJ · 4 months ago

Yes, same probleme here

MIM18-code · 4 months ago

Same issue since yesterday afternoons desktop app update.

ignsm · 4 months ago

Still same here + horrible new UI 🥲

jbk1998 · 4 months ago

Same issue here!

wenhaochai · 4 months ago

solved in new version

puneet1409 · 4 months ago

Still reproducing on Claude Desktop (Code tab) — Windows, 2026-04-20

Reporting as a fresh data-point: this regression persists in the Claude Desktop app's bundled Claude Code runtime even though the CLI-side fix appears to have shipped. Desktop users have no way to force the embedded runtime forward independently of the app's own release cadence — claude update in the shell doesn't touch it.

Environment

Surface: Claude Desktop → Code tab (not the standalone claude CLI)
OS: Windows 11 ARM64
CLI versions installed side-by-side at ~/.local/share/claude/versions/: 2.1.109, 2.1.110, 2.1.114
Claude Desktop: current release (auto-update reports "up to date")

Symptom

/ autocomplete in the Code tab lists plugin skills (anthropic-skills:*, codex:*, user skills) but omits the built-in /mcp command.
Typing /mcp explicitly and pressing Enter is a no-op — no interactive UI, no error.
MCP servers themselves are connected and functional (claude mcp list in a separate shell correctly lists them; their tools fire).

Ask
When the next Desktop release is cut, please confirm the bundled Claude Code runtime picks up the fix — that's the only upgrade path Desktop users have.

github-actions[bot] · 4 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.