Anthropic's Browser Use hands Claude element refs, and hands you the browser

The bookkeeping is the part nobody ships for you. `read_page` returns a text rendering of the accessibility tree, produced by the developer's own executor, with links, buttons and text boxes tagged ^[4]. Claude replies with a reference such as `ref_3` plus the operation it wants, rather than working out that the button sits at x: 640, y: 320 ^[5]. Between the read and the click, the page can move underneath the reference, and the API will not notice: the executor has to hold the mapping, decide that a navigation has invalidated it, reject the action, and send Claude back to read the page again ^[6].

The batching arithmetic is worth doing before accepting the latency story. Several actions can now arrive as `tool_use` blocks in a single turn, executed in order with the results returned together ^[7], which Anthropic says lowers latency and cost as workflows grow from a handful of interactions to dozens or hundreds ^[8]. A hundred-interaction task at one model call per action is a hundred round trips; batched ten at a time it is ten ^[14]. The clicks themselves do not get faster, and because each action depends on the state the previous one left, a failed first click strands everything behind it in a page state Claude never reached ^[9]. Somebody has to write that unwind.

None of the perception work here is new. Playwright can represent a page as an ARIA snapshot and locate elements by role, and Microsoft's Playwright MCP server already hands models structured accessibility snapshots with references ^[10]. Puppeteer exposes the same tree through `Accessibility.snapshot()` and drives both Chrome and Firefox ^[12]. What is missing is the wiring: Playwright MCP speaks MCP while Anthropic's tool uses its own client-toolset protocol, so an adapter has to translate Claude's requests and return results in the shape Claude expects ^[11], with Anthropic's reference mappings maintained on top of whichever driver you already run ^[12]. There is also an unrelated open-source project called Browser Use that drives Chromium over the Chrome DevTools Protocol with its own agent loop, sharing the name and nothing else ^[13].

That puts the boundary in an unusual place. Anthropic's side emits requests; the developer's executor is the only component that reads or touches the page ^[3]. So the executor is also the only place a rule can be applied: which domains are reachable, and whether `ref_3` still points at the element Claude believed it did ^[15]. A refusal has to be written in application code, because an API that never performs the action cannot decline to perform it ^[15]. The same release moved Computer Use, the Skills API and the Files API into general availability ^[2], and Browser Use itself arrives as a versioned toolset name, `browser_toolset_20260801` ^[1], which is the part that will date fastest if reference semantics change.