{"version":"2.1.285","anchor":"chrome-tool-permission-checker-for-navigate-and-browser-batc","canonical_anchor":"chrome-tool-permission-checker-for-navigate-and-browser-batc","heading":"Claude in Chrome checks permissions for each navigation and batch action","tier":"notice","area":"Chrome & Browser","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/chrome-tool-permission-checker-for-navigate-and-browser-batc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Claude in Chrome checks permissions for each navigation and batch action\n\nClaude in Chrome now allows, blocks or asks about navigation and batched browser actions based on the web address and your domain rules\n\n**Unclear.** It is unclear whether this check replaces an earlier permission path for these actions or runs alongside it.\n\n**What**\n\nClaude in Chrome, which lets Claude control your Chrome browser, now runs a permission check before navigating or running a `browser_batch` call (one call that bundles several browser actions). The check works like this:\n\n- Addresses that are not ordinary web pages are refused.\n\n- Sites whose domain is on your deny list are refused.\n\n- Sites whose domain is on your allow list go ahead.\n\n- When the `chromeClassifierFloorEnabled` setting is on, Claude asks you before going ahead.\n\n- Input that cannot be read safely is refused with the message \"Can't run this Claude in Chrome action: its input couldn't be safely checked.\"\n\nFor a `browser_batch` call, each action inside the batch is checked on its own.\n\n**Why**\n\nBrowser navigation now follows per-domain permission rules, and a batch cannot slip an unchecked action past them.\n\n- Area: Chrome & Browser\n- Names: `browser_batch`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}