Claude in Chrome: Extension crashes when executing javascript_tool or read_page on certain pages
Resolved 💬 3 comments Opened Feb 25, 2026 by altpet Closed Mar 1, 2026
Bug Description
The Claude in Chrome browser extension consistently crashes Chrome when attempting to use read_page or javascript_tool on the Luma notifications page (luma.com/notifications). The crash occurs immediately upon tool execution — even a lightweight JS call like document.body.innerText.substring(0, 5000) triggers it.
Steps to Reproduce
- Connect to browser via
switch_browser(works fine) - Get tab context via
tabs_context_mcp(works fine) - User manually navigates a tab in the MCP group to
https://luma.com/notifications - Attempt
read_pageorjavascript_toolon that tab - Chrome crashes / extension disconnects
Environment
- OS: macOS (Darwin 24.6.0)
- Claude Code version: 2.1.52
- Browser: Chrome (work laptop)
- Extension: Claude in Chrome (latest)
What Works
switch_browser— connects successfully every timetabs_context_mcp— returns correct tab info including the Luma URLtabs_create_mcp— works
What Crashes
read_pageon the Luma tab — crashes Chromejavascript_toolon the Luma tab — crashes Chromenavigatetoluma.com— also caused crashes in earlier attempts
Additional Context
- Tried multiple times with fresh tab groups
- Tried varying
depthparameter onread_page - The Luma notifications page is a React SPA with dynamic content — may have a very large DOM
- The same extension works fine for
switch_browserandtabs_context_mcpcalls - Home PC Chrome extension connects but has the same issue pattern (permission denied / disconnect after initial connection)
Expected Behavior
read_page and javascript_tool should execute without crashing Chrome, even on complex SPAs. If the page is too large, a graceful error/truncation would be preferred over a crash.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗