{"version":"2.1.242","anchor":"shape-rules-for-claude-in-chrome-batched-actions-off-without","canonical_anchor":"shape-rules-for-claude-in-chrome-batched-actions-off-without","heading":"Shape rules for Claude in Chrome batched actions, off without server config","tier":"soon","area":"Browser Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/shape-rules-for-claude-in-chrome-batched-actions-off-without","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Shape rules for Claude in Chrome batched actions, off without server config\n\nBrowser batch calls get strict shape rules with denials, but only under server config.\n\n**What**\n\nBrowser tool calls are inspected before they run: a batch must target exactly one tab, may not act on a page after navigating to it in the same batch, may not contain another batch, and switching browsers must be its own call. Violations are denied with a message explaining the correct shape, and the denial is a safety decision the permission classifier cannot approve. Enabled only when the server-supplied auto mode configuration sets Chrome navigation to true, which nothing in this build does locally.\n\n**Details**\n\n- The tab's URL is resolved and compared against the last URL executed for that scope, which is how the navigate-then-act case is detected.\n\n**Evidence**\n\n`Claude in Chrome: a browser_batch cannot act on a page after navigating to it. Issue the navigate on its own, then batch the actions on the loaded page.`\n\n- Area: Browser Control\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}