Browser "Allowed sites" allowlist ignored — allowlisted site still prompts on every action ("Site-level permissions are disabled for this site")

Status Open

Maintainer reply None cached

Activity 0 comments · opened Oct 13, 2026

Summary

A host added to Settings → Claude Code → Browser → Allowed sites still triggers a permission prompt on every built-in Browser action, instead of running prompt-free as the setting promises ("Claude can use its Browser tools on these sites without a permission prompt. Remove a site and Claude asks again the next time that site needs your approval.").

Environment

Claude Code desktop app (Code tab), built-in Browser pane
macOS
Model: Opus 4.8

Steps to reproduce

Add a local dev host (e.g. a <name>.test host served over http://) to Settings → Claude Code → Browser → Allowed sites, and confirm it appears in the list.
Have Claude drive the built-in Browser pane on that host (navigate + click), e.g. during multi-page UI verification.
Every computer click raises a permission prompt:

> Allow Claude to click on <host>?
> Site-level permissions are disabled for this site. You'll be asked for each action.

…offering only Deny / Allow once (no "Always allow").

Expected

No per-action permission prompt for a site that is present in the Allowed sites list.

Actual

A prompt appears on every click. The dialog text "Site-level permissions are disabled for this site" directly contradicts the fact that the site is in the Allowed sites allowlist. Over a long browser session this produces hundreds/thousands of prompts and effectively blocks browser automation / subagent visual-QA on the allowlisted site.

Possible cause

The allowlist entries appear to be stored without a scheme (host.test), while the permission prompt's origin includes the scheme (http://host.test). This looks like an origin/scheme (and possibly port) matching mismatch, so the allowlist lookup never matches the requesting origin.

Impact

Multi-page browser automation and subagent-driven visual QA on an allowlisted local dev site are blocked by a flood of per-action prompts, despite the site being explicitly allowlisted.

View original on GitHub ↗