[FEATURE] Support wildcard/glob patterns in Claude in Chrome blocked sites list

Resolved 💬 2 comments Opened Mar 11, 2026 by AdamSutch Closed Apr 9, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

The Claude in Chrome team admin settings (under "Claude in Chrome settings" → "Blocked sites") only accept exact domain entries. There is no support for wildcard or glob patterns.

This means that if an organization wants to block an entire domain and all of its subdomains (e.g., everything under example.com), an admin must manually add every individual subdomain — app.example.com, api.example.com, staging.example.com, etc. This is impractical for domains with many subdomains, and new subdomains won't be blocked until manually added.

Proposed Solution

Allow wildcard/glob patterns in the "Blocked sites" list. For example:

*.example.com — blocks all subdomains of example.com
*.internal.company.com — blocks all subdomains under a specific subdomain

This is consistent with how wildcard patterns already work in other parts of Claude Code (e.g., network egress settings support *.example.com syntax).

Alternative Solutions

  • Manually listing every subdomain: not scalable, misses new subdomains
  • Blocking the root domain only: does not cover subdomains

Priority

High - Significant impact on productivity

Feature Category

Configuration and settings

Use Case Example

_No response_

Additional Context

This applies to the team-level admin "Blocked sites" configuration in the Claude in Chrome settings panel, where the default is set to "Allow extension" for all sites except those explicitly blocked.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗