[BUG] Claude in Chrome 1.0.85: navigate and page reading denied on every domain except google.com, no approval prompt ever renders

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?

The Claude in Chrome extension denies both navigation and page reading for every domain
except google.com, even though the extension's site access is set to "On all sites" and the
"Read and change all your data on all websites" permission is granted.

The approval dialog that is supposed to populate the allowed-domain list never appears —
not in the side panel, not as a popup, not at the toolbar icon. I checked after every single
attempt. Because the prompt never renders, the list can never be filled and the block is
permanent.

This looks like the same underlying problem as #74696, #58464 and #56965, but it still
reproduces on extension 1.0.85 — newer than the 1.0.79 reported in #74696 — with Claude Code
2.1.237 and Chrome 146. So whatever shipped since does not cover this case.

Notable detail that may help locate the bug: navigating to a blocked domain fails, but
reaching the SAME domain by clicking a link succeeds. I navigated to a Google results page
(allowed), clicked the first result with computer/left_click, and the tab did load
https://www.wildbee.shop/ — confirmed via tabs_context_mcp. So the restriction is enforced
in the navigate path only, while the resulting page is still treated as unapproved for
reading.

What Should Happen?

With site access set to "On all sites", navigate should reach any domain. If a per-domain
approval is required by design, the approval prompt must actually render so the user can
grant it. Right now there is no path to approve a domain at all.

Error Messages/Logs

navigate -> https://example.com
Error: Navigation to this domain is not allowed

navigate -> https://www.wildbee.shop
Error: Navigation to this domain is not allowed

navigate -> https://www.google.com/search?q=...
OK

get_page_text        -> Error: Permission denied for reading page content on this domain
computer: screenshot -> Error: Permission denied for this action on this domain

Steps to Reproduce

1. In chrome://extensions, set the Claude extension's site access to "On all sites".
2. From Claude Code, connect to the browser (list_connected_browsers, select_browser) and

create a tab (tabs_context_mcp with createIfEmpty: true).

1. Call navigate with https://example.com

-> "Navigation to this domain is not allowed"

1. Open any non-google page in that same tab by clicking a link from a Google results page.
2. Call get_page_text on it

-> "Permission denied for reading page content on this domain", and no prompt appears.

Tried without success:

• Site access was already "On all sites" (verified in the extension details page).
• Updated the extension via chrome://extensions -> developer mode -> "Update", then fully

restarted Chrome. No change.

• Reconnected the browser and created fresh tabs. No change.
• Opening the target page first and calling get_page_text standalone (outside browser_batch)

to trigger the prompt. No prompt appeared.

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.237

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

Environment:

• OS: Windows 11 Home, 10.0.26200.0
• Chrome: 146.0.7680.81
• Claude in Chrome extension: 1.0.85
• Extension site access: On all sites
• Granted permission: "Read and change all your data on all websites"
• Surface: Claude Code desktop app

Additional observation: every failed navigation attempt caused the extension to create a new
tab group with a new tabId, discarding the previous one. Any cached tabId becomes stale, so
tabs_context_mcp has to be called again before each action. May or may not be related.

Impact: the extension is unusable for anything except Google. WebFetch works as a workaround
for public pages, but not for anything requiring a logged-in session — which is the main
reason to use the extension in the first place.