Claude's Computer Use Tool Is Generally Available, and a New Browser Tool Shipped Alongside It

On August 19, Anthropic took the computer use tool out of beta on the Claude API. It now ships as a stable toolset called computer_toolset_20260801, no beta header required, and it arrived the same day as a second, related tool built for a narrower job: driving a browser instead of a whole desktop. The Skills API and the Files API left beta on the same date. Four pieces of platform infrastructure, one release, and the useful question for anyone building on Claude is which of these actually changes what you can ship, versus which one just drops a header you were already sending.

The computer use tool drops its beta header, and gains batch actions

Computer use is the tool that lets Claude look at a screenshot and act on it: move the mouse, click, type, take another screenshot, repeat. It has been available in beta for well over a year, first as computer_20241022, then computer_20250124, then computer_20251124. The version that went generally available, computer_toolset_20260801, is a real step past those earlier versions, not just a rename.

Three changes stand out. First, batch actions: Claude can now issue several actions in a single turn instead of one screenshot-click-screenshot cycle per turn, which cuts the number of round trips a long task needs. Second, zoom is enabled by default, letting the model inspect a region of the screen more closely before deciding what to click, which matters on dense interfaces where a wrong click is expensive to recover from. Third, per-member configuration through a configs parameter, so a team running computer use across multiple accounts or environments can set behavior per member rather than per request.

Earlier beta versions of the tool still work, but Anthropic's own migration guide flags that upgrading changes the request shape and how tool results get handled, so this is not a drop-in swap. If you built something on computer_20251124, budget time to actually read the migration notes before flipping the toolset name in your code.

Browser use is not computer use with a smaller scope, it is a different tool

The part of this release that is easy to skim past is the second toolset: browser_toolset_20260801, a client toolset for driving a browser your own application hosts. It is not a scaled-down computer use, it works differently. Instead of taking a screenshot and clicking coordinates on it, browser use reads the page itself, its accessibility tree, elements, forms, and open tabs, and gives Claude element references it can act on directly. On top of that base it adds form input, tab management, download reporting, and opt-in file upload, layered over the older screenshot-and-click approach rather than replacing it outright.

That distinction is worth sitting with if you are choosing between the two. Computer use is the right tool when the target is a real desktop app with no API, the same category of problem that free, open-source MCP servers like Nuphus MCP were built to solve outside Anthropic's own platform. Browser use is the right tool when the target is a web page inside a browser your application already controls, and reading the page's actual structure will be more reliable than clicking blind on pixel coordinates. Both toolsets are available on Claude Fable 5, Claude Mythos 5, Claude Opus 5, Claude Sonnet 5, and Claude Opus 4.8.

Files API and Skills API leave beta the same day

The Files API, which lets you upload a file once and reference it across Messages API requests instead of re-sending it every time, is now generally available. Requests to /v1/files no longer need the files-api-2025-04-14 beta header. The GA response format adds file expiration (set expires_in_seconds on upload, and the file object reports back expires_at), plus page and next_page pagination and an ids[] filter when listing files. Requests that still send the old beta header keep working in the previous format, so nothing breaks if you have not migrated yet.

Agent Skills and the Skills API (/v1/skills) also went generally available on August 19. The skills-2025-10-02 beta header is no longer required, including for Messages API requests that load a skill through the container parameter. This is the same Skills API that lets you package a reusable capability, packaging logic, a house style, a checklist, once, and load it into any session that needs it, rather than re-pasting instructions into every system prompt.

What generally available actually buys you

GA is a status change with a real practical consequence: it is the point where a team stops treating an integration as something that could still change shape under them. A beta header is a signal, implicit or explicit, that the request format, the response schema, or the tool's behavior might shift before it stabilizes. Building a production workflow on top of a beta feature means accepting that risk, or building an abstraction layer to absorb it. Once something is GA, that risk mostly goes away, and the header requirement disappearing is really just the visible symptom of the underlying commitment.

For a team that has been holding off on wiring computer use, the Skills API, or the Files API into a real workflow because it was still in beta, August 19 is the actual green light, not a formality. The concrete move worth making this week is a small one: pick a single workflow that currently has no API, an internal tool, a legacy dashboard, a vendor app that only ships a GUI, and test computer use or browser use against it before building anything larger around the assumption that it will work. Anthropic's own migration guide for computer use is the first thing to read if you already have something running on an earlier beta version, since the request and result shapes changed enough that a straight toolset rename will not work.

This was one release in a busier August for the Claude Platform: Managed Agents got budget caps and self-hosted sandbox memory the same week, and the Console's session viewer was redesigned days earlier. Individually, none of these is a headline. Together, they are what a platform maturing past its own beta phase looks like from the outside.