v2.1.92: `claude remote-control` returns "not yet enabled for your account" — regression vs 2.1.90/2.1.91
Summary
claude remote-control fails on v2.1.92 with Error: Remote Control is not yet enabled for your account. The same account works fine on v2.1.90 and v2.1.91 — strongly suggesting a client-side regression in 2.1.92, not a server entitlement change.
Environment
- macOS (Darwin 25.3.0)
- Claude Code installed via
claude install(native build) - Installed versions side-by-side: 2.1.90, 2.1.91, 2.1.92
- Account: personal Max subscription, firstParty auth, personal org
claude auth status:
\\\json\
{
"loggedIn": true,
"authMethod": "claude.ai",
"apiProvider": "firstParty",
"subscriptionType": "max"
}
\\
Reproduction
Same shell, same user, same minute, same \claude auth status\:
\\\`
$ ~/.local/share/claude/versions/2.1.90 remote-control
·✔︎· Connected · CodeBucket · HEAD
Capacity: 0/32 · New sessions will be created in the current directory
Continue coding in the Claude app or https://claude.ai/code?bridge=...
$ ~/.local/share/claude/versions/2.1.91 remote-control
·✔︎· Connected · CodeBucket · HEAD
Capacity: 0/32 · ...
Continue coding in the Claude app or https://claude.ai/code?environment=...
$ ~/.local/share/claude/versions/2.1.92 remote-control
Error: Remote Control is not yet enabled for your account.
\\\`
The \/remote-control\ slash command inside an interactive 2.1.92 session similarly returns \Unknown skill: remote-control\.
Why this looks client-side, not server-side
If entitlement had been revoked server-side, all three binaries would fail identically — the server is the source of truth. 2.1.90 and 2.1.91 successfully open a bridge with identical credentials, so the server is still granting access. 2.1.92 is producing the error itself.
Impact
Feature is the primary way to continue a local terminal session from the Claude mobile app / claude.ai/code. Workaround is to pin to 2.1.91, but \claude install latest\ reinstalls the broken 2.1.92.
Expected
\claude remote-control\ on 2.1.92 should behave as it does on 2.1.91.
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗