[BUG] Remote Control blocked — subscription not recognized despite active Max plan (Linux)

Resolved 💬 3 comments Opened Mar 21, 2026 by xmlRoot Closed Mar 24, 2026

Preflight Checklist

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

What's Wrong?

claude remote-control fails with "Remote Control is not yet enabled for your account" despite having an active Max subscription with extra usage enabled. The OAuth login flow does not recognize the subscription, causing the Remote Control feature gate to evaluate as disabled. The server consistently returns Remote Control as disabled even after clearing all local caches and re-authenticating.

What Should Happen?

claude remote-control should start a Remote Control session, display a session URL and QR code, and allow connecting from claude.ai/code — as documented for Max plan subscribers.

Error Messages/Logs

Error Messages/Logs
$ claude remote-control
Error: Remote Control is not yet enabled for your account.

$ claude remote-control --verbose 2>&1
Error: Remote Control is not yet enabled for your account.

$ claude auth status
{
  "loggedIn": true,
  "authMethod": "oauth_token",
  "apiProvider": "firstParty"
}
The OAuth account object in ~/.claude.json confirms an active Stripe subscription:
json{
  "oauthAccount": {
    "hasExtraUsageEnabled": true,
    "billingType": "stripe_subscription"
  }
}

Steps to Reproduce

  1. claude auth logout
  2. claude auth login (OAuth via claude.ai)
  3. claude remote-control
  4. Observe error: Remote Control is not yet enabled for your account.

Remediation attempts that did NOT resolve the issue:

  • claude auth logoutclaude auth login (multiple times)
  • Cleared all local feature flag caches under ~/.claude/
  • Removed all cached feature flags from ~/.claude.json to force a fresh server-side fetch
  • Verified no DISABLE_TELEMETRY, CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC, or ANTHROPIC_API_KEY environment variables are set
  • Unset a CLAUDE_CODE_OAUTH_TOKEN env var that was previously present
  • Fresh flags fetched from the server still evaluate Remote Control as disabled

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

v2.1.80

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Other

Additional Information

Plan: Max (Stripe subscription, extra usage enabled)

 "accountUuid": "b2139760-2a64-4bfb-b237-91ca2f815a13",
 "organizationUuid": "3ee48ed6-68df-412c-88f5-d5408f0bc2d2",
````

The OAuth flow correctly populates the account billing type and extra usage flag, but the subscription status is not being propagated to the feature flag evaluation system on the server side. Clearing all local caches and re-authenticating does not resolve the issue — the server consistently returns the Remote Control feature gate as disabled for this account.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗