[BUG] /remote-control not available on Claude Pro plan - "not yet enabled for your account"

Resolved 💬 2 comments Opened May 17, 2026 by frankentag Closed Jun 18, 2026

Preflight Checklist

  • [x] 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' slash command (and 'claude remote-control' CLI command) is not available on
my Claude Pro account, despite official documentation stating it supports Pro plan subscribers.
Running the command returns:
Error: Remote Control is not yet enabled for your account.
Authentication and plan are correct - all other Claude Code features work normally.

What Should Happen?

Running /remote-control' or "claude remote-control' should start a Remote Control session and
display a QR code and session URL to connect from another device, as documented at
https://code.claude.com/docs/en/remote-control

Error Messages/Logs

Error: Remote Control is not yet enabled for your account.

Steps to Reproduce

  1. Log in to Claude Code with Claude Pro account via claude.ai (not API key)
  2. Run: claude remote-control

OR type / remote-control inside an active Claude Code session

  1. Error appears immediately - no QR code, no session URL

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.143

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

{
"loggedIn": true,
"authMethod": "claude.ai",
"apiProvider": "firstParty",
"email": "*",
"orgId": "5557e
",
"orgName": "
** Organization",
"subscriptionType": "pro"
}

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗