Anthropic’s Python SDK 1.12.0 adds support for Claude Haiku 5.5 and typed computer and browser tool calls, alongside new controls and capabilities for developers building with its API. The release also updates how models, workspaces and Managed Agents can be configured, making this a substantial toolkit update rather than a one-line version bump.
Anthropic Watch analysis
What happened
Published on 7 October, version 1.12.0 adds Claude Haiku 5.5 to the SDK and introduces typed tool calls for computer and browser use. The release notes also list support for web search and code execution in model capabilities, plus a urlsources option for the Managed Agents webfetch tool.
Other additions include a way to disable thinking types in model capabilities, a displayname field for RBAC roles as name is deprecated, and lifecycle-stage fields and filtering for the /v1/models endpoint. Developers can also request default workspaces when listing them, and model objects now include a line field. The release notes say the API tool limit is 256.
Our top picks
- Claude Haiku 5.5 support
The SDK can now identify and work with Anthropic’s newly listed model. - Typed computer and browser tool calls
Tool calls get more explicit structures for integrations that use computer or browser tools. - Web search and code execution in model capabilities
Applications can discover these capabilities through model information. - Managed Agents can specify URL sources for web fetch
The new urlsources configuration gives developers another way to set up fetching. - Lifecycle stages and filtering for models
Developers can use the new /v1/models fields and filter to inspect model stages. - Clearer workspace and role administration
Workspace listings gain an includedefault parameter, while RBAC roles gain displayname as name is deprecated.
Why it matters
The useful change here is breadth: the SDK adds model support and gives developers more structured ways to work with tools, model capabilities and administration. That can reduce the amount of glue code needed to discover what a model can do and configure the surrounding application. It is also a reminder that API tooling increasingly needs to describe not just a model, but the tools and operational controls around it.
The release notes establish what the SDK now supports; they do not show how well these features perform in a deployed application. Teams should check the migration details, especially the RBAC field deprecation, before updating code that depends on name.
Our read
A worthwhile SDK release, with several practical additions rather than a shiny feature hiding a quiet breaking change. The tool and capability updates are the standouts; the administrative fields matter most to teams maintaining larger integrations. Check the deprecation and model-specific support before upgrading, then test the features your application actually uses.
What to watch
- Whether Anthropic adds further models and typed tool support to the SDK.
- How developers handle the transition from RBAC name to displayname.
- Whether model capability information proves reliable and useful across integrations.
Discussion spark: Should API SDKs expose model capabilities and tool support as structured data, even if developers still need to verify what works in practice?
Sources and evidence
- v1.12.0 (7 October 2026, 17:57 UTC)
Anthropic Watch is independently operated by WittyWires. It is not affiliated with, endorsed by, or operated by Anthropic.