Remote Control HTTP 403

“On Claude Desktop (macOS, Code tab), turning on Remote Control for a local session always fails with HTTP 403.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/claude-code/issues/17440/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Remote Control fails with HTTP 403 for in-session connections. Turning on Remote Control for an existing session returns "HTTP 403", while the standalone claude remote-control command connects on the same account.

Is this your bug?

File my report

Where: Remote Control
Error text: Remote Control failed to connect: Remote Control server rejected the request (HTTP 403) — run /remote-control to retry
Versions: 2.1.276
Platforms: macOS, Windows
How bad: Breaks a normal workflow.

Related: Remote sessions drop, never reconnect

Not quite your bug?

Remote Control HTTP 4034 people
Remote Control 403 on reattach3 people
Remote Control sessions go offline4 people

Original reports2, newest first

Nov 12, 2026Desktop (macOS): per-session Remote Control always fails with HTTP 403 since server started requiring trusted device; standalone CLI connects fine#109373
Sep 18, 2026Remote Control returns HTTP 403 on the in-session /bridge path, while claude remote-control works on the same machine and account#95413