Remote Control unavailable on Max subscription — feature flag not rolled out

Description

claude remote-control returns Error: Remote Control is not yet enabled for your account. and the /remote-control slash command shows as Unknown command inside sessions. Everything on my end appears eligible per the changelog notes.

Reproduction

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

Inside an interactive session:

> /remote-control
Unknown command: /remote-control

Environment

• CLI version: 2.1.112 (Claude Code)
• Auth method: claude.ai (firstParty)
• Subscription: max
• Org ID: abb12b6e-5f03-484b-a539-45c4089d61ce
• Platform: Linux 6.17.0-35-generic
• Shell: bash (VS Code integrated terminal)

Ruled out locally

• env | grep -iE "FOUNDRY|BEDROCK|VERTEX" — empty (no third-party provider override)
• env | grep -iE "DISABLE_TELEMETRY|NONESSENTIAL" — empty
• Same greps against ~/.bashrc, ~/.zshrc, ~/.profile, ~/.claude/settings.json, ~/.claude/settings.local.json — empty
• CLI version is well above the 2.1.74 minimum mentioned for phone-side sessions
• claude auth status returns loggedIn: true, authMethod: claude.ai, apiProvider: firstParty, subscriptionType: max

Expected

Since Max subscription + firstParty auth + recent CLI + no telemetry/provider overrides, Remote Control should be available (per changelog entries referencing /remote-control and claude remote-control).

Actual

Feature is gated off. Looks like a GrowthBook / backend rollout that hasn't reached this org yet.

Ask

Please enable the Remote Control feature flag for org \abb12b6e-5f03-484b-a539-45c4089d61ce\, or point me to the correct opt-in path if there's a manual toggle I've missed.

Thanks!