[Bug] claude rc "Remote Control not yet enabled for your account" — seatTier: null on active Max subscription (macOS aarch64)

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?

Running claude rc or claude remote-control returns:

Error: Remote Control is not yet enabled for your account.

This occurs on an active Max plan personal account. Persists after full
re-authentication including config wipe.

Key diagnostic from ~/.claude.json:

• seatTier: null
• hasAvailableSubscription: absent entirely after fresh login
• billingType: stripe_subscription
• subscriptionCreatedAt: 2026-02-28T11:26:57.196041Z

What Should Happen?

claude rc should start a remote control session and display a session URL
and QR code as documented at https://code.claude.com/docs/en/remote-control

Error Messages/Logs

Error: Remote Control is not yet enabled for your account.

Steps to Reproduce

1. Run: claude rc
2. Observe: "Error: Remote Control is not yet enabled for your account."

Attempted fixes (all failed):

1. /logout then /login inside session
2. rm ~/.claude.json then claude /login (fresh config)
3. Verified Max plan active at claude.ai/settings/billing
4. Confirmed no CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC or

DISABLE_TELEMETRY in shell profile (~/.zshrc, ~/.zprofile)

Claude Model

None

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.144 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

~/.claude.json confirms:
"billingType": "stripe_subscription"
"subscriptionCreatedAt": "2026-02-28T11:26:57.196041Z"
"seatTier": null
"opusProMigrationComplete": true

Account is personal Gmail, not Team/Enterprise — no org admin involved.
Subscription created ~4 days after Remote Control launched (Feb 24).
Possible that new Max subscribers created post-launch weren't
auto-provisioned with the feature flag.

Related issues: #30242, #33119