[BUG] remote-control command not recognized - "Unknown skill: remote-control"
Status Closed — not planned
Reported on v2.1.63
Maintainer reply None cached
Activity 14 comments · opened Mar 1, 2026 · closed Jun 18, 2026
Preflight Checklist
- [ ] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
The /remote-control (and /rc) command returns "Unknown skill: remote-control" error despite meeting all documented requirements.
Environment
- logged in account with MAX plan
- Claude Code version: 2.1.63
- OS: macOS Tahoe 26.2
- Node.js version: 25.6.1
What Should Happen?
remote control should work
Error Messages/Logs
Unknown skill: remote-control
Steps to Reproduce
- Run
claudein project directory - Login via
/login(authenticated through claude.ai) - Run
/remote-controlor/rc
Expected behavior
Remote Control session should start with session URL and QR code.
Claude Model
None
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.63
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
- Subscription: Max plan (verified)
- Authentication: Logged in via
/login(not API key) - Workspace trust: Accepted
- Tried
/logoutand/login— issue persists
Showing cached comments. Read the full discussion on GitHub ↗
13 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
If you run
claude remote-controlonce it automatically installs it for youI solved the issue by totally removing the env vars:
Setting the value to 0 has no effect on this issue, env var should be removed totally.
This was indicated in issue #28098 but its locked.
Then I had troubles to get the /rc command working properly and I solved it by ensuring that I have the latest version of applications also and logging out / logging in in EVERY clients (terminal, browser, application)
I am still seeing this issue in 2.1.71. The error message is "There is no remote-control command in the Claude CLI."
same issue... last version of claude max plan i have Unknown skill: remote-control
I'm seeing this in CLI version 2.1.76. I have tried:
I had
CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFICset to1and confirmed removing this flag made/rcavailable.Still seeing this on v2.1.81, macOS Darwin 24.6.0, iTerm2.
Also worth noting:
/feedbackcommand fails too — returns "Error submitting feedback / bug report" with no details, so there's no way to report bugs from within the CLI either.Hey guys, we need this fixed for the whole built-in command surface in remote sessions, not just
/remote-control.We are seeing the same routing class of bug in
claude.ai/code/ remote-control sessions where built-in commands get treated like skills and fail withUnknown skill.In our case it also affects
/pluginin remote: the session returnsUnknown skill: plugin, even thoughclaude plugin ...exists in the CLI.So this looks bigger than one command. Built-in slash commands should be consistently available in remote/web sessions and should not fall through to skill resolution.
Claude was down for a bit today, then once it came back
/remote-controlis gone:Still reproduces on Claude Code v2.1.138 / macOS (Darwin 22.6.0).
Repro:
claude/remote-control→Unknown skill: remote-controlNotes:
claude plugin list→No plugins installed).claude --remote-control(orclaude --remote-control -cto resume) starts the session with RC enabled and prints the URL/QR. Only the in-session slash command is affected.still happen on CLaude code V2.1.143 / Macos sonoma14.5
Closing for now — inactive for too long. Please open a new issue if this is still relevant.