stagehand-python@4.4.0a0.dev1662: fix : bump ai-sdk for opus 5.5 support ( 3340)
Browserbase Stagehand releases published stagehand-python@4.4.0a0.dev1662: fix : bump ai-sdk for opus 5.5 support ( 3340). why Fixes 3337 The extension used @ai-sdk/anthropic 4.0.8 which predates opus 5.5. For structured output, it sent a forced tool call ( tool choice: { type: "any" } ), which opus 5.5 rejected. Because of this, act , observe and extract…
原始内容为英文;当前页面提供中文导航与来源说明,具体事实请以原文为准。
为什么值得关注
Browserbase Stagehand releases published stagehand-python@4.4.0a0.dev1662: fix : bump ai-sdk for opus 5.5 support ( 3340). This automated release-watch entry was generated from the project's official GitHub release feed and is kept separate from human-reviewed editorial analysis. Release notes: why Fixes 3337 The extension used @ai-sdk/anthropic 4.0.8 which predates opus 5.5. For structured output, it sent a forced tool call ( tool choice: { type: "any" } ), which opus 5.5 rejected. Because of this, act , observe and extract were also failing. what changed Bump @ai-sdk/anthropic to ^4.0.90. This version uses native structured output for Opus 5.5. Bump ai to ^7.0.155. It must use the same @ai-sdk/provider version as the new Anthropic package. Pin @ai-sdk/anthropic to 4.0.26 in mastra-sdk to match the @ai-sdk/provider version that @mastra/core uses test plan Added a gateway test fixture to catch when tool choice is required but the reply has no tool call Summary by cubic Bumps @ai-sdk/anthropic and ai in the extension so it works with Claude Opus 5.5, fixing act , observe , and extract failures for that model. Fixes 3337 , where forced tool calls ( tool choice: { type: "any" } )…
可执行摘要
Treat stagehand-python@4.4.0a0.dev1662: fix : bump ai-sdk for opus 5.5 support ( 3340) as an official release signal. Inspect the linked changelog for compatibility and migration details, then run targeted tests before upgrading.
- Agent 实用度
- 77/100
- 可信度
- 96%
- 机器格式
- JSON + Markdown
开发者应核对什么
- Review the official Browserbase Stagehand releases release notes before upgrading.
- Check compatibility, migration, and security notes against your current agent stack.
- Run focused regression tests before production rollout.