[BUG] Desktop Projects (beta) / Remote Control threads: `/` autocomplete omits user skills (~/.claude/skills) and plugin commands — they execute when typed in full

Status Open
Reported on v2.1.146
Maintainer reply None cached
Activity 0 comments · opened Sep 28, 2026

Preflight Checklist

  • [x] I have searched existing issues. Closest matches: #62482 and #76932 (same symptom for Remote Control, both auto-closed as stale and never fixed — the bot asked for a new issue) and #82657 (open; project skills in GitHub-repo sessions). This report adds the Projects (beta) surface and the fact that plugin commands are missing too.
  • [x] This is a single bug report
  • [x] I am using the latest version of Claude Code

What's Wrong?

In the Claude desktop app's Projects (beta), threads run as local Remote Control sessions on my Mac. In those threads the / autocomplete popup only lists built-in commands and claude.ai-synced skills (config, model, morning, docs, import-memory, skill-creator, setup-writing-style). It omits:

  • every user-scope skill from ~/.claude/skills/*/SKILL.md (e.g. /frugal-mode, /file-interview-kb-ai-draft)
  • every command from plugins synced to the machine (e.g. /frugal:models, /frugal:routing from the frugal plugin)

The thread's process has all of them:

  • sending /frugal-mode status in full runs the skill (Skill tool → ~/.claude/skills/frugal-mode) and returns its output
  • the plugin's SessionStart / UserPromptSubmit hooks fire in that thread
  • asked to list its skills, the thread listed frugal-mode, frugal:routing, file-interview-kb-ai-draft

In a standalone desktop session (sidebar "+ New") in the same folder, the popup lists all of them. The project conversation pane (cloud side) shows the frugal:* plugin commands but no user skills — expected, since it isn't on the machine — which makes the thread popup look even more inconsistent by comparison.

Impact: users conclude the skill or plugin isn't installed for that project and re-install / re-diagnose (I spent an afternoon on this). There is no /help-style way in the pane to see what the worker actually loaded, so command names must be memorised.

What Should Happen?

The / popup in a project thread should be populated from the local worker's actual skill and command registry — the same list a native desktop session in that folder shows. Failing that, the pane should indicate that the list is incomplete.

Error Messages/Logs

None — silent omission.

Steps to Reproduce

  1. Create ~/.claude/skills/hello-local/SKILL.md with frontmatter name: hello-local and any description/body. Optionally enable any plugin that ships commands (e.g. frugal).
  2. Open the Claude desktop app → Projects (beta) → a project with a connected local folder. Start a local thread (message the project, or "+ → Work locally").
  3. In the thread pane type /hell (or /frug). Observed: the popup shows only built-ins and claude.ai-synced skills; hello-local and the plugin commands are absent.
  4. Type /hello-local in full and send. Observed: the skill runs.
  5. Open a standalone desktop session in the same folder and type /hell. Observed: hello-local is listed.

Claude Model

Claude Opus 5.5

Is this a regression?

No — long-standing (#62482 May 2026, #76932 July 2026), never fixed.

Last Working Version

n/a

Claude Code Version

2.1.146 (Claude Code); Claude desktop app 2.9939.2

Platform

Anthropic API (claude.ai Max subscription)

Operating System

macOS 26.2 (arm64)

View original on GitHub ↗