Claude in Chrome batches can be refused, with each action run as its own call instead
Claude 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
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Claude in ChromeArea: what it touches
ImprovementsKind: in v2.1.311,
ImprovementsSection of the release
What
In 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.
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.
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."
When a domain is allowed, Claude Code now records whether you left that decision to the classifier (the automatic safety check).
The handling of answers given from a phone was moved into a shared helper.
Why
In 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.
