Browser batch calls get strict shape rules with denials, but only under server config.
Batch shape enforcement activates only when server auto-mode config sets Chrome navigation true, which nothing here does.
What's wrong with this entry?
Browser 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.
- 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.
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.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.239
Chrome tabs opened by a session are closed when it ends
Both mention browser
-
v2.1.248
Browser-consent dialog defaults to declining
Both mention browser
-
v2.1.239
Clearer message when Claude in Chrome is not connected
Both mention browser