/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

  1. Start Claude Code normally: claude
  2. Inside the session, type /rc or /remote-control
  3. 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.

View original on GitHub ↗

33 Comments

github-actions[bot] · 4 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/18754
  2. https://github.com/anthropics/claude-code/issues/18677
  3. https://github.com/anthropics/claude-code/issues/18756

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

iChenwin · 4 months ago

same problem, even claude remote-control not works:

~/projects$ claude remote-control
Error: Remote Control is not enabled for your account. Contact your administrator.
~/projects$ claude update
Current version: 2.1.53
Checking for updates to latest version...
Claude Code is up to date (2.1.53)

I'm in a wsl:

~/projects$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 24.04.4 LTS
Release:        24.04
Codename:       noble
inkuxuan · 4 months ago
$ claude --update
Current version: 2.1.56
Checking for updates to latest version...
Claude Code is up to date (2.1.56)

$ claude remote-control

           Claude Code v2.1.50
 ▐▛███▜▌   Sonnet 4.6 · Claude Max
▝▜█████▛▘  ...
  ▘▘ ▝▝    [✻] [✻] [✻] · 3 guest passes at /passes

❯ remote-control

● Recalled 1 memory, read 1 file (ctrl+o to expand)

● Could you clarify what you mean by "remote-control"? Are you looking to:

  1. Add a remote control feature to the bot (e.g., admin commands via Discord or HTTP API)?
  2. Something else entirely?

  A bit more context would help me understand what you'd like to implement.
inkuxuan · 4 months ago

<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 --update

Tried curl -fsSL https://claude.ai/install.sh | bash

Nothing worked

pannal · 4 months ago

Same here, on Max, skill not available.

inkuxuan · 4 months ago

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" />

AshleyFang · 4 months ago

same question, in 2.1.59

halitbatur · 4 months ago

Same here, in 2.1.62

zacrify · 4 months ago

same here

bNovo · 4 months ago

Same issue here. I'm on 2.1.63 with Max plan. Using claude remote-control for a new session works as expected. Attempting to use /remote-control or /rc return Unknown skill errors. The /config setting for remote control on all sessions does not show up either.

the-vampiire · 4 months ago

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?

patrikhuber · 4 months ago

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:

$ claude remote-control
Error: Remote Control is not yet enabled for your account.

How do I get remote control back?

Both computers on Windows with "native" Claude Code (not WSL2).

$ claude --version
2.1.63 (Claude Code)
patrikhuber · 4 months ago

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.

/rc works for me too now after logout/login.

salatmaster · 4 months ago

same here, max subscription, 2.1.63, relogin won't fix

wmitsuda · 4 months ago
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. /rc works for me too now after logout/login.

logout/login doesn't fix it. on 2.1.63.

rsamf · 4 months ago
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. /rc works for me too now after logout/login.

This worked for me on 2.1.63. It's important to _logout_ and then login.

joshmeads · 4 months ago

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.

antonevane · 4 months ago

2.1.71 the same issue

joseairosa · 4 months ago

Same here 2.1.71 not showing for me. claude remote-control works but not on an existing session

SutanuNandigrami · 4 months ago

The issue happend when cc was installed through official script then later on I ran claude update.

kankunnawat · 4 months ago

any update on this?

dejoma · 4 months ago

Just run claude remote-control once. start a session etc. Then, quit. Then run claude /resume session you were in. And then /rc will appear

the-vampiire · 4 months ago

fyi 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

archie1602 · 3 months ago

Solution: remove DISABLE_TELEMETRY from ~/.claude/settings.json. It helps me!

antonevane · 3 months ago

Additional override that resolved the issues:

unset DISABLE_TELEMETRY
unset CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC
claude /logout
claude /login

Then claude remote-control again.

kankunnawat · 3 months ago

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

nadivto · 3 months ago

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.

apetta · 3 months ago

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" />

sinjens · 3 months ago

Can also confirm that removing the telemetry flag = 0 in the settings json fixed it for me.

keenanthomson · 2 months ago

similar fix to others: removed CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC, restarted claude, and /remote_control was available

tsuttsu305 · 2 months ago

In my case, removing export DO_NOT_TRACK=1 from my .bash_profile resolved the issue.

Anaphylaxis · 3 days ago

Also occurs on Windows with DISABLE_TELEMETRY set to true in Windows system environment variables.