claude-code - 💡(How to fix) Fix [BUG] reporting.xero.com blocked by Claude in Chrome MCP — "Navigation to this domain is not allowed [1 comments, 2 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#51850Fetched 2026-04-23 07:43:15
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Timeline (top)
labeled ×4commented ×1

Error Message

When Claude attempts to navigate to reporting.xero.com via the mcp__Claude_in_Chrome__navigate tool, it returns the 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.

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 Note: go.xero.com navigates successfully in the same session. The block appears to be specific to the reporting.xero.com subdomain.

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 the Claude in Chrome extension (v1.0.67) where navigation to reporting.xero.com was working correctly.

Guidance

  • Verify that the issue is indeed specific to version v1.0.68 by testing with the previous version (v1.0.67) to confirm the regression.
  • Check the release notes or changelog for version v1.0.68 to see if there were any changes related to domain permissions or navigation that could be causing this issue.
  • If the issue persists, try manually adding an explicit permission for the reporting.xero.com subdomain in the settings.local.json file, even though it's already listed without a domain qualifier.
  • Test navigation to other subdomains of approved sites to see if the issue is specific to reporting.xero.com or if it's a broader problem with subdomain handling.

Example

No code snippet is provided as the issue seems to be related to configuration or versioning rather than a specific code error.

Notes

The solution is based on the information provided that the issue is a regression introduced in version v1.0.68. Without access to the codebase or more detailed error logs, it's challenging to provide a more specific fix. The guidance is aimed at helping the user isolate the issue and potentially find a workaround by reverting to a known working version.

Recommendation

Apply workaround: Revert to version v1.0.67 of the Claude in Chrome extension, as it is known to work correctly with reporting.xero.com, until a fix for the regression in v1.0.68 is available.

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 comments, 2 participants]