[BUG] Claude in Chrome extension blocks navigation to all domains except one specific site (behaves like an allowlist)

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 Claude uses the Claude in Chrome extension to navigate to a website, navigation to boottent.com succeeds, but navigation to every other domain I've tried (google.com, spartacodingclub.kr, and others) fails immediately with the error Navigation to this domain is not allowed — even though the extension's own "Site access" setting in chrome://extensions is set to "On all sites" and I have not configured any domain whitelist myself.

This behaves as if some other allowlist (separate from the Chrome extension's site-access permission) is silently restricting navigation to a single domain, with no visible setting to view or change it, and no clear explanation given to the user about why it's happening. I re-checked and re-approved the extension's site access and retried navigation within the same session, but the restriction persisted.

What Should Happen?

The Claude in Chrome extension should allow navigation to any domain the user has granted site access to (currently set to "On all sites" in chrome://extensions), consistent with the extension's own permission settings. Since no domain whitelist has been configured by the user, Claude should be able to navigate to any website (e.g., google.com, spartacodingclub.kr) — not just boottent.com.

If there is an intentional session-level or backend domain allowlist restricting navigation, this should be either (a) surfaced to the user with a clear explanation of which domains are allowed and why, or (b) configurable/removable by the user, rather than silently blocking navigation with a generic "Navigation to this domain is not allowed" error that gives no indication of how to resolve it.

Error Messages/Logs

Steps to Reproduce

1. Install/enable the Claude in Chrome extension (v1.0.79) and confirm in chrome://extensions → Claude → Site access that it is set to "On all sites."
2. Start a Claude Code session that uses the Claude in Chrome MCP tools (e.g. mcp__claude-in-chrome__navigate).
3. Ask Claude to navigate to boottent.com (or have it navigate there as part of a task). Confirm this succeeds — the page loads normally.
4. In the same session, ask Claude to navigate to a different domain, e.g. https://www.google.com or https://spartacodingclub.kr.
5. Observe that navigation fails immediately with the error: Navigation to this domain is not allowed.
6. Go back to chrome://extensions → Claude → Site access and confirm it is still "On all sites" (no whitelist configured).
7. Retry step 4 in the same session — the error persists.

Expected result: Step 4 should succeed, since the extension has full site access and no whitelist was configured.

Actual result: Only boottent.com is reachable; all other domains are blocked with no way to view or change the restriction from the extension's UI.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

1.18286.0.0Unable to run claude --version directly (using the Claude Code desktop app, not a standalone CLI). App version shown in Windows Settings > Apps > Claude: 1.18286.0.0

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

I'm using the Claude in Chrome extension (v1.0.79) and running into a navigation restriction that seems unintended.

Symptom: When Claude uses mcp__claude-in-chrome__navigate (or the Claude in Chrome extension) to visit websites, navigation to boottent.com works fine, but navigation to other domains (e.g. google.com, spartacodingclub.kr) fails with the error: Navigation to this domain is not allowed.

What I've already checked: In chrome://extensions → Claude → Site access, the extension is set to "On all sites" and I have not configured any domain whitelist/restriction myself. So this doesn't appear to be a Chrome extension permission issue on my end.

Reproducibility: This has occurred consistently across multiple sessions over the past week. Re-approving the extension's site access and retrying did not resolve it within the same session.

Question: Is this an intended per-session domain restriction/allowlist feature, or a bug? If intended, is there a way for the user to see or configure which domains are allowed?