claude-code - 💡(How to fix) Fix [BUG] reporting.xero.com blocked by Claude in Chrome MCP — "Navigation to this domain is not allowed" [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#51848Fetched 2026-04-23 07:43:19
View on GitHub
Comments
0
Participants
1
Timeline
6
Reactions
0
Participants
Timeline (top)
labeled ×4closed ×1cross-referenced ×1

Error Message

When Claude attempts to navigate to reporting.xero.com via the mcp__Claude_in_Chrome__navigate tool, it returns the error: Observe "Navigation to this domain is not allowed" error

Error Messages/Logs

This error is returned directly by the mcp__Claude_in_Chrome__navigate tool when attempting to navigate to any URL on reporting.xero.com. No further detail is provided in the error.

Code Example

Navigation to this domain is not allowed

This error is returned directly by the mcp__Claude_in_Chrome__navigate tool when attempting to navigate to any URL on reporting.xero.com. No further detail is provided in the error.
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

When Claude attempts to navigate to reporting.xero.com via the mcp__Claude_in_Chrome__navigate tool, it returns the error:

Navigation to this domain is not allowed

This occurs even when:

Chrome extension Site Access is set to "On all sites" mcp__Claude_in_Chrome__navigate is explicitly listed in settings.local.json permissions (no domain qualifier) The user has manually navigated to reporting.xero.com in the same browser session Impact: reporting.xero.com is Xero's reporting subdomain, used for Account Transactions, Balance Sheet, and Profit & Loss reports. These are core to accounting workflows. The main Xero app (go.xero.com) works fine — only the reporting subdomain is blocked.

Steps to reproduce:

Open a Claude Code session with Claude in Chrome enabled Ask Claude to navigate to reporting.xero.com/[any path] Observe "Navigation to this domain is not allowed" error Expected behaviour: Navigation succeeds (as it does for go.xero.com)

Environment:

Claude in Chrome Beta v1.0.68 Windows 11 Chrome (latest)

What Should Happen?

Claude in Chrome should be able to navigate to, read, and interact with reporting.xero.com in the same way it can with go.xero.com. The tool should not block subdomains of approved sites unless there is a specific security reason, and if a domain is blocked it should be documented so users know in advance.

Error Messages/Logs

Navigation to this domain is not allowed

This error is returned directly by the mcp__Claude_in_Chrome__navigate tool when attempting to navigate to any URL on reporting.xero.com. No further detail is provided in the error.

Steps to Reproduce

Open Claude Code with Claude in Chrome extension enabled (v1.0.68) In a Claude session, ask Claude to navigate to reporting.xero.com (e.g. "go to the Account Transactions report in Xero") Claude calls mcp__Claude_in_Chrome__navigate with URL reporting.xero.com/[any path] Tool immediately returns: Navigation to this domain is not allowed

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

v1.0.67 — navigation to reporting.xero.com worked correctly in the previous version. The block appears to have been introduced in v1.0.68.

Claude Code Version

Claude Code 2.1.109

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

No response

extent analysis

TL;DR

The issue can likely be resolved by reverting to the previous version of Claude in Chrome (v1.0.67) where navigation to reporting.xero.com was working correctly.

Guidance

  • Verify that the issue is indeed a regression by confirming that v1.0.67 allows navigation to reporting.xero.com as expected.
  • Check the release notes for v1.0.68 to see if there are any mentions of changes related to domain navigation or security that might be causing this issue.
  • Test if the issue persists when using a different Claude model or version of Claude Code to isolate if the problem is specific to the Sonnet model or Claude Code version 2.1.109.
  • Consider reaching out to the developers or support team for further assistance, as the error message does not provide detailed information about why the navigation is blocked.

Notes

The solution provided is based on the information given that the issue is a regression and was working in the previous version (v1.0.67). Without more detailed error logs or information about the changes in v1.0.68, reverting to the previous version seems like the most straightforward workaround.

Recommendation

Apply workaround: Revert to version v1.0.67 of Claude in Chrome, as it is confirmed to work correctly for navigating to reporting.xero.com. This is recommended because the issue is identified as a regression and the previous version is known to function as expected.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] reporting.xero.com blocked by Claude in Chrome MCP — "Navigation to this domain is not allowed" [1 participants]