Computer use goes GA with a new request shape, and browser automation becomes something you buy

Start with the name. The tool ships as `computer_toolset_20260801` ^[2], and the brief's advice to pin that string in exactly one place ^[7] describes the maintenance ahead more honestly than "out of beta" does. A dated toolset identifier means the schema is a versioned artefact, and versioned artefacts get superseded on a calendar you do not set.

The arithmetic is worth a second. The identifier carries 2026-08-01, while the release entry is dated August 19 ^[1], eighteen days later ^[8]. The version was minted before it was announced, which is ordinary, and also the reason the next rename will arrive the same way: as something you read about after it has been decided.

"Not a header swap" ^[3] is the load-bearing phrase. A header-gated beta comes off with a one-line diff and a test run. Adjusting the request structure means the code that builds the tool block changes, and batch actions ^[2] mean the code reading model output changes too. An executor written on the assumption of one action per turn will not throw an error; it will quietly perform fewer actions than the model asked for. That is the class of failure that survives a smoke test and shows up as a flaky agent three weeks later. The new configuration system ^[2] points at the same place: wherever your request assembly currently hardcodes tool parameters.

The browser toolset ^[6] is the half with a budget attached. Per the brief, vendor-hosted browser automation is becoming an API primitive, which moves the build-vs-buy line for anyone maintaining a Playwright-plus-prompts stack ^[4]. What changes hands is not capability for capability but one maintenance surface for another: a driver and browser stack you upgrade yourself, traded for a toolset string the vendor bumps and a request shape you follow. Teams that priced their own harness against model quality alone were pricing the wrong side of it.

One caution on provenance. All of this comes from a weekly engineering brief on dev.to citing Claude Platform release notes dated August 19 and fetched August 24 ^[5]; the notes themselves are not in front of me. The brief's own framing of the sequencing is the useful part: book the migration rather than meet it when the beta versions are retired ^[9]. The retirement date belongs to Anthropic. The ordering of your work is the piece still in your hands.