Anthropic's SDKs add beta toolsets for browser and computer use

Anthropic’s official SDKs now include beta classes that run a browser-use loop and a computer-use loop. The docs say the Python and TypeScript SDKs each have a class for the browser use tool and a class for the computer use tool. You subclass one and write one method per action, such as navigate or left_click. The SDK routes each call, runs the policies you pass, asks your approval callback, and builds each tool_result.

The release notes for 7 October 2026 point at that page. The same day, anthropic-sdk-python v1.12.0 (published 17:57 UTC) and anthropic-sdk-typescript v0.132.0 (published 17:57 UTC) both list “typed computer and browser toolset tool calls” among the features.

The classes are beta, and the names are fixed

The docs say “the browser toolset class is in beta” and “the computer toolset class is in beta.” The browser class is BetaAbstractBrowserToolset20260801. The computer class is BetaAbstractComputerToolset20260801. Each one runs with the tool runner, or in a loop you write yourself.

The SDK does not include a browser, a desktop, a ready-made driver, or a URL policy. A minimal example in claude-quickstarts drives Chromium through the Chrome DevTools Protocol. The docs say that example “isn’t production code.”

The docs’ quick start subclasses the browser class. This excerpt is from that sample, shortened to the navigate method. backend is your own wrapper, as the docs describe it:

class MyBrowser(BetaAbstractBrowserToolset20260801):
    def navigate(
        self, context: BetaToolsetCallContext, input: BetaBrowserNavigateInput
    ) -> BetaBrowserNavigateResult:
        page = self.backend.goto(input.url, input.tab_id)
        return BetaBrowserNavigateResult(
            url=page.url, status=page.status, title=page.title
        )

Other methods in the same sample are screenshot, left_click, and _browser_state (TypeScript: browserState). The state method returns a BetaBrowserState with a tab list. The docs say every driver needs that report.

What you still have to supply

The SDK runs the loop. Three checks stay in your code.

A URL policy is a function you pass, url_policy. The sample raises ToolError when a URL is not on an allowed host. The docs call that sample “an example, not a production policy.”

A file policy covers uploads and downloads. The docs say the SDK can also change the tool input before the call, and that it does not check the changed input again.

An approval callback is confirm, built with make_confirm() in Python and makeConfirm() in TypeScript. The docs say a default make_confirm() call returns a callable with no approvals. You call it once per toolset, and each user gets their own toolset. An approval covers the page as the last state report showed it. The page can change before the call runs. Purchases, sent messages, and accepted terms go through ordinary members such as left_click and type, so the docs say to decide which of those need a confirm step.

Partners, as the docs list them

The docs name four companies that publish their own integrations: Browser Use, Browserbase (its Stagehand docs), Daytona, and E2B. Those are links out to their docs and examples. Anthropic’s page does not say those products are required.

How this differs from Copilot’s computer use

GitHub Copilot’s computer use preview is a product surface: Copilot CLI and the Copilot app on macOS and Windows can click and type in local desktop apps. Anthropic’s toolsets are library classes. You bring the browser or the desktop automation, and you bring the policy. Copilot’s preview is GitHub driving apps on the machine. This SDK is a loop you host, still labeled beta, with the safety checks left in the subclass.