{"version":"2.1.295","anchor":"claude-in-chrome-permission-checks-now-match-host80-and-add","canonical_anchor":"claude-in-chrome-permission-checks-now-match-host80-and-add","heading":"Claude in Chrome checks blocked sites more strictly","tier":"notice","area":"Chrome","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/claude-in-chrome-permission-checks-now-match-host80-and-add","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Claude in Chrome checks blocked sites more strictly\n\nClaude in Chrome now matches blocked sites with or without a port, and refuses actions when it cannot tell which site they target\n\n**What**\n\nClaude in Chrome lets Claude Code act in your Chrome browser. You can deny it certain sites. Those deny rules are now checked more strictly:\n\n- Each site is checked both by its name and by its name with a port number (the number after a colon in an address, such as `:80`).\n\n- A plain `http` address with no port is treated as port 80. A rule for that site with `:80` therefore also matches.\n\n- If Claude Code cannot tell which site an action would affect, and you have any deny rules, it refuses the action. It shows: \"Claude in Chrome could not tell which site this call would act on, so it could not check the sites that are denied.\"\n\nClaude Code also strips host-only arguments from the requests it sends to Chrome before they run.\n\n**Why**\n\nThis closes gaps through which an action could reach a site you had blocked. Examples are writing the address with a port, or sending an action whose target site could not be read. If you use deny rules, some actions that went through before may now be refused.\n\n- Area: Chrome\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}