claude-code - 💡(How to fix) Fix [BUG] issues #48806 and #44541 "OAuth token forbidden (403) — missing scope or org access" [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#55612Fetched 2026-05-03 04:48:55
View on GitHub
Comments
1
Participants
2
Timeline
8
Reactions
0
Author
Timeline (top)
labeled ×6commented ×1unlabeled ×1

After updating Claude Desktop to version 1.5354.0 on April 29, 2026, the Claude in Chrome bridge connection fails with OAuth token forbidden (403) - missing scope or org access. The Chrome extension works perfectly standalone in the browser, but Cowork sessions cannot connect to it.

Error Message

Actual Behavior The bridge WebSocket connects to wss://bridge.claudeusercontent.com/chrome/ but is immediately rejected with HTTP 403. Error from logs (%APPDATA%\Claude\logs\main.log): [Claude in Chrome] Connecting to bridge: wss://bridge.claudeusercontent.com/chrome/a4d76241-7a8e-41ec-9197-2362ddedb96a [Claude in Chrome] WebSocket connected, sending connect message [warn] [Claude in Chrome] Bridge error: OAuth token forbidden (403) - missing scope or org access [Claude in Chrome] Bridge connection closed (code: 1008, duration: 0ms) Token scope details: [oauth] looking up token for orgId=e8ac4c31-35a4-426c-a71e-ed845a4acc85, cacheKey=89355bc3-cbfd-4382-905b-976645cad410:e8ac4c31-35a4-426c-a71e-ed845a4acc85: https://api.anthropic.com:user:inference user:office The token scopes are user:inference user:office. The Chrome bridge rejects this token. What I've Already Tried (All Failed)

Reloading the Chrome extension (toggle off/on in chrome://extensions) Restarting Chrome Restarting Claude Desktop Signing out and back into Claude Desktop (fresh OAuth token obtained, still 403) Clearing Session Storage to force token refresh Toggling Claude in Chrome connector off/on in Settings > Connectors Full uninstall/reinstall of Claude Desktop

Root Cause

After updating Claude Desktop to version 1.5354.0 on April 29, 2026, the Claude in Chrome bridge connection fails with OAuth token forbidden (403) - missing scope or org access. The Chrome extension works perfectly standalone in the browser, but Cowork sessions cannot connect to it.

Code Example

Actual Behavior
The bridge WebSocket connects to wss://bridge.claudeusercontent.com/chrome/ but is immediately rejected with HTTP 403.
Error from logs (%APPDATA%\Claude\logs\main.log):
[Claude in Chrome] Connecting to bridge: wss://bridge.claudeusercontent.com/chrome/a4d76241-7a8e-41ec-9197-2362ddedb96a
[Claude in Chrome] WebSocket connected, sending connect message
[warn] [Claude in Chrome] Bridge error: OAuth token forbidden (403) - missing scope or org access
[Claude in Chrome] Bridge connection closed (code: 1008, duration: 0ms)
Token scope details:
[oauth] looking up token for orgId=e8ac4c31-35a4-426c-a71e-ed845a4acc85, 
cacheKey=89355bc3-cbfd-4382-905b-976645cad410:e8ac4c31-35a4-426c-a71e-ed845a4acc85:
https://api.anthropic.com:user:inference user:office
The token scopes are user:inference user:office. The Chrome bridge rejects this token.
What I've Already Tried (All Failed)

Reloading the Chrome extension (toggle off/on in chrome://extensions)
Restarting Chrome
Restarting Claude Desktop
Signing out and back into Claude Desktop (fresh OAuth token obtained, still 403)
Clearing Session Storage to force token refresh
Toggling Claude in Chrome connector off/on in Settings > Connectors
Full uninstall/reinstall of Claude Desktop

---

[Claude in Chrome] Connecting to bridge: wss://bridge.claudeusercontent.com/chrome/a4d76241-7a8e-41ec-9197-2362ddedb96a
[Claude in Chrome] WebSocket connected, sending connect message
[warn] [Claude in Chrome] Bridge error: OAuth token forbidden (403) - missing scope or org access
[Claude in Chrome] Bridge connection closed (code: 1008, duration: 0ms)

---

[oauth] looking up token for orgId=e8ac4c31-35a4-426c-a71e-ed845a4acc85, 
cacheKey=89355bc3-cbfd-4382-905b-976645cad410:e8ac4c31-35a4-426c-a71e-ed845a4acc85:
https://api.anthropic.com:user:inference user:office

---

[oauth] no cached token found for orgId=e8ac4c31-35a4-426c-a71e-ed845a4acc85
[oauth] performing fresh oauth exchange for orgId=e8ac4c31-35a4-426c-a71e-ed845a4acc85
[oauth] obtained new token for orgId=e8ac4c31-35a4-426c-a71e-ed845a4acc85, caching
...
[warn] [Claude in Chrome] Bridge error: OAuth token forbidden (403) - missing scope or org access

---

[Claude in Chrome] Connecting to bridge: wss://bridge.claudeusercontent.com/chrome/a4d76241-7a8e-41ec-9197-2362ddedb96a
[Claude in Chrome] WebSocket connected, sending connect message
[warn] [Claude in Chrome] Bridge error: OAuth token forbidden (403) - missing scope or org access
[Claude in Chrome] Bridge connection closed (code: 1008, duration: 0ms)

---

[oauth] looking up token for orgId=e8ac4c31-35a4-426c-a71e-ed845a4acc85, 
cacheKey=89355bc3-cbfd-4382-905b-976645cad410:e8ac4c31-35a4-426c-a71e-ed845a4acc85:
https://api.anthropic.com:user:inference user:office

---

[oauth] no cached token found for orgId=e8ac4c31-35a4-426c-a71e-ed845a4acc85
[oauth] performing fresh oauth exchange for orgId=e8ac4c31-35a4-426c-a71e-ed845a4acc85
[oauth] obtained new token for orgId=e8ac4c31-35a4-426c-a71e-ed845a4acc85, caching
...
[warn] [Claude in Chrome] Bridge error: OAuth token forbidden (403) - missing scope or org access
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Summary After updating Claude Desktop to version 1.5354.0 on April 29, 2026, the Claude in Chrome bridge connection fails with OAuth token forbidden (403) - missing scope or org access. The Chrome extension works perfectly standalone in the browser, but Cowork sessions cannot connect to it.

What Should Happen?

Expected Behavior Cowork session connects to the Chrome extension via the bridge and browser tools work normally (this was working before the update).

Error Messages/Logs

Actual Behavior
The bridge WebSocket connects to wss://bridge.claudeusercontent.com/chrome/ but is immediately rejected with HTTP 403.
Error from logs (%APPDATA%\Claude\logs\main.log):
[Claude in Chrome] Connecting to bridge: wss://bridge.claudeusercontent.com/chrome/a4d76241-7a8e-41ec-9197-2362ddedb96a
[Claude in Chrome] WebSocket connected, sending connect message
[warn] [Claude in Chrome] Bridge error: OAuth token forbidden (403) - missing scope or org access
[Claude in Chrome] Bridge connection closed (code: 1008, duration: 0ms)
Token scope details:
[oauth] looking up token for orgId=e8ac4c31-35a4-426c-a71e-ed845a4acc85, 
cacheKey=89355bc3-cbfd-4382-905b-976645cad410:e8ac4c31-35a4-426c-a71e-ed845a4acc85:
https://api.anthropic.com:user:inference user:office
The token scopes are user:inference user:office. The Chrome bridge rejects this token.
What I've Already Tried (All Failed)

Reloading the Chrome extension (toggle off/on in chrome://extensions)
Restarting Chrome
Restarting Claude Desktop
Signing out and back into Claude Desktop (fresh OAuth token obtained, still 403)
Clearing Session Storage to force token refresh
Toggling Claude in Chrome connector off/on in Settings > Connectors
Full uninstall/reinstall of Claude Desktop

Steps to Reproduce

Bug Report: Claude in Chrome Bridge Failure in Cowork Mode After Desktop Update

Summary

After updating Claude Desktop to version 1.5354.0 on April 29, 2026, the Claude in Chrome bridge connection fails with OAuth token forbidden (403) - missing scope or org access. The Chrome extension works perfectly standalone in the browser, but Cowork sessions cannot connect to it.

Environment

  • Claude Desktop Version: 1.5354.0 (MSIX, installed April 29, 2026)
  • OS: Windows 11 (10.0.26200), CoreSingleLanguage, x64
  • Chrome Extension Version: 1.0.69 (Claude in Chrome Beta)
  • Chrome Extension ID: fcoeoabgfenejglbffodgkkbkcdhcgfn
  • Plan: Pro ($21/month, active, last invoice April 23, 2026)
  • Account Email: [email protected]

Steps to Reproduce

  1. Update Claude Desktop to version 1.5354.0
  2. Open Chrome with Claude in Chrome extension installed and signed in
  3. Open a Cowork session
  4. Attempt any browser tool (e.g., tabs_context_mcp)
  5. Connection fails with "Claude in Chrome is not connected"

Expected Behavior

Cowork session connects to the Chrome extension via the bridge and browser tools work normally (this was working before the update).

Actual Behavior

The bridge WebSocket connects to wss://bridge.claudeusercontent.com/chrome/ but is immediately rejected with HTTP 403.

Error from logs (%APPDATA%\Claude\logs\main.log):

[Claude in Chrome] Connecting to bridge: wss://bridge.claudeusercontent.com/chrome/a4d76241-7a8e-41ec-9197-2362ddedb96a
[Claude in Chrome] WebSocket connected, sending connect message
[warn] [Claude in Chrome] Bridge error: OAuth token forbidden (403) - missing scope or org access
[Claude in Chrome] Bridge connection closed (code: 1008, duration: 0ms)

Token scope details:

[oauth] looking up token for orgId=e8ac4c31-35a4-426c-a71e-ed845a4acc85, 
cacheKey=89355bc3-cbfd-4382-905b-976645cad410:e8ac4c31-35a4-426c-a71e-ed845a4acc85:
https://api.anthropic.com:user:inference user:office

The token scopes are user:inference user:office. The Chrome bridge rejects this token.

What I've Already Tried (All Failed)

  1. Reloading the Chrome extension (toggle off/on in chrome://extensions)
  2. Restarting Chrome
  3. Restarting Claude Desktop
  4. Signing out and back into Claude Desktop (fresh OAuth token obtained, still 403)
  5. Clearing Session Storage to force token refresh
  6. Toggling Claude in Chrome connector off/on in Settings > Connectors
  7. Full uninstall/reinstall of Claude Desktop

Key Diagnostic Finding

Even after a full sign-out/sign-in cycle, the NEW token still gets 403:

[oauth] no cached token found for orgId=e8ac4c31-35a4-426c-a71e-ed845a4acc85
[oauth] performing fresh oauth exchange for orgId=e8ac4c31-35a4-426c-a71e-ed845a4acc85
[oauth] obtained new token for orgId=e8ac4c31-35a4-426c-a71e-ed845a4acc85, caching
...
[warn] [Claude in Chrome] Bridge error: OAuth token forbidden (403) - missing scope or org access

This confirms the issue is server-side, not a cached token problem.

Configuration Verified Correct

  • Claude in Chrome connector: Enabled (Settings > Connectors)
  • Allow all browser actions: ON (Settings > General)
  • Computer use: Enabled
  • Chrome Native Messaging Host: Registered (com.anthropic.claude_browser_extension in HKCU registry)
  • Native host executable exists: %APPDATA%\Claude\ChromeNativeHost\chrome-native-host.exe
  • Extension ID in allowed_origins: Yes (fcoeoabgfenejglbffodgkkbkcdhcgfn)

Related GitHub Issues

  • #48806 - Claude in Chrome + Control Chrome Failures in Cowork Mode
  • #44541 - Chrome Connection not possible with Cowork
  • #41034 - Claude in Chrome - all sites blocked in Cowork mode (was working previously)

Request

Please investigate the server-side bridge authentication at bridge.claudeusercontent.com for this account. The OAuth token exchange works but the bridge rejects the token with 403, suggesting a missing scope that the desktop app should be requesting but isn't, or a server-side permission that needs to be granted for this account.

Claude Model

Not sure / Multiple models

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

Claude Desktop Version: 1.5354.0 (MSIX, installed April 29, 2026)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

Bug Report: Claude in Chrome Bridge Failure in Cowork Mode After Desktop Update

Summary

After updating Claude Desktop to version 1.5354.0 on April 29, 2026, the Claude in Chrome bridge connection fails with OAuth token forbidden (403) - missing scope or org access. The Chrome extension works perfectly standalone in the browser, but Cowork sessions cannot connect to it.

Environment

  • Claude Desktop Version: 1.5354.0 (MSIX, installed April 29, 2026)
  • OS: Windows 11 (10.0.26200), CoreSingleLanguage, x64
  • Chrome Extension Version: 1.0.69 (Claude in Chrome Beta)
  • Chrome Extension ID: fcoeoabgfenejglbffodgkkbkcdhcgfn
  • Plan: Pro ($21/month, active, last invoice April 23, 2026)
  • Account Email: [email protected]

Steps to Reproduce

  1. Update Claude Desktop to version 1.5354.0
  2. Open Chrome with Claude in Chrome extension installed and signed in
  3. Open a Cowork session
  4. Attempt any browser tool (e.g., tabs_context_mcp)
  5. Connection fails with "Claude in Chrome is not connected"

Expected Behavior

Cowork session connects to the Chrome extension via the bridge and browser tools work normally (this was working before the update).

Actual Behavior

The bridge WebSocket connects to wss://bridge.claudeusercontent.com/chrome/ but is immediately rejected with HTTP 403.

Error from logs (%APPDATA%\Claude\logs\main.log):

[Claude in Chrome] Connecting to bridge: wss://bridge.claudeusercontent.com/chrome/a4d76241-7a8e-41ec-9197-2362ddedb96a
[Claude in Chrome] WebSocket connected, sending connect message
[warn] [Claude in Chrome] Bridge error: OAuth token forbidden (403) - missing scope or org access
[Claude in Chrome] Bridge connection closed (code: 1008, duration: 0ms)

Token scope details:

[oauth] looking up token for orgId=e8ac4c31-35a4-426c-a71e-ed845a4acc85, 
cacheKey=89355bc3-cbfd-4382-905b-976645cad410:e8ac4c31-35a4-426c-a71e-ed845a4acc85:
https://api.anthropic.com:user:inference user:office

The token scopes are user:inference user:office. The Chrome bridge rejects this token.

What I've Already Tried (All Failed)

  1. Reloading the Chrome extension (toggle off/on in chrome://extensions)
  2. Restarting Chrome
  3. Restarting Claude Desktop
  4. Signing out and back into Claude Desktop (fresh OAuth token obtained, still 403)
  5. Clearing Session Storage to force token refresh
  6. Toggling Claude in Chrome connector off/on in Settings > Connectors
  7. Full uninstall/reinstall of Claude Desktop

Key Diagnostic Finding

Even after a full sign-out/sign-in cycle, the NEW token still gets 403:

[oauth] no cached token found for orgId=e8ac4c31-35a4-426c-a71e-ed845a4acc85
[oauth] performing fresh oauth exchange for orgId=e8ac4c31-35a4-426c-a71e-ed845a4acc85
[oauth] obtained new token for orgId=e8ac4c31-35a4-426c-a71e-ed845a4acc85, caching
...
[warn] [Claude in Chrome] Bridge error: OAuth token forbidden (403) - missing scope or org access

This confirms the issue is server-side, not a cached token problem.

Configuration Verified Correct

  • Claude in Chrome connector: Enabled (Settings > Connectors)
  • Allow all browser actions: ON (Settings > General)
  • Computer use: Enabled
  • Chrome Native Messaging Host: Registered (com.anthropic.claude_browser_extension in HKCU registry)
  • Native host executable exists: %APPDATA%\Claude\ChromeNativeHost\chrome-native-host.exe
  • Extension ID in allowed_origins: Yes (fcoeoabgfenejglbffodgkkbkcdhcgfn)

Related GitHub Issues

  • #48806 - Claude in Chrome + Control Chrome Failures in Cowork Mode
  • #44541 - Chrome Connection not possible with Cowork
  • #41034 - Claude in Chrome - all sites blocked in Cowork mode (was working previously)

Request

Please investigate the server-side bridge authentication at bridge.claudeusercontent.com for this account. The OAuth token exchange works but the bridge rejects the token with 403, suggesting a missing scope that the desktop app should be requesting but isn't, or a server-side permission that needs to be granted for this account.

extent analysis

TL;DR

The most likely fix is to investigate and update the OAuth token scopes requested by the Claude Desktop application to include the necessary permissions for the Chrome bridge connection.

Guidance

  1. Verify OAuth token scopes: Check the current OAuth token scopes requested by the Claude Desktop application and compare them with the required scopes for the Chrome bridge connection.
  2. Update OAuth token scopes: If the necessary scopes are missing, update the Claude Desktop application to request the required scopes during the OAuth token exchange process.
  3. Test with updated token: After updating the OAuth token scopes, test the Chrome bridge connection with a new token to ensure the issue is resolved.
  4. Check server-side permissions: If the issue persists, investigate server-side permissions and ensure that the account has the necessary permissions to access the Chrome bridge.
  5. Review related GitHub issues: Examine related GitHub issues (#48806, #44541, #41034) to see if others have experienced similar problems and if there are any known workarounds or fixes.

Example

No code snippet is provided as the issue is related to OAuth token scopes and server-side configuration, which cannot be resolved with a simple code change.

Notes

The issue is likely caused by a missing scope in the OAuth token or a server-side permission issue. The fact that the Chrome extension works standalone but fails in Cowork mode suggests a problem with the bridge connection. The error message "OAuth token forbidden (403) - missing scope or org access" indicates that the token is being rejected due to insufficient permissions.

Recommendation

Apply a workaround by investigating and updating the OAuth token scopes requested by the Claude Desktop application to include the necessary permissions for the Chrome bridge connection. This should resolve the issue and allow the Chrome bridge connection to work as expected.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] issues #48806 and #44541 "OAuth token forbidden (403) — missing scope or org access" [1 comments, 2 participants]