/remote-control (/rc) not recognized as built-in command in existing session
Open 💬 33 comments Opened Feb 24, 2026 by ashvin-verma
Description
/remote-control (and /rc) is not recognized when typed inside an existing Claude Code session. It returns "Unknown skill: rc" / "Unknown skill: remote-control".
Starting a new session with claude remote-control works fine.
Steps to Reproduce
- Start Claude Code normally:
claude - Inside the session, type
/rcor/remote-control - Get error:
Unknown skill: rc
Expected Behavior
/remote-control should start a Remote Control session from within the existing session, as documented at https://code.claude.com/docs/en/remote-control#from-an-existing-session
Environment
- Claude Code version: 2.1.52
- Plan: Max
- Platform: Linux (Ubuntu, kernel 6.8.0-101-generic)
- Authentication: logged in via
/login
Workaround
Starting a new session with claude remote-control from the terminal works correctly.
33 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
same problem, even
claude remote-controlnot works:I'm in a wsl:
Max-only for now
https://github.com/anthropics/claude-code/issues/28471#issuecomment-3958542740
<img width="1481" height="880" alt="Image" src="https://github.com/user-attachments/assets/bd23afb7-826b-455a-b4b7-2fdf7b480543" />
Active Max subscription, did not work
Tried in Ubuntu, Raspberry Pi OS, Windows
Tried
claude --updateTried
curl -fsSL https://claude.ai/install.sh | bashNothing worked
Same here, on Max, skill not available.
Good news people, Max subscription explicitly bans you from using remote-control :)
<img width="1049" height="111" alt="Image" src="https://github.com/user-attachments/assets/5d451053-e821-400e-902c-517dbb05061f" />
same question, in 2.1.59
Same here, in 2.1.62
same here
Same issue here. I'm on 2.1.63 with Max plan. Using
claude remote-controlfor a new session works as expected. Attempting to use/remote-controlor/rcreturn Unknown skill errors. The/configsetting for remote control on all sessions does not show up either.its working on my other machine. same versions 2.1.63 but doesnt work, says
Error: Remote Control is not yet enabled for your account.on max 20x plan. what are we supposed to do?
Same issue here. I'm on Max plan, remote-control was working for me on another computer for the past week, but on my second computer:
How do I get remote control back?
Both computers on Windows with "native" Claude Code (not WSL2).
Okay the fix is simple: Log out and log in again, and if you're on a recent CC version, this will fix it! At least it should for most people.
I think Anthropic is having some issues with gate-caching this feature and the issues are not all resolved yet.
/rcworks for me too now after logout/login.same here, max subscription, 2.1.63, relogin won't fix
logout/login doesn't fix it. on 2.1.63.
This worked for me on 2.1.63. It's important to _logout_ and then login.
I finally got it working by uninstalling all CC installs, ~/.claude.json, ~/.claude, and the .local/claude folders.
Reinstalled via the curl/bash script. Still didn't work but then the logout and back in (via /logout not Claude auth logout) finally fixed it.
Before I was still on native install, .63 patch version.
2.1.71 the same issue
Same here 2.1.71 not showing for me. claude remote-control works but not on an existing session
The issue happend when cc was installed through official script then later on I ran claude update.
any update on this?
Just run
claude remote-controlonce. start a session etc. Then, quit. Then runclaude/resumesession you were in. And then/rcwill appearfyi they solved it for me in the other issue comments. disabling telemetry env vars interferes with the feature flags.
https://github.com/anthropics/claude-code/issues/33327#issuecomment-4052695948
Solution: remove
DISABLE_TELEMETRYfrom ~/.claude/settings.json. It helps me!Additional override that resolved the issues:
Then
claude remote-controlagain.confirm DISABLE_TELEMETRY is a blunt flag that cuts off more than just analytics.
disabling telemetry somehow silently disables it too.
thanks for your solution @archie1602
I'm experiencing the same problem
Documentation confirms remote control is available on ALL paid plans (Pro, Max, Team, Enterprise).
This isn't a plan gating issue.
I'm on Pro, v2.1.84, no telemetry flags set, Dispatch is visible and clickable in the Desktop sidebar — but /rc, /remote-control, and claude remote-control don't exist in the CLI.
Logout/login didn't fix it.
For me, the auth method had somehow switched to the "Anthropic Console Account" by itself.
Signing out and back in with the "Claude account with Subscription" option got remote control and other missing features working!
<img width="509" height="540" alt="Image" src="https://github.com/user-attachments/assets/abbdb988-fca2-4d1c-bbd1-77b8bff53ab9" />
Can also confirm that removing the telemetry flag = 0 in the settings json fixed it for me.
similar fix to others: removed
CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC, restarted claude, and/remote_controlwas availableIn my case, removing
export DO_NOT_TRACK=1from my.bash_profileresolved the issue.Also occurs on Windows with
DISABLE_TELEMETRYset to true in Windows system environment variables.