[BUG] Remote Control fails with "Remote Control server rejected the request (HTTP 403)" on Pro plan (Windows, Claude Desktop)

### Preflight Checklist

- [x] I have searched [existing issues](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug) and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code

### What's Wrong?

**Summary**
Remote Control worked correctly yesterday on my Pro plan account (Windows, Claude Desktop app, Code tab). Today, running `/remote-control` inside an active session consistently fails with:

Remote Control failed to connect: Remote Control server rejected the request (HTTP 403) — run /remote-control to retry

Retrying does not resolve it.

**Environment**
- OS: Windows 11
- Client: Claude Desktop app (Code tab)
- Bundled Claude Code CLI version: 2.1.260
- Plan: Pro

**Steps already tried (none resolved the issue)**
1. Fully signed out and signed back in on the Desktop app
2. Restarted the Desktop app
3. Ran `/remote-control` directly inside the session (same 403)
4. Ran the standalone bundled `claude.exe remote-control` from a separate terminal — this instead returned "You must be logged in to use Remote Control. Remote Control is only available with claude.ai subscriptions. Please use `/login`..." (a different, unauthenticated CLI context)
5. Checked for `DISABLE_TELEMETRY` and `CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC` environment variables at User/Machine/process level — none were set

**Additional context**
I found two community reports describing what appears to be the same class of issue (rollout/backend-side, not user-fixable):
- https://zenn.dev/otani_ai_memo/articles/claude-code-remote-control-fix
- https://did2memo.net/2026/03/01/claude-code-remote-control-failed-error/

The second article documents multiple Pro-plan users hitting the same "Remote Control failed" / "Bridge environments are not available for this organization" error shortly after Remote Control was opened up to Pro plans, with no user-side fix identified.

**Expected behavior**
Remote Control should connect successfully, as it did yesterday on this same account/device.

### What Should Happen?

**What should happen**
Remote Control should connect successfully and pair with my mobile device, the same way it did yesterday on this same account and device, allowing me to send instructions to this session remotely.

### Error Messages/Logs

```shell
Remote Control failed to connect: Remote Control server rejected the request (HTTP 403) — run
/remote-control
to retry
```

### Steps to Reproduce

**Steps already tried (none resolved the issue)**
1. Fully signed out and signed back in on the Desktop app
2. Restarted the Desktop app
3. Ran `/remote-control` directly inside the session (same 403)
4. Ran the standalone bundled `claude.exe remote-control` from a separate terminal — this instead returned "You must be logged in to use Remote Control. Remote Control is only available with claude.ai subscriptions. Please use `/login`..." (a different, unauthenticated CLI context)
5. Checked for `DISABLE_TELEMETRY` and `CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC` environment variables at User/Machine/process level — none were set

### Claude Model

None

### Is this a regression?

Yes, this worked in a previous version

### Last Working Version

_No response_

### Claude Code Version

1.46388.4

### Platform

Anthropic API

### Operating System

Windows

### Terminal/Shell

Windows Terminal

### Additional Information

Additional context
I found two community reports describing what appears to be the same class of issue (rollout/backend-side, not user-fixable):

https://zenn.dev/otani_ai_memo/articles/claude-code-remote-control-fix
https://did2memo.net/2026/03/01/claude-code-remote-control-failed-error/
The second article documents multiple Pro-plan users hitting the same "Remote Control failed" / "Bridge environments are not available for this organization" error shortly after Remote Control was opened up to Pro plans, with no user-side fix identified.

Expected behavior
Remote Control should connect successfully, as it did yesterday on this same account/device.

No repository file, test, or entry point is named. Start by locating the Remote Control connection flow and reproducing the HTTP 403 on Windows with Claude Desktop and a Pro account; done means identifying and fixing the rejected request so the session pairs successfully, with a regression test for the failure.

Vom Indexierungsmodell aus dem Issue-Text verfasst.