Vercel has issued several updates to its AI SDK, specifically for the @ai-sdk/xai and @ai-sdk/google packages. On August 27, @ai-sdk/xai received updates to versions 2.0.91, 3.0.129, and 4.0.48. Concurrently, @ai-sdk/google was updated to version 4.0.55.
Key Points
- The @ai-sdk/xai package versions 2.0.91, 3.0.129, and 4.0.48 include a fix to preserve
web_searchactions. - This preservation applies to
query,sources, andopen_pagewithinweb_searchactions in responses tool results. - The @ai-sdk/xai@2.0.91 release occurred on August 27 at 18:50.
- The @ai-sdk/xai@3.0.129 release occurred on August 27 at 18:40.
- The @ai-sdk/xai@4.0.48 release occurred on August 27 at 15:36.
- The @ai-sdk/google@4.0.55 package update surfaces prompt-level Google safety blocks.
- These safety blocks are presented as content-filter results with prompt feedback metadata when no candidates are available.
- The @ai-sdk/google@4.0.55 release also occurred on August 27 at 15:36.
Context
According to the Vercel AI SDK changelog, the updates for @ai-sdk/xai address an issue where web_search actions were not fully preserved in tool results. The @ai-sdk/google update, as noted by Vercel, enhances how Google's safety features are communicated to developers, specifically when content is blocked at the prompt level.
Why It Matters
These updates provide developers using the Vercel AI SDK with more robust handling of web search tool results and clearer feedback on content filtering from Google's safety mechanisms. This can improve the reliability of applications that integrate web search capabilities and enhance the debugging process for content safety issues.
What To Do
- Developers using @ai-sdk/xai should update to versions 2.0.91, 3.0.129, or 4.0.48 to ensure
web_searchactions are preserved. - Review the changelog for @ai-sdk/google@4.0.55 to understand how prompt-level safety blocks are now surfaced.
- Test applications integrating Google models with the updated @ai-sdk/google package to observe the new content-filter results and metadata.
- Note the specific timestamps of the releases on August 27 for version control and deployment planning.
