Claude in Chrome: xero.com blocked (Navigation to this domain is not allowed)

Description

Claude in Chrome (browser automation via Claude Code) is being blocked from navigating to or interacting with xero.com (all subdomains tested: go.xero.com, www.xero.com, login.xero.com), while every other domain works normally in the same session.

Errors seen

• On navigate to any xero.com URL: Navigation to this domain is not allowed
• On computer/screenshot of an already-loaded, manually-authenticated xero.com page: Permission denied for this action on this domain

Neither error offers the normal one-time new-domain approval flow (compare: a genuinely new domain visited for the first time returns permission_required: <domain> — call navigate standalone so the user is prompted, which does work as expected once retried standalone). The xero.com errors are flat denials with no prompt offered.

Timeline

• Extensive successful Claude-in-Chrome automation on xero.com earlier the same session (viewing/creating/editing/sending quotes, changing Xero account settings, navigating multiple areas of the app) — worked without issue for an extended period.
• Returned to Xero later in the same day/session; the very first navigation attempt failed immediately with the error above. Not a gradual degradation after repeated attempts — already fully blocked on the first try after the working period.

Troubleshooting already ruled out (all produced the identical error)

• Fresh browser tab, fresh tab group
• Full Chrome restart
• Switching Chrome profile
• Confirmed Chrome's own extension "Site access" setting is "On all sites" (not a Chrome-side permission issue)
• User reset Claude's site-specific permission for xero.com in the extension's own settings — no change
• Full uninstall and reinstall of the Claude in Chrome extension — no change

Control tests (rule out Xero-side or network-side blocking)

• The user logged into Xero manually, normally, in a regular (non-automated) tab in the same browser — worked with no issues, no captcha, no warning.
• A different AI coding tool (OpenAI Codex, using its own separate browser automation) was able to open the same Xero account and navigate the Invoices tab normally, around the same time, on the same machine/network.

Both indicate this is not Xero's own bot-detection or a network/account-level block — it is specific to the Claude in Chrome extension's own requests to this domain.

Question

Is xero.com deliberately restricted for Claude in Chrome / Computer Use browser automation (for example, in favor of routing Xero access through Anthropic's official read-only Xero connector)? If so:

1. Is this intentional and expected to stay in place?
2. What is the supported path for a Claude Code user who needs full (not read-only) Xero interaction — quote/invoice creation, sending, settings changes — via browser automation going forward?

Happy to provide session logs or further detail if useful.