stagehand-python@4.2.2a0.dev1605: fix : add new webmcp launch flag ( 3198)
Browserbase Stagehand releases published stagehand-python@4.2.2a0.dev1605: fix : add new webmcp launch flag ( 3198). why chromium versions newer than 157 require enable-features=WebMCP what changed added the new chrome flag to defaults Summary by cubic Adds the WebMCP flag to the default local Chrome launch flags across all SDKs so WebMCP works on Chromium…
Why this signal matters
Browserbase Stagehand releases published stagehand-python@4.2.2a0.dev1605: fix : add new webmcp launch flag ( 3198). 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 chromium versions newer than 157 require enable-features=WebMCP what changed added the new chrome flag to defaults Summary by cubic Adds the WebMCP flag to the default local Chrome launch flags across all SDKs so WebMCP works on Chromium versions newer than 157. Updates the WebMCP flag from --enable-features=WebMCPTesting,DevToolsWebMCPSupport to --enable-features=WebMCP,WebMCPTesting,DevToolsWebMCPSupport in TypeScript, Python, and Go SDKs. Updates docs and test fixtures to match the new flag. Written for commit c75f0d9 . Summary will update on new commits.
Actionable summary
Treat stagehand-python@4.2.2a0.dev1605: fix : add new webmcp launch flag ( 3198) as an official release signal. Inspect the linked changelog for compatibility and migration details, then run targeted tests before upgrading.
- Agent usefulness
- 72/100
- Confidence
- 96%
- Canonical data
- JSON + Markdown
What builders should check
- 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.