claude-code - 💡(How to fix) Fix [BUG] Claude in Chrome (Beta) 1.0.70, macOS - sidepanel flickers between Log In and authenticated state; Cowork cannot connect to browser [1 comments, 2 participants]

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?

Right after installing Claude in Chrome on macOS, the extension popup/sidepanel rapidly flickers between the "Log In" screen and the authenticated view. The user is fully signed in to claude.ai in the same Chrome profile. The Claude Desktop app's "Claude in Chrome" connection feature is also unable to discover this browser (list_connected_browsers returns no devices on repeated retries).

Note: The Claude Desktop app itself is working perfectly on this machine — chat, file tools, Cowork mode. The issue is isolated to the Chrome extension and its connection channel back to Desktop.

What Should Happen?

Sidepanel should render the authenticated view immediately and consistently when the user is signed in to claude.ai, and Claude Desktop should be able to discover the browser.

Error Messages/Logs

**Console output from the sidepanel**

Two CSP violations blocking inline scripts in `sidepanel.html`:


Executing inline script violates the following Content Security Policy directive: "script-src 'self'". Either the 'unsafe-inline' keyword, a hash ('sha256-kFwyFWA0myfqRcE5y2d5UX8g0o2QFHSmCz1gWSW0xpk='), or a nonce ('nonce-...') is required to enable inline execution.



Executing inline script violates the following Content Security Policy directive: "script-src 'self' 'wasm-unsafe-eval' 'inline-speculation-rules'".


CSP violation blocking an external analytics script:


Loading the script 'https://cdn.segment.com/next-integrations/actions/amplitude-plugins/f12a4347e1080fb88155.js' violates the following Content Security Policy directive: "script-src 'self'". (script-src-elem was not explicitly set, so script-src is used as a fallback.) The action has been blocked.


Telemetry SDK initialised twice:


Datadog Browser SDK: SDK is loaded more than once. This is unsupported and might have unexpected behavior.
(at sidepanel-p3pTyYhf.js:2)


Async messaging race in PermissionManager (likely the root cause of the auth-state flicker):


PermissionManager-BqJmxUlR.js:3
Error: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received


No errors are produced from the extension's service worker; all network requests on the Network tab complete successfully.

Steps to Reproduce

1. Install Claude in Chrome (Beta) 1.0.70 on the environment above.
2. Sign in to claude.ai in the same Chrome profile.
3. Click the Claude extension icon (or open the side panel).
4. Observe: the panel oscillates between the Log In screen and the authenticated UI.
5. From Claude Desktop, attempt to connect to this Chrome — the browser does not appear in the device list.

Environment

• Device: MacBook Air M3 (Apple Silicon)
• OS: macOS Sequoia 15.7.3 (24G419)
• Chrome: 148.0.7778.167 (Official Build, arm64)
• Claude Desktop: 1.7196.0, build 2dbd78, 2026-05-12 — operating normally, no other defects observed
• Claude in Chrome (Beta): 1.0.70 (ID fcoeoabgfenejglbffodgkkbkcdhcgfn)
• No ad blockers or privacy extensions installed; Claude is the only extension
• Signed in to https://claude.ai in the same profile; session is valid
• Energy saver / Low Power Mode disabled

Claude Model

None

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.138

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response