[BUG] Remote Control regression - "not yet available on your plan" on Claude Max

[argravatar2012]

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?

claude remote-control was working on my Claude Max account ($100/month), including QR code phone connection. After re-authenticating today, I get: "Error: Remote Control is not yet available on your plan." This is a regression — the feature worked before and now it's broken. Claude Code version 2.1.62, Windows 10, PowerShell.

What Should Happen?

Remote Control should display a QR code for phone connection, as it did previously on this same account.

Error Messages/Logs

Error: Remote Control is not yet available on your plan.

Steps to Reproduce

1. Open PowerShell on Windows 10
2. Run claude (opens Claude Code v2.1.62)
3. Run /login — login succeeds
4. Run claude remote-control
5. Error: "Remote Control is not yet available on your plan"

Note: This was working before on the same Claude Max ($100/month) account, including QR code phone connection.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.62

Claude Code Version

2.1.62 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

Related GitHub issues with the same bug: #28816, #28884, #29037, #29164, #29185. This is a widespread regression affecting many Max/Pro users.

[github-actions]

Found 3 possible duplicate issues:

1. Remote Control returns "not yet available on your plan" for Max subscriber #28816
2. Remote Control unavailable on Max plan (v2.1.59) #28833
3. [Bug] Remote Control unavailable on Max 20x plan (v2.1.62, macOS) #29308

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

[neoman007-git]

Same issue here. Max plan, v2.1.66, macOS. claude remote-control returns "Remote Control is not yet enabled for your account." Tried logout/login — no change.

[WesleyMFrederick]

Workaround That Fixed This

Had the same issue on macOS (filed #30756). Fixed by clearing stale auth state and re-authenticating cleanly:

Steps

1. Clear old auth + env overrides

   • In the terminal where you run Claude Code, unset any env vars:

     unset CLAUDE_CODE_OAUTH_TOKEN
     unset ANTHROPIC_API_KEY
     

   • Remove them from shell rc files like ~/.zshrc (or PowerShell $PROFILE) so they don't come back.
   • If you previously wired tokens into other tools, remove those too so they don't confuse things.

2. Fully log out Claude Code

   • Run claude and in the chat, run /logout to sign out completely.
   • Quit Claude Code (close the terminal session / background process).

3. Log back in using your subscription

   • Run claude again, then use /login.
   • When the browser opens, choose the same Claude Pro/Max account you use on claude.ai (not Console / API-only credentials).
   • If it offers API credit / Console login, decline that if you want to be purely on the subscription.

After this, Claude Code uses the subscription directly rather than any CLAUDE_CODE_OAUTH_TOKEN or ANTHROPIC_API_KEY path, and Remote Control works.

Root Cause

The hasAvailableSubscription: false flag in ~/.claude.json was stale from a previous auth method. A clean logout + login cycle with the subscription account refreshed it correctly.

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.