anthropics / anthropics/claude-code
[BUG]
- 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?
I just upgraded to v2.110.0 and immediately noticed I could not reactivate Remote Control mode. I had Claude investigate the issue internally and he produced this report below:
Claude Desktop 2.110.0 (Windows), Claude Code CLI auto-updated 2.1.270 → 2.1.271 at 2026-09-16 20:04.
Remote Control connected fine at 17:42 on 2.1.270. Every enable since the first session spawn on
2.1.271 (20:54:50) fails instantly:
[remote-control] bridge_state: "failed" — "Remote Control server rejected the request (HTTP 403)"
Reproduced 10x across re-login and full app relaunch; app reuses the cached OAuth token each time.
Device bridge (bridge.claudeusercontent.com) authenticates normally with the same account.
### What Should Happen?
Remote Control should activate, but will not with repeated 403 errors trying to connect to Remote Control server.
### Error Messages/Logs
```shell
```
### Steps to Reproduce
Upgrade from prior version to 2.110.0
Attempt to activate remote control in Claude Code chat using /Remote-Control command
Get Remote Control server connection failure 403 error
### Claude Model
Opus
### Is this a regression?
Yes, this worked in a previous version
### Last Working Version
_No response_
### Claude Code Version
not sure
### Platform
Anthropic API
### Operating System
Windows
### Terminal/Shell
PowerShell
### Additional Information
_No response_
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the regression on Windows with Claude Code 2.1.271 after upgrading from 2.1.270, using the /Remote-Control command, and inspect the bridge_state 403 response. Done means Remote Control activates successfully with the cached OAuth token after relogin and relaunch, without the Remote Control server rejecting the request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- api, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100