Anthropic said on 20 August that computer use, the Skills API and the Files API are generally available on the Claude Platform [E1]. A new browser-use tool sits in the same release, so an agent can read page structure instead of aiming at pixels alone [E1][E3]. The company developer account restated the four items as generally available the same afternoon [E2]. Older beta integrations keep working while teams migrate [E1].
The computer-use change that matters for cost is multi-action turns. The 20260801 toolset lets Claude click, type, press keys and take a screenshot in one model response instead of one action per round trip [E1][E3]. Anthropic says early-access customers saw 20 to 40 percent fewer round trips [E1]. The browser-use docs say the tool is generally available on the Claude API with no beta header [E3]. Skills upload and version through /v1/skills and run in the code-execution sandbox [E1].
Files storage now takes an expiry, a 500-request-per-minute ceiling and a terabyte per organisation [E1][E4]. That is a plumbing change, not a new model. Computer use is also described as eligible for HIPAA-regulated workloads under Anthropic’s BAA [E1]. The commercial BAA help article still listed Computer Use, Skills and Files as beta and not covered when this desk retrieved it [E6]. The blog and the support page do not yet agree [E1][E6].
Asteroid published its own 20 August note on healthcare flows that used the new computer-use tool [E5]. Davide Locatelli wrote that model calls fell 32 to 52 percent, cost per task fell 25 to 32 percent, and completion rose to 100 percent on every workflow tested, from as low as 77 percent [E5]. Those numbers are Asteroid’s, not a third-party audit [E5]. The 32-minutes-to-13 figure that circulated from the Anthropic page is a claims-workflow anecdote on that blog, not the Asteroid table [E1][E5].
Microsoft Foundry already hosts the Skills API and the Files API, according to the same announcement [E1]. The updated computer-use and browser-use tools are described as coming soon to Google Cloud’s Vertex AI, which means they are not live there [E1]. No Meta, Google or OpenAI statement on this specific GA was retrieved inside the freeze [E1][E2].
What the 20 August record actually contains is a GA blog, matching docs for the 20260801 toolsets, an Asteroid customer note, and a BAA page that has not caught up [E1][E3][E5][E6]. Agents that operate software without an API are now a generally available product on one platform. Whether the BAA list and Vertex follow is a later clock [E1][E6].