[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

  1. Run claude in project directory
  2. Login via /login (authenticated through claude.ai)
  3. Run /remote-control or /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 /logout and /login — issue persists

View original on GitHub ↗

13 Comments

github-actions[bot] · 6 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/29265
  2. https://github.com/anthropics/claude-code/issues/28322
  3. https://github.com/anthropics/claude-code/issues/18754

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

wolph · 6 months ago

If you run claude remote-control once it automatically installs it for you

mickaelperrin · 5 months ago

I solved the issue by totally removing the env vars:

  • CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC
  • DISABLE_TELEMETRY

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)

laurenbdaniels-coder · 5 months ago

I am still seeing this issue in 2.1.71. The error message is "There is no remote-control command in the Claude CLI."

helwan2 · 5 months ago

same issue... last version of claude max plan i have Unknown skill: remote-control

designbyian · 5 months ago

I'm seeing this in CLI version 2.1.76. I have tried:

  • /logout and re-auth
  • Running claude remote-control from CLI. This works but starts a server that will accept new remote sessions. It does not allow an existing session to be remote-controlled as far as I can tell
  • Waiting for version 2.1.76... the /remote-control and /rc commands didn't work for me on release (Max plan), I figured if I waited a couple weeks it would likely get fixed. So far not so much.
ikstewa · 5 months ago

I had CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC set to 1 and confirmed removing this flag made /rc available.

AgasiArgent · 5 months ago

Still seeing this on v2.1.81, macOS Darwin 24.6.0, iTerm2.

> /remote-control
Unknown skill: remote-control

Also worth noting: /feedback command fails too — returns "Error submitting feedback / bug report" with no details, so there's no way to report bugs from within the CLI either.

graid2030 · 4 months ago

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 with Unknown skill.

In our case it also affects /plugin in remote: the session returns Unknown skill: plugin, even though claude 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.

NumberChiffre · 4 months ago

Claude was down for a bit today, then once it came back /remote-control is gone:

Updates
└ Auto-updates: enabled
└ Auto-update channel: latest
└ Stable version: 2.1.92
└ Latest version: 2.1.104
Version Locks
└ 2.1.104: PID 65668 (running)
scottwhitingw · 3 months ago

Still reproduces on Claude Code v2.1.138 / macOS (Darwin 22.6.0).

Repro:

  1. Start a session: claude
  2. In-session, type /remote-controlUnknown skill: remote-control

Notes:

  • No plugins installed (claude plugin listNo plugins installed).
  • The CLI flag works fine: claude --remote-control (or claude --remote-control -c to resume) starts the session with RC enabled and prints the URL/QR. Only the in-session slash command is affected.
  • This appears to be the same regression tracked in #28322 (Linux). Bumping since this issue is the macOS-tagged thread and was marked stale.
Rrostyy · 3 months ago

still happen on CLaude code V2.1.143 / Macos sonoma14.5

  1. start conversation : claude
  2. In-session, type /remote-control or /rc -> no command recognize
github-actions[bot] · 2 months ago

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

Showing cached comments. Read the full discussion on GitHub ↗