## Description Getting `Error: Remote Control is not yet enabled for your account.` when running `claude remote-control` despite being on the Max 20x plan ($200/mo). ## Environment - **Claude Code version:** 2.1.63 (native build) - **OS:** macOS 15 (Darwin 25.2.0), Apple Silicon arm64 - **Auth method:** OAuth token (firstParty) - **Auth status:** `loggedIn: true, authMethod: oauth_token, apiProvider: firstParty` ## Steps to Reproduce 1. `claude remote-control` 2. Returns: `Error: Remote Con

Remote Control not enabled for Max 20x subscriber ($200/mo)

Status Closed — not planned

Reported on v2.1.63

Maintainer reply None cached

Activity 15 comments · opened Feb 28, 2026 · closed Apr 25, 2026

Description

Getting Error: Remote Control is not yet enabled for your account. when running claude remote-control despite being on the Max 20x plan ($200/mo).

Environment

Claude Code version: 2.1.63 (native build)
OS: macOS 15 (Darwin 25.2.0), Apple Silicon arm64
Auth method: OAuth token (firstParty)
Auth status: loggedIn: true, authMethod: oauth_token, apiProvider: firstParty

Steps to Reproduce

claude remote-control
Returns: Error: Remote Control is not yet enabled for your account.

What I've Tried

Confirmed Max 20x plan is active ($200/mo)
Updated to latest version (2.1.63 native build via claude install)
Logged out and back in via claude auth logout / /login
Also tried from npm version (2.1.62) — same result
/rc slash command inside a session also does nothing

Expected Behavior

Remote Control should be available on Max plans per the documentation.

Notes

This appears to be the same server-side feature flag issue reported in #28816, #28884, #29164, and #28278. Would appreciate having the flag enabled for my account.

View original on GitHub ↗

15 Comments

vbspot · 6 months ago

+1 got the same issue as Max subscriber

bchan930 · 6 months ago

+1 same here. was working before now I'm getting the reported error.

BrandonRCopeland · 6 months ago

+1 - MAX $200 subscriber here and need it enabled!

jonathanmalkin · 5 months ago

Same error. Max plan, v2.1.71, macOS, cache not regenerating. Please help.

procrastix · 5 months ago

Same issue here

konradodwrot · 5 months ago

for me unsetting these envs helped, I'm on PRO subscription:

CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC
CLAUDE_CODE_DISABLE_TERMINAL_TITLE

heyroocoke · 5 months ago

Same error. Max plan, v2.1.79, macOS

tatumterese · 5 months ago

+1 Same issue. Max plan, v2.1.81, macOS, logged in via /login. claude
remote-control returns "not yet enabled."

giladpagi · 5 months ago

Root Cause: DISABLE_TELEMETRY / CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC blocks feature flag sync

We ran into this same issue and tracked it down. If you have either of these environment variables set:

DISABLE_TELEMETRY=1
CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC=1

...they block Statsig from syncing feature flags, which freezes the tengu_ccr_bridge gate to false — even if your account is entitled to Remote Control on the Max plan.

Fix: Unset both variables:

unset DISABLE_TELEMETRY
unset CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC

Then restart claude. Remote Control should work immediately.

As @konradzagozda noted above, this resolves the issue. We confirmed it independently — unsetting these vars restored remote control on a Max 20x subscription.

Why this happens: These env vars are commonly set to reduce telemetry, but they also suppress the Statsig SDK call that checks feature entitlements. Without that call succeeding, the client never learns that your account has remote control access, so it defaults to disabled.

---

Generated by a Bean agent ([BeanOS.ai](<https://beanos.ai>))

github-actions[bot] · 4 months ago

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

sammcj · 4 months ago

Closed as not planned? are you getting rid of remote control?

giladpagi · 4 months ago

Closed as not planned? are you getting rid of remote control?

"not planned" as in "nothing is planned to be done for this issue". Remote Control is live and working for quite some time. The bug is "customer side". See my comment above regarding the env vars blocking remote control.

sammcj · 4 months ago

It's still broken even with those unset, so it's not solely controlled by if you're allowing telemetry or not.

▸ unset DISABLE_TELEMETRY CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC
▸ grep -iE 'telemetry|nonessential' ~/.claude/settings.json*
▸ claude remote-control
Error: Remote Control is not yet enabled for your account.

! env|grep -iE 'telemetry|nonessential'
❯ /remote
❯ Unknown command: /remote

konradodwrot · 4 months ago

In my opinion, the remote control is not connected to the DISABLE_TELEMETRY and CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC options in an obvious way

Perhaps a warning invalid configuration - remote control requires ... would be a good middle-ground solution to save users the inconvenience of debugging the configuration on their own

github-actions[bot] · 3 months ago

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.