Claude Cowork Chrome extension: 'Browser URL could not be parsed' on .tech TLD domains

Bug Description

The Claude-in-Chrome MCP extension consistently fails to interact with pages on .tech TLD domains. All interactive tools (click, form_input, javascript execution) return the error:

Browser URL could not be parsed

Screenshots work fine — only the interactive tools fail.

Steps to Reproduce

1. Navigate to any page on a .tech domain in Chrome (e.g., https://example.tech/page)
2. Ask Claude Cowork to interact with the page (click a button, fill a form, run JavaScript)
3. Every interactive tool returns "Browser URL could not be parsed"

Observed Behavior

• screenshot tool: Works (can see the page)
• click, form_input, javascript, find tools: All fail with "Browser URL could not be parsed"
• Tested on brain.fountaincity.tech (valid wildcard SSL cert from Google Trust Services, proper DNS via Cloudflare)
• Also fails on fountaincity.tech directly
• Standard domains (.com, .io) work fine in the same browser session

Expected Behavior

The Chrome extension should parse and interact with pages on all valid TLDs, including .tech.

Environment

• Chrome (latest stable)
• Claude Cowork Chrome extension (latest)
• Domain: brain.fountaincity.tech (Cloudflare DNS, valid wildcard SSL cert *.fountaincity.tech issued by Google Trust Services)
• CSP has been relaxed to allow unsafe-eval and chrome-extension: — no change in behavior

Workaround

Currently none. The user must manually interact with the page while Cowork watches via screenshots, which defeats the purpose of the automation.

Impact

Blocks automated workflows where Cowork needs to read content from a .tech domain dashboard and post it to other platforms (LinkedIn, Medium). The domain has a valid certificate and proper DNS — the only issue is the TLD.