anthropics / anthropics/claude-code
[BUG] Remote Control failed to connect: Remote Control server rejected the request (HTTP 403)
- Dominant language
- Python
- Stars
- 145k
- Forks
- 23.1k
- PR merge metrics
- PR metrics pending
Description
### 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?
Plan: Pro/Max, account shows signed in on desktop
Phone cannot discover/see the desktop session at all — not just a retry failure, pairing itself isn't happening
No one else on your team/setup has this issue
Already tried: sign out/in (multiple times), full app restart, full machine reboot, clearing the stored auth token in Settings → Claude Code
### What Should Happen?
should be able to run /remote-control on desktop code and then be able to see my desktop on my phone app
### Error Messages/Logs
```shell
Remote Control failed to connect: Remote Control server rejected the request (HTTP 403)
```
### Steps to Reproduce
1 I logged out of claude desktop, logged back in.
2 on a code chat window, I type /remote-control
3 I see error "Remote Control failed to connect: Remote Control server rejected the request (HTTP 403)"
on phone, I log out , I log in. I go to and I don't see my desktop laptop listed.
### Claude Model
Sonnet (default)
### Is this a regression?
Yes, this worked in a previous version
### Last Working Version
same version
### Claude Code Version
Sonnet 5
### Platform
Anthropic API
### Operating System
macOS
### Terminal/Shell
Terminal.app (macOS)
### Additional Information
_No response_
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the /remote-control command and the reported HTTP 403 error, then trace the desktop-to-phone pairing flow and its authentication response. Compare the current behavior with the previously working version; done means the desktop session appears in the phone app without the server rejecting the request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- authentication, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100