[BUG] Remote Control fails with org_level_disabled on Pro plan (Linux)

Preflight Checklist

• [x] I have searched existing issues and this is related to: #28098, #29037, #29185, #29449, #30820
• [x] This is a single bug report
• [x] I am using the latest version of Claude Code

What's Wrong?

I'm a Claude Pro subscriber on Linux and /remote-control fails silently. The terminal shows "Remote Control connecting…" and then shows a "disabled" message / "Remote Control failed".

After inspecting .claude.json, I found my account is flagged as org_level_disabled:

"cachedExtraUsageDisabledReason": "org_level_disabled",
"remoteControlAtStartup": false,
"bridgeOauthDeadExpiresAt": 1774282410283,
"bridgeOauthDeadFailCount": 3

The source code confirms the check: isPolicyAllowed("allow_remote_control") returns false, resulting in:

"Remote Control is disabled by your organization's policy."

This is a personal Pro account (not a Team/Enterprise org), so there should be no org-level policy disabling this feature. Remote Control previously worked for me on this account.

What Should Happen?

Running /remote-control should successfully connect and display a session URL, allowing remote access from a mobile device or browser.

Error Messages

Remote Control connecting…
Remote Control is disabled by your organization's policy.

Debug log key entry:

[bridge:repl] Skipping: allow_remote_control policy not allowed
reason: policy_denied

Steps to Reproduce

1. Claude Pro subscription (claude.ai OAuth, not API key)
2. Install Claude Code v2.1.81 on Linux
3. Run /remote-control
4. See "connecting…" then failure

Environment

• Claude Code version: 2.1.81
• Plan: Claude Pro (claude.ai OAuth)
• OS: Linux (Debian 6.12.73, x86_64)
• Auth method: claude.ai OAuth

Is this a regression?

Yes, this worked in a previous version.

Related Issues

#28098, #29037, #29185, #29449, #30820, #30169