Rank, 14 days: 309 on the Claude Code sheet
4 people reported

All time, since Sep 16, including 1 thumbs-up on GitHub.

Remote Control HTTP 403

“Remote Control should activate, but will not with repeated 403 errors trying to connect to Remote Control server.”

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/17297/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

Fading. No reports and thumbs-up in the last 7 days and 1 the week before, down from 5 a week at the mid-September peak.

Remote Control fails with HTTP 403 in desktop app sessions. Enabling Remote Control fails instantly with "Remote Control server rejected the request (HTTP 403)", even after sign out/in and full app relaunch.

Is this your bug?

File my report
Where
Remote Control
Error text
Remote Control server rejected the request (HTTP 403)
Versions
2.2553.1
Platforms
macOS, Windows
How bad
Breaks a normal workflow. Most reports say it used to work. Some reports say it blocks them completely.

Not quite your bug?

  1. Remote Control 403 on reattach3 people
  2. Remote Control sessions go offline4 people
  3. Remote Control lost on relaunch61 people

Original reports3, newest first

  1. Remote Control: desktop app sessions always fail with HTTP 403 (CLI sessions connect fine)#95619
  2. Remote Control failed to connect: Remote Control server rejected the request (HTTP 403)#95173
  3. #94910

Do you work on Claude Code?

Claim its RAP Sheet to see what your users report and answer them in one place.