[BUG] Claude in Chrome blocks navigation/content access to specific domains even after granting "Full access"; persists across restarts
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 browser automation tool refuses to navigate to, or read content from,
certain domains — even after I explicitly granted the domain "Full access" in the Chrome
extension's own per-site permission panel (chrome://extensions icon > Claude).
Affected domains: eservices.knox.vic.gov.au, copp.t1cloud.com, www.portphillip.vic.gov.au,
and even www.google.com (tested as a neutral control).
Working domains in the same session with the same tooling: wyndham.t1cloud.com,
www.tenders.vic.gov.au.
The navigate action on a blocked domain returns: "Navigation to this domain is not allowed".
This persists across a full Chrome restart AND a full Claude Code session restart.
As a workaround, I had the user manually type the blocked URL into the address bar of a tab
that Claude in Chrome was already tracking (rather than Claude calling navigate itself). That
made the tab's URL/title become visible to the tool — but every further action on that same tab
still fails:
get_page_text→ "Permission denied for reading page content on this domain"computer(screenshot) → "Permission denied for this action on this domain"
I checked both ~/.claude/settings.json and the project's .claude/settings.local.json for a
browser domain allowlist — none exists. The browser tool permissions listed there are
unscoped (e.g. "mcp__claude-in-chrome__navigate" with no domain restriction), so whatever is
blocking these domains isn't visible or editable from any local settings file I have access to.
What Should Happen?
Granting a domain "Full access" in the Claude in Chrome extension's own permission UI should be
sufficient to allow navigation, content reading, and screenshots on that domain. If there's a
separate allowlist controlling this (account-level or server-side), there should be a visible
way to see and modify it, or a prompt to the user requesting access to a new domain — not a
silent, unexplained refusal that persists no matter what is granted in the visible UI.
Error Messages/Logs
Navigation to this domain is not allowed
Permission denied for reading page content on this domain
Permission denied for this action on this domain
Steps to Reproduce
- Open a Claude Code session with Claude in Chrome connected.
- Call the
navigateaction (mcp__claude-in-chrome__navigate) with url set to
"https://eservices.knox.vic.gov.au/ePathway/Production/Web/GeneralEnquiry/EnquiryLists.aspx"
- Observe error: "Navigation to this domain is not allowed"
- Open the Chrome extension's permissions panel (puzzle-piece icon > Claude > "This Can Read
and Change Site Data") on that exact domain and confirm/grant "Full access".
- Retry step 2 — same error persists.
- Restart Chrome entirely. Retry step 2 — same error persists.
- Restart the Claude Code session entirely. Retry step 2 — same error persists.
- As a workaround, manually type the blocked URL into the address bar of the SAME tab Claude
in Chrome already has open/tracked, and press Enter yourself (not via the navigate tool).
The tab's title/URL now becomes visible to tabs_context_mcp.
- Call
get_page_textorcomputer(screenshot) on that same tab. - Observe: "Permission denied for reading page content on this domain" /
"Permission denied for this action on this domain"
Note: the domain www.tenders.vic.gov.au and wyndham.t1cloud.com work fine with the exact same
tool calls in the exact same session — so this is domain-specific, not a general tool failure.
Claude Model
Sonnet (default)
Is this a regression?
No, this never worked
Last Working Version
_No response_
Claude Code Version
N/A — using Claude Code desktop app
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
This is happening inside the Claude Code desktop app (Code tab), not a terminal-invoked CLI
session. The browser automation is via the Claude in Chrome extension. I'm happy to provide
further diagnostic detail (session logs, extension version) on request.
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗