{"version":"2.1.311","anchor":"browser-batch-unavailable-message","canonical_anchor":"browser-batch-unavailable-message","heading":"Claude in Chrome batches can be refused, with each action run as its own call instead","tier":"notice","area":"Claude in Chrome","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/browser-batch-unavailable-message","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Claude in Chrome batches can be refused, with each action run as its own call instead\n\nClaude in Chrome now refuses `browser_batch` in some cases, including auto mode with session allow rules, and tells Claude to make each action its own call\n\n**What**\n\nIn Claude in Chrome, a `browser_batch` call bundles several browser actions into one. There are now cases where the batch is refused and Claude is told to make each action its own call.\n\n- In auto mode (where Claude goes ahead without asking you each time), a `browser_batch` call is now refused when session allow rules exist. The message says \"Claude in Chrome: this call does not run in auto mode, so each action is its own call\". Before, the batch had each navigation address checked, without this refusal.\n\n- A new fixed message tells Claude: \"browser_batch isn't available right now, and nothing in this call ran. Make each action its own call instead. Don't retry it as a batch.\"\n\n- When a domain is allowed, Claude Code now records whether you left that decision to the classifier (the automatic safety check).\n\n- The handling of answers given from a phone was moved into a shared helper.\n\n**Why**\n\nIn auto mode, each Chrome action can now be checked one at a time instead of being run as part of a bundle. The new message also makes clear that nothing in the refused batch ran and that Claude should not try it again as a batch.\n\n- Area: Claude in Chrome\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}