Remote Control entitlement lost after May 27-28 incident — `Error: Remote Control is not yet enabled for your account` on active Max subscription

Summary

Claude Code Remote Control was working on my account (Claude Max, OAuth) until 2026-05-28 ~16:00 Asia/Taipei. After the May 27-28 incident recovery window, all claude remote-control subcommand variants return:

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

The error is identical and immediate across all variants, with no network probe — the entitlement check is server-side, gating the subcommand entry point.

Reproduction

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

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

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

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

What I've tried

• [x] claude auth login to refresh OAuth tokens — no change
• [x] /logout + /login inside REPL — no change
• [x] Verified all 6 documented disabling env vars are unset: ANTHROPIC_API_KEY, CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC, DISABLE_TELEMETRY, CLAUDE_CODE_USE_BEDROCK, CLAUDE_CODE_USE_VERTEX, CLAUDE_CODE_USE_FOUNDRY
• [x] Downgraded to 2.1.152 (and 2.1.150) — same error, ruling out a 2.1.153 client regression
• [x] Confirmed via Claude Help Center Fin chat (2026-05-29) — Fin could not resolve and recommended /feedback / GitHub Issue

Environment (from /status)

• Version: 2.1.153 (Claude Code)
• Login method: Claude Max account (OAuth)
• Organization: personal Max auto-org (no Team/Enterprise admin layer)
• Email: agoodbear@gmail.com
• macOS: Darwin 25.3.0
• ANTHROPIC_API_KEY: unset

Ask

This appears to be an account-level entitlement that was inadvertently revoked during incident recovery. Could the Claude Code team re-enable Remote Control on agoodbear@gmail.com?

Happy to provide additional diagnostic info on request.