[BUG]

Preflight Checklist

• [x] I have searched existing issues 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?

Hi Anthropic Support,

I'm reporting a critical bug with Claude in Chrome that makes browser automation completely unusable.

Summary:
Chrome fully quits (all windows close) within 2-3 minutes of any browser automation via Claude in Chrome, whether triggered from claude.ai or Cowork Desktop.

Environment:

• Mac with Apple Silicon M4 Pro
• macOS 15.7.4 (Sequoia)
• 48GB RAM
• Claude Desktop version 1.1.4010
• Claude in Chrome extension version 1.0.54
• Chrome latest version

Reproduction steps:

1. Open Chrome with Claude in Chrome extension enabled
2. Start any browser automation task (from claude.ai or Cowork Desktop)
3. Chrome works for 1-3 minutes
4. Chrome quits entirely — all windows and tabs close

Troubleshooting already performed (all failed):

• Clean Chrome profile with ZERO other extensions → still crashes
• Disabled Adblock Plus, Email Tracker, GoFullPage, Lusha → still crashes
• Cleared /tmp/claude-mcp-browser-bridge socket files → no effect
• Verified only one native messaging host config exists (com.anthropic.claude_browser_extension.json)
• Confirmed no Claude Code CLI conflict
• Tested from both claude.ai and Cowork Desktop → same crash on both

Log evidence (from ~/Library/Logs/Claude/main.log):

• "[Claude in Chrome] Tool call timeout: computer (4efdde16) after 120003ms"
• "[Claude in Chrome] Error calling tool: [Claude in Chrome] Tool call timed out: computer"
• Repeated "Blocked permission check: background-sync from track.hubspot.com" (from a visited website, not user-installed)

Claude extension error log (chrome://extensions → Errors):

• "Executing inline script violates the following Content Security Policy directive 'script-src self'" on sidepanel.html:8
• "Loading the script 'https://cdn.segment.com/next-integrations/actions/amplitude-plugins/...' violates Content Security Policy"

These CSP errors suggest the sidePanel cannot fully initialize its scripts, which likely causes the tool calls to hang until timeout, eventually crashing Chrome.

Related GitHub issues:

• #27530 — Claude in Chrome causes repeated Chrome crashes on macOS Sequoia + Apple Silicon
• #27492 — Cowork MCP issue after Desktop auto-update
• #23221 — CSP blocking scripts in extension after Chrome update
• Chromium bug #355266358 — sidePanel API crash on macOS ARM

This bug makes Claude in Chrome completely unusable on Apple Silicon Macs. I'm a paying Max plan subscriber and this is a core feature I cannot use.

Please prioritize a workaround (e.g., fallback to popup/tab UI instead of sidePanel) rather than waiting on the upstream Chromium fix.

Thank you,
Octave van den Bosch

What Should Happen?

Google Chrome quits unexpectedly.

Error Messages/Logs

Steps to Reproduce

1. Open Chrome on macOS Sequoia 15.7.4 with Apple Silicon M4 Pro (48GB RAM)
2. Install Claude in Chrome extension (v1.0.54) — no other extensions needed
3. Open any website (e.g. linkedin.com)
4. Start a browser automation task from either claude.ai or Cowork Desktop
5. Chrome works normally for 1-3 minutes
6. Chrome quits entirely — all windows and tabs close simultaneously
7. Claude Desktop logs show: "Tool call timeout: computer after 120003ms"

Tested with:

• Clean Chrome profile with ZERO other extensions → still crashes
• Disabled all other extensions on main profile → still crashes
• Cleared /tmp/claude-mcp-browser-bridge socket files → no effect
• Verified single native messaging host config (no Claude Code CLI conflict)
• Both claude.ai and Cowork Desktop trigger the same crash

Related: Chromium bug #355266358 (sidePanel API crash on macOS ARM)
Related GitHub issues: #27530, #27492, #23221

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

1.0.54

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_