{"version":"2.1.275","anchor":"chromebrowser-tool-batch-url-checks-now-pre-screen-for-unv","canonical_anchor":"chromebrowser-tool-batch-url-checks-now-pre-screen-for-unv","heading":"Chrome\/browser tool: batch URL checks now pre-screen for unvettable\/denied domains across the whole batch","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/chromebrowser-tool-batch-url-checks-now-pre-screen-for-unv","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Chrome\/browser tool: batch URL checks now pre-screen for unvettable\/denied domains across the whole batch\n\nBatched browser URL checks now screen every URL in the batch, not just the first, before allowing the call\n\n**What**\n\nFor `browser_batch` tool calls, which bundle multiple browser actions into one call, Claude Code now checks every URL in the batch up front rather than just the primary one. If any URL in the batch is a non-web or unparseable address (like a browser-internal page), the whole call is denied with a message telling the user to navigate to a web page first. If any URL matches a denied-domain rule, the call is denied and the specific offending URL is named.\n\n**Why**\n\nThis closes a gap where a batched call could slip past domain restrictions or hit an internal browser page as long as only a secondary URL in the batch was the problem, instead of the first one being checked.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}