[Bug] Remote Control feature unavailable on Pro plan despite account eligibility

[robinsandfort]

Bug Description
Title: Remote Control environments are not available for your account (Pro plan)

Description:
I’m on a Claude Pro subscription and cannot use Claude Code Remote Control from the CLI.

When I run:

claude remote-control

in my project directory, I consistently get:

Remote Control environments are not available for your account.

However, according to the documentation, Remote Control should now be available on both Max and Pro plans.

Steps to reproduce:

On Windows 11, open PowerShell.

Log in with claude → /login using my Pro account.

In a trusted project directory (workspace already trusted), run:
claude remote-control

Observe the error message:
Remote Control environments are not available for your account.

Expected behavior:
Remote Control should start a remote environment for my local session, as described in the Remote Control docs for Pro/Max plans.

Actual behavior:
The CLI immediately returns:
Remote Control environments are not available for your account.
No remote environment is created.

Diagnostics / checks performed:

Plan: Claude Pro subscription, same account used in the CLI.

ANTHROPIC_API_KEY is not set (echo $env:ANTHROPIC_API_KEY is empty).

CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC is not set.

claude doctor shows only a warning about a leftover npm global installation at C:\Users\pereg\AppData\Roaming\npm\claude; I have uninstalled the npm global package with npm -g uninstall @anthropic-ai/claude-code and now use only the native Windows installer, but the issue persists.

OS: Windows 11 (64‑bit).

Network: Stable home connection, no VPN/proxy.

Question:
Is it possible that my Pro account is missing the Remote Control feature flag? Could you please check and enable Remote Control for this account, or let me know if Pro access is still rolling out and not yet available for all users?

Thank you!

Environment Info

• Platform: win32
• Terminal: windows-terminal
• Version: 2.1.63
• Feedback ID: 80c32c9e-4f5e-4ca3-be34-be56e78142d5

Errors

[]

[github-actions]

Found 3 possible duplicate issues:

1. [BUG] "Remote Control environments are not available for your account." for Claude Code Pro Plan user #29449
2. Remote Control not available despite active Pro plan #29037
3. [Bug] Remote Control unavailable despite Pro plan authentication #28817

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

[HarshalJain-cs]

Hi @robinsandfort — this is a known issue affecting many Pro users. Here's the situation and what you can do right now:

What's happening

Remote Control is currently on a phased rollout for Pro plans. The docs page at code.claude.com/docs/en/remote-control has a confusing contradiction:

• One section says it's available on Pro
• The requirements section says "Pro plan support is coming soon"

This is being tracked in issue #28817 (assigned to the Anthropic docs team). Your error Remote Control environments are not available for your account may mean your account hasn't been included in the rollout yet — or there may be a local config issue.

Troubleshooting steps for Windows (try these first)

1. Verify you're logged in via claude.ai account, not API key:

claude auth status
# Should NOT show API key auth

2. Unset conflicting env vars:

$env:CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC = $null
$env:ANTHROPIC_API_KEY = $null
claude remote-control

3. Reset your settings.json (since you mentioned claude doctor found a leftover npm install):

Copy-Item "$env:USERPROFILE\.claude\settings.json" "$env:USERPROFILE\.claude\settings.json.backup"
Set-Content "$env:USERPROFILE\.claude\settings.json" '{"env": {}}'
claude auth logout
claude auth login
claude remote-control

4. Confirm npm uninstall completed cleanly:

claude doctor
# Should show no warnings about multiple installations

If all of the above still returns the error, your account is likely pending the Pro rollout. I've submitted PR #29985 with a full troubleshooting guide covering all error variants and platform-specific steps while the official docs are updated.

[robinsandfort]

Got fixed

[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.