{"version":"2.1.290","anchor":"browser-batch-gets-its-own-tool-call-timeout","canonical_anchor":"browser-batch-gets-its-own-tool-call-timeout","heading":"Batched browser actions now have their own time limit","tier":"notice","area":"Chrome & Browser","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/browser-batch-gets-its-own-tool-call-timeout","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Batched browser actions now have their own time limit\n\nIn Claude in Chrome, `browser_batch` calls now use their own time limit instead of the default one other tools use\n\n**Unclear.** The actual time limits are not stated, so it is not known whether the batch limit is longer than the default.\n\n**What**\n\nIn Claude in Chrome, a `browser_batch` call bundles several browser actions into one. Claude Code now gives these calls their own time limit before it gives up waiting for them. All other tools keep the default limit.\n\n**Why**\n\nA batch of several browser actions can take longer than a single action, so it now has a separate limit from other tools.\n\n- Area: Chrome & Browser\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}