[BUG] claude-in-chrome navigate blocked on all domains ("Navigation to this domain is not allowed")

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?

Claude Code version: 2.1.143
Claude in Chrome extension version: 1.0.84
OS: Windows
Account type: Personal (not team/organization)

Bug: Every claude-in-chrome navigate call fails with "Navigation to this domain is not allowed", for ANY domain — including neutral test domains like https://example.com, not just a specific site.

Steps to reproduce:

1. Call mcp__claude-in-chrome__tabs_context_mcp — works fine, returns a valid tab list.
2. Call mcp__claude-in-chrome__navigate to any URL (tested with a real site and with https://example.com) — fails with: "Navigation to this domain is not allowed"
3. Call mcp__claude-in-chrome__read_page on the current tab — fails with a different message: "Permission denied for reading pages on this domain"

Already ruled out:

• Extension is enabled in Chrome (chrome://extensions), version 1.0.84.
• Site access is set to "On all sites" (most permissive setting).
• list_connected_browsers correctly shows the browser as connected (isLocal: true).
• Toggled the extension off/on to force a fresh reconnect — connectedAt timestamp updated (confirming a genuinely new handshake), but the error persisted identically afterward.
• select_browser with the correct deviceId — no change.
• switch_browser — reports "No other browsers available to switch to" (only one browser connected, so nothing to re-pair against).

Conclusion: Since two different actions (navigate vs read_page) return two distinct, specific error messages rather than a generic crash, the extension itself appears to be responding — but every action is being denied by some permission/policy layer, uniformly across all domains, even after a fresh reconnect. This points to a bug in the Claude Code ↔ Claude in Chrome connection/authorization layer rather than a local Chrome/extension misconfiguration.

Impact: Cannot use claude-in-chrome for any browser automation in this session — full functionality of the connector is blocked.

What Should Happen?

The navigate call should successfully load the requested URL in the connected Chrome tab, the way it did in previous sessions (browsing worked fine as recently as 2026-07-09).

Error Messages/Logs

Navigation to this domain is not allowed
Permission denied for reading pages on this domain

Steps to Reproduce

1. In a Claude Code session with the Claude in Chrome extension connected, call the MCP tool tabs_context_mcp — this succeeds and returns a valid tab list.
2. Call the MCP tool navigate with any URL, including a neutral test domain like https://example.com — this fails with "Navigation to this domain is not allowed".
3. Call the MCP tool read_page on the current tab — this fails with a different error: "Permission denied for reading pages on this domain".
4. In Chrome, confirm the extension is enabled, version 1.0.84, with Site access set to "On all sites".
5. Toggle the extension off and back on in chrome://extensions to force a fresh reconnect — list_connected_browsers shows a new connectedAt timestamp (fresh handshake), but step 2 still fails identically.
6. Try select_browser with the correct deviceId, and switch_browser — neither changes the outcome.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

Claude Code Version : 2.1.143 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_