[BUG] Remote Control "not yet enabled" on Max plan account

Resolved 💬 2 comments Opened Mar 25, 2026 by suril88-art Closed Apr 24, 2026

Bug Description

claude remote-control returns "Remote Control is not yet enabled for your account" despite being on Claude Max plan.

Steps to Reproduce

  1. Install Claude Code v2.1.83 on Windows 11
  2. Run claude auth login — login successful via OAuth
  3. Run claude auth status — confirms logged in, oauth_token, firstParty
  4. Run claude remote-control --name "My PC"
  5. Error: "Remote Control is not yet enabled for your account"

Environment

  • Claude Code version: 2.1.83
  • OS: Windows 11 Pro 10.0.26200
  • Plan: Claude Max
  • Auth method: OAuth (firstParty)
  • No DISABLE_TELEMETRY or CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC set
  • No Bedrock/Vertex/Foundry env vars set
  • Tried logout + re-login — same error

Expected Behavior

Remote Control should start and display a URL/QR code for connecting from another device.

Actual Behavior

Immediate error: "Remote Control is not yet enabled for your account."

Notes

This appears to be the same server-side feature flag issue reported in #33119, #29569, #34528. The tengu_ccr_bridge flag seems to return false despite an active Max subscription.

View original on GitHub ↗

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