Anthropic's Python SDK 1.12.0 and TypeScript SDK 0.132.0 add computer_toolset_20260801 and browser_toolset_20260801: a single tools[] entry declares a whole family of desktop or browser actions, the SDK tool_runner executes them in order and stops at the first failure, and url_policy, file_policy and confirm hooks run before each call. Developers no longer hand-write the loop that maps clicks and keystrokes to commands; they subclass an abstract toolset and plug in their own VNC, DevTools or hosted-browser backend.

Key Takeaways

  • ✓Versions: Python anthropic 1.12.0 and TypeScript SDK 0.132.0 (2026-10-07) add typed computer and browser toolset calls
  • ✓The computer toolset covers 17 actions (screenshot, left_click, type, scroll, zoom...); unimplemented ones are sent as enabled: false (docs)
  • ✓The browser toolset adds navigate, tabs, read_page, read_network, form_input, file_upload and more, with url_policy checked on every navigate (docs)
  • ✓Official 7-step safety checklist: URL policy, request interception, container egress rules, file policy, confirm gates, per-session isolation, treat page content as untrusted
  • ✓ClaudeDevs announcement drew 3,500+ likes and 248K views; no new benchmark numbers were published
Claude's Python and TypeScript SDKs now ship built-in computer-use and browser-use toolsets: the SDK runs the agent loop, you only write the driver
🖼️Official Media
Click to view high-res
🧭

Turn your technical choice into a development budget

Compare 40 dev plans & simulate token costs vs $20/mo subscriptions

🔬

In-Depth Technical Analysis

Claude's computer-use tool only tells you what the model wants to click or type; until now every team wrote its own loop to map those actions to commands. Python SDK 1.12.0 and TypeScript SDK 0.132.0 (Oct 7, 2026) add toolsets: computer_toolset_20260801 and browser_toolset_20260801 are single tools[] entries that declare a family of member actions. You subclass an abstract toolset (for example BetaAbstractComputerToolset20260801) and implement only what your backend supports, whether VNC, xdotool, a DevTools client or a hosted browser; unimplemented members are sent as enabled: false. The tool_runner executes a turn's actions in order and stops at the first failure or refusal. The browser toolset runs your url_policy, file_policy and confirm hooks before each call, and a reference Chrome DevTools driver lives in claude-quickstarts. Anthropic published no new benchmarks for this SDK change. Before deploying, follow the seven-point safety checklist in browser-toolset.md: URL policy, request interception in the driver, container egress rules, a file policy or no file_upload, confirm gates for consequential actions, per-session isolation, and treating all page content as untrusted.

Action HubReady to adopt this in production?

Benchmark side-by-side against alternatives, or calculate monthly token cost vs subscription break-even.