Claude in Chrome connector: remote navigate/action calls silently fail with "Navigation to this domain is not allowed" on every domain, even when paired to a verified-working browser instance

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?

When using Claude Code's Claude_in_Chrome MCP connector (navigate, computer, etc.), every action fails immediately with "Navigation to this domain is not allowed" — for every domain tested (mail.google.com, google.com, example.com), with zero approval prompt ever surfacing.

Diagnostic steps taken, all ruled out as the cause:

Account mismatch: Claude Code session and the Chrome extension are both logged into the same Claude.ai account.
Wrong paired browser: Re-confirmed via list_connected_browsers/select_browser that I was paired to the exact deviceId/browser instance the user had open.
Chrome's native extension permission: "Site access" is set to "On all sites."
Extension's own notification setting: "Task completion notifications" toggle was off, then turned on — no change.
Extension's "Approved sites" list (Permissions tab) shows "No sites have been approved yet," with no visible way to manually add a site, and no approval prompt ever appears when a remote/paired action is attempted.
Control test that isolates this to the remote-pairing channel specifically: the user opened the extension's own side panel and typed a message directly into it (e.g., "go to google.com"). That worked immediately — it showed an inline "approve this plan" prompt, the user approved it, and it navigated successfully. So the extension itself functions correctly when driven natively; the failure is specific to actions issued through the paired/remote Claude Code session.

What Should Happen?

Remote navigate calls from a paired Claude Code session should trigger the same kind of approval surface that native in-extension chat gets, or add the approved domain to the extension's "Approved sites" list.

Error Messages/Logs

Steps to Reproduce

Pair a Claude Code session with the Claude in Chrome extension via list_connected_browsers / select_browser (or switch_browser).
Confirm the extension is logged into the same Claude.ai account as the Claude Code session.
From Claude Code, call the connector's navigate tool with any URL (tested: mail.google.com, google.com, example.com).
Observe the call fails immediately with "Navigation to this domain is not allowed" — no approval prompt appears anywhere (not in the extension's side panel, not as a Chrome popup, not as an OS notification).
Check the extension's own Permissions tab → "Your approved sites" — it shows "No sites have been approved yet," with no way to manually add a domain.
As a control: open the extension's side panel directly and type a prompt like "go to google.com." This works immediately — it shows an inline "approve this plan" card, which when approved navigates successfully.
Repeat step 3 — it still fails identically, confirming the extension itself is functional but the remote/paired session's actions never get an approval surface.

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.170

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_