claude-code - 💡(How to fix) Fix Remote Control "not yet enabled" on Max plan — v2.1.126 (Arch Linux)

Summary

claude remote-control errors with "Remote Control is not yet enabled for your account." on an active Max plan. /remote-control inside the TUI returns "Unknown command: /remote-control". This used to work on this same machine and login.

Repro

$ claude --version
2.1.126 (Claude Code)

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

In the TUI:

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

claude --help still lists --remote-control-session-name-prefix, so the binary knows the feature exists — it's just gated off for this account.

Tested with CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC unset and with CLAUDE_CODE_ENABLE_TELEMETRY=1 forced on — same error either way, so this isn't a telemetry-gate side effect.

Environment

• OS: Arch Linux, kernel 7.0.10-arch1-1
• Claude Code: 2.1.126 (/home/jonesy/.local/bin/claude)
• Plan: Max, active subscription, other features (chat, tools, plugins) all working normally
• Shell: bash

Note on prior reports

There are a lot of these (#61338, #60983, #56424, #54112, #46715, #43609, #38734, #37763, #37281, #36487, #36382, #35674, #35569, #34452, #34290, #31616, #31606, #29513, …) and they keep being auto-closed as duplicates within ~3 days by the duplicate-detection bot. The widely-suggested fix (delete ~/.claude.json + ~/.claude/, re-login) has not worked for several commenters across those threads. Repeated, unresolved reports of the same symptom across many users on the eligible plan suggest a real account/eligibility/feature-gate bug, not user misconfig — and the auto-close loop is suppressing the signal rather than addressing it.

Ask

Either confirmation of the actual eligibility/gating logic, or a fix. Happy to provide additional logs or run a debug build.