Rank, 14 days: 52 on the Claude Code sheet
3 people reported
All time, since Nov 10, including 1 thumbs-up on GitHub.
Chrome bridge 403 rejection
“The debug log shows the real cause: the bridge rejects Claude Code's OAuth token with a 403 before the extension is ever contacted.”
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/27432/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
Chrome bridge rejects valid OAuth token with 403, extension reported not connected. Bridge closes the connection to wss://bridge.claudeusercontent.com/chrome/ with "OAuth token forbidden (403)" while the extension is signed in and the side panel works.
Is this your bug?
File my report- Where
- Claude in Chrome
- Error text
OAuth token forbidden (403) - missing scope, org access, or net- Versions
- 2.1.321 to 2.1.322. Still reported on the newest version, 2.1.322.
- Platforms
- macOS, Windows
- How bad
- Stops work: a core feature can't be used.
Not quite your bug?
- Chrome extension never connects13 people
- Chrome disconnected after account switch4 people
- Chrome extension not connecting2 people