Remote Control not enabled despite Pro subscription
Open 💬 20 comments Opened Feb 26, 2026 by Nemoholic85
Bug Report
Description
claude remote-control fails with "Remote Control is not enabled for your account" even though the account has an active Pro subscription.
Steps to Reproduce
- Run
claude remote-controlin any project directory
Expected Behavior
Remote Control session starts and displays QR code / URL
Actual Behavior
Error: Remote Control is not enabled for your account. Contact your administrator.
Environment
- Claude Code version: 2.1.58
- OS: Ubuntu (WSL2 on Windows)
- Kernel: 6.6.87.2-microsoft-standard-WSL2
- Auth method: claude.ai (firstParty)
- Subscription: Pro
- Auth status: Logged in ✓
Notes
- Latest version (2.1.58) confirmed
- Could be a WSL2 environment limitation or incomplete rollout
20 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Maybe it is not yet deployed ??
In their documents, they said Pro user CAN use it.
Same issue here. My friend is also on Pro and getting the same error.
Has there been an update on this?
Same
same
same problem on macos.
same
Also affected on Ubuntu 22 / Pro plan / v2.1.63. Debug log shows the specific error:
No
statsigfolder is created in~/.claude/— Statsig never initializes. The bridge API is rejecting the account server-side.try
unset CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFICmy settings.json
{
"skipDangerousModePermissionPrompt": true
}
Should be fixed! https://x.com/noahzweben/status/2029648921354719319
Same issue here. Pro plan, Windows (MSYS2/Git Bash), Claude Code v2.1.71.
Tried
claude auth logout+claude auth login, updated from v2.1.62 to v2.1.71 — still getting "Remote Control is not yet enabled for your account."CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFICis not set. Auth method isoauth_tokenwithfirstPartyprovider.#28098 was closed a few weeks ago because "should be resolved in tomorrow's release: the expected behavior is that this is not available to Pro/Max subscribers at the moment, and the error message will reflect that."
Alas, the error message exactly the same as before, and this feature is actively being advertised
Did anyone manage to actually use this feature? I have a pro max subscription and don't see any way to enable it. The logout + login workaround did not work for me.
@jtaub I managed to use the feature now. Unfortunately the implementation is so bad right now that I didn’t bother actually using it, so you are not missing out on much.
I'm on a team plan and have the same problem, despite activated in our organisation. I was able to use it before, but not any longer. I thought it was working good enough to use.
For a second, I thought it was going to work.
I ran into this issue as well. What fixed it for me was removing this line from
~/.claude/settings.json:Hope this helps someone.
saved my day. although its another setting entry in my case. Try to remove everything in
~/.claude/settings.json