claude-code - 💡(How to fix) Fix [BUG] Claude in Chrome: screenshot/debugger API fails with 'Cannot access a chrome-extension:// URL' even on clean profile with no other extensions [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#45221Fetched 2026-04-09 08:10:28
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
Timeline (top)
labeled ×5commented ×1

Error Message

Error capturing screenshot: Cannot access a chrome-extension:// URL of different extension The error message is misleading: the active tab is on a regular https:// URL (e.g., https://www.google.com), NOT a chrome-extension:// URL. The error suggests a cross-extension URL access issue, but no extension URL is involved — the debugger API simply fails to attach to any tab. 7. Attempt computer(screenshot) → fails with the chrome-extension:// error even though the tab URL is https://

  • #16239 — same error, but resolved by disabling extensions (not the case here)
  • #29790 — same error on Anthropic websites

Fix Action

Fix / Workaround

  • #16239 — same error, but resolved by disabling extensions (not the case here)
  • #29790 — same error on Anthropic websites

Code Example

Error capturing screenshot: Cannot access a chrome-extension:// URL of different extension
RAW_BUFFERClick to expand / collapse

Bug Description

Screenshot and all debugger-based tools (screenshot, javascript_tool, left_click) fail with:

Error capturing screenshot: Cannot access a chrome-extension:// URL of different extension

The error message is misleading: the active tab is on a regular https:// URL (e.g., https://www.google.com), NOT a chrome-extension:// URL. The error suggests a cross-extension URL access issue, but no extension URL is involved — the debugger API simply fails to attach to any tab.

What Works vs. What Fails

ToolAPI UsedStatus
tabs_context_mcpChrome tabs API✅ Works
tabs_create_mcpChrome tabs API✅ Works
navigateChrome tabs API✅ Works
read_pageAccessibility tree✅ Works
findAccessibility tree✅ Works
screenshotchrome.debugger API❌ Fails
javascript_toolchrome.debugger API❌ Fails
left_clickchrome.debugger API❌ Not tested but likely fails

All tools using the chrome.debugger API fail. All tools using the accessibility tree or tabs API work fine.

Steps to Reproduce

  1. Create a brand new Chrome profile
  2. Install only the Claude in Chrome extension
  3. Close all other Chrome profiles and Chromium browsers
  4. Restart Chrome completely (Cmd+Q and reopen)
  5. Connect Claude Code to the extension
  6. Navigate to any regular https:// URL (e.g., https://www.google.com)
  7. Attempt computer(screenshot) → fails with the chrome-extension:// error even though the tab URL is https://

Troubleshooting Already Attempted

  • ✅ Created a clean Chrome profile with only Claude in Chrome installed
  • ✅ Disabled all other extensions
  • ✅ Enabled "Allow JavaScript from Apple Events" (Chrome → View → Developer)
  • ✅ Closed all other Chromium-based browsers
  • ✅ Full Chrome restart (Cmd+Q)
  • ✅ Created new tabs and navigated to fresh URLs
  • ✅ Tested on multiple domains (google.com, smiles.com.br, voegol.com.br)
  • ❌ None of the above resolved the issue

Environment

  • OS: macOS (Darwin 25.3.0)
  • Chrome: 146.0.7680.178
  • Claude Code: 2.1.96

Related Issues

  • #16239 — same error, but resolved by disabling extensions (not the case here)
  • #29790 — same error on Anthropic websites

extent analysis

TL;DR

The issue is likely related to the chrome.debugger API failing to attach to tabs, and a potential workaround is to investigate alternative methods for capturing screenshots and executing JavaScript tools.

Guidance

  • Investigate the chrome.debugger API documentation to see if there are any known issues or limitations that could be causing the problem.
  • Consider using alternative APIs, such as the tabs API or accessibility tree, to capture screenshots or execute JavaScript tools, as these APIs seem to be working fine.
  • Verify that the issue is not specific to the Claude in Chrome extension by testing with other extensions or a clean Chrome profile.
  • Check if there are any updates available for Chrome or the Claude Code extension that may resolve the issue.

Example

No code snippet is provided as the issue seems to be related to the chrome.debugger API and not a specific code implementation.

Notes

The issue seems to be specific to the chrome.debugger API, and the error message is misleading. The fact that other APIs, such as tabs and accessibility tree, are working fine suggests that the issue is not related to the Chrome profile or extension configuration.

Recommendation

Apply workaround: Investigate alternative methods for capturing screenshots and executing JavaScript tools, such as using the tabs API or accessibility tree, as these APIs seem to be working fine. This is because the chrome.debugger API is failing to attach to tabs, and using alternative APIs may provide a temporary solution until the issue is resolved.

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] Claude in Chrome: screenshot/debugger API fails with 'Cannot access a chrome-extension:// URL' even on clean profile with no other extensions [1 comments, 2 participants]