[BUG] remote-control command not available on Pro account

[manishakuhar]

Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report (please file separate reports for different bugs)
• I am using the latest version of Claude Code

What's Wrong?

The remote-control command (or feature) is not available despite having an active Claude Pro subscription. There is no clear indication in the docs or UI about why Pro accounts are excluded, or what tier is required.
Steps to reproduce

What Should Happen?

The remote-control command should be accessible to Pro users, or the docs should clearly state which plan is required.
Actual behavior
Command is not available on a Pro account.
Environment

Error Messages/Logs

Steps to Reproduce

Log in with a Claude Pro account
Attempt to use the remote-control command in Claude Code
Command is unavailable / not recognized / gated behind a higher tier

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.56

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

[Rus23b]

Same issue. Pro plan user, getting "Invalid OAuth Request - Unknown scope: user:mcp_ser" error when trying to authorize. Version 2.1.56 on Ubuntu server.

[morav]

Same

[nim444]

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
Error: Remote Control is not enabled for your account. Contact your administrator.

[morav]

I think it's because they've rolled it out to the max plan users now
https://x.com/noahzweben/status/2026371260805271615

[inkuxuan]

I have an active Max subscription and still not seeing it in my claude code

[kimi26yg]

I'm also experiencing this issue on a Pro plan.

Environment:

• OS: macOS
• Claude Code: latest version

I've tried logging out and re-authenticating, as well as running claude doctor with no issues detected, but the problem persists.