Slash command autocomplete intermittently missing in Desktop with remote-control
Resolved 💬 3 comments Opened Mar 24, 2026 by luckkim123 Closed Mar 27, 2026
Description
When using claude remote-control to connect Claude Desktop to a remote Claude Code instance, the slash command (/) autocomplete dropdown menu intermittently fails to appear in some conversations while working correctly in others.
Environment
- Claude Code version: 2.1.81
- Connection method:
claude remote-control→ Claude Desktop app - OS (remote): Ubuntu 24.04 (Docker container)
- OS (local): Windows (Claude Desktop)
Steps to Reproduce
- Start
claude remote-controlon a remote machine - Connect via Claude Desktop app
- Open a new conversation and type
/in the input field - Slash command autocomplete dropdown appears correctly
- Open another new conversation and type
/ - Slash command autocomplete dropdown does NOT appear
Expected Behavior
The slash command autocomplete dropdown should consistently appear in all conversations when typing /.
Actual Behavior
- Some conversations show the autocomplete dropdown normally (with all registered skills: update-config, debug, simplify, batch, loop, schedule, claude-api, changelog, memory-update, readme-project, train-analyze, train-evaluate, etc.)
- Other conversations in the same Desktop app, connected to the same remote instance, do not show the dropdown at all
Screenshots
Working session ("Initial project setup and configuration"):
- Slash command dropdown appears with full skill list
Non-working session ("Debug skill availability issue in Claude..."):
- No dropdown appears when typing
/
Both sessions are connected to the same remote machine (ksm-MS-7E01).
Notes
- Skills themselves work fine when invoked programmatically (via the Skill tool) even in sessions where the autocomplete UI is missing
- The issue appears to be a Desktop UI-side problem, not a server-side skill loading issue
- No
--disable-slash-commandsflag is set - All plugins are properly enabled in settings.json
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗