What changed
Anthropic's Python SDK release v0.120.0, published on July 24, 2026, added support for claude-opus-5 and introduced tool addition/removal blocks plus tool_change events in the same release. The update also expanded fallback token handling and added a server-side fallbacks default option.
Anthropic's own model docs for What's new in Claude Opus 5 position Opus 5 as a new top-end Claude model, while the platform docs on fine-grained tool streaming and the stream events API reference show the broader runtime direction: lower-latency tool interaction and richer event streams around agent execution.
Why it matters
The interesting product signal is not just another model ID landing in an SDK. Anthropic is moving Claude workflows toward a more stateful agent runtime where tools can change over time instead of being fixed at request start. That matters for builders shipping longer-running assistants, managed workflows, or approval-based agents, because capability changes, event visibility, and fallback behavior become part of the product surface rather than custom glue code.
Pairing Opus 5 support with live tool-change plumbing also suggests Anthropic wants its highest-end model to sit inside these richer orchestration patterns quickly, not months later after the rest of the platform catches up.
What builders should watch
Builders should watch three things next. First, whether tool_change events become the standard way to observe and govern Claude sessions in production. Second, whether fine-grained streaming plus dynamic tool updates reduces the latency and brittleness of multi-step agent loops. Third, whether Anthropic extends the same runtime pattern consistently across more SDKs and managed agent surfaces, which would make Claude feel less like a static chat API and more like a programmable session layer.