Claude-in-Chrome: Server-side domain blocking breaks legitimate business automation

Problem

The Claude-in-Chrome extension blocks browser automation on financial sites (Wells Fargo, Charles Schwab, and likely all banking/brokerage domains). The block message is "This site is blocked."

How it works

The extension calls api.anthropic.com/api/web/domain_info/browser_extension?domain=... which returns a category. Categories 1 and 2 trigger blocking. This is a server-side decision with no local override or configuration option.

Why this matters

I'm a small business owner on Maui who has spent hundreds of hours using Claude Code + Claude-in-Chrome for bookkeeping automation: downloading bank statements, reconciling transactions, navigating banking portals. This is core business infrastructure, not casual use.

The blocking appears to be new (or newly enforced). These workflows were working before and are now broken with no workaround.

Request

Please provide one of:

1. A way for account holders to allowlist domains for their own accounts (opt-in, acknowledging the risk)
2. An enterprise/business tier setting that permits financial site automation
3. At minimum, documentation of which domains are blocked and why, so users can plan around it

Environment

• Claude Code: 2.1.86
• Claude-in-Chrome extension: 1.0.64
• macOS Darwin 25.3.0
• Max plan subscriber

Context

The safety concern (preventing credential theft from untrusted content) makes sense for general use. But a business owner automating their own banking with their own credentials on their own machine is a legitimate use case that this blocking prevents. The server-side nature means there is zero workaround available.