[BUG] Claude in Chrome v1.0.75 — "Navigation to this domain is not allowed" on all domains via Claude Code MCP

Open 💬 1 comment Opened Jun 6, 2026 by Weculp

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?

Every mcp__Claude_in_Chrome__navigate call returns "Navigation to this domain is not allowed", including benign domains like example.com. The block fires before any permission prompt appears, so approvals can never be granted. tabs_context and tabs_create still work, but navigate, screenshot, read_page, find, and click all fail. Related to #43255 and #50606 (same error string, v1.0.66+ regression), but those reports are macOS — this is on Windows 11, so the regression is not platform-specific.

What Should Happen?

Navigation to standard domains should succeed, or there should be a configurable allowlist so domains can be approved.
Error Messages/Logs
Navigation to this domain is not allowed

<img width="2030" height="504" alt="Image" src="https://github.com/user-attachments/assets/27b55c5b-fd4b-41ff-b522-c0a8bdde8941" />

Error Messages/Logs

Navigation to this domain is not allowed

Steps to Reproduce

1) Connect Claude Code to Chrome via the Claude in Chrome extension
2) Ask Claude to navigate to https://example.com/
3) Observe the error "Navigation to this domain is not allowed"

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.19

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

Claude Code inside the Windows desktop app's Code panel, not a standalone terminal. Extension is v1.0.75. Tried: restarting Chrome and the app, setting Site access to "On all sites" in chrome://extensions, and allowing the extension on all sites at claude.ai/settings/browser-extension. None resolved it. No way to install an older extension build via the Chrome Web Store.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗