← AI PulseAug 27, 2026

Wire · news · Multi-source brief

Vercel AI SDK Google Integration Updates Safety Block Reporting

The Vercel AI SDK's Google integration, version @ai-sdk/google@4.0.55, now surfaces prompt-level Google safety blocks without candidates as content-filter results, including prompt feedback metadata.

By Illumora Editorial

Source · Aug 27, 2026, 3:39 PM · On Illumora · Aug 27, 2026, 3:43 PM

Media from the primary source — shown here so you can stay on Illumora.

Synthesized from multiple allowlisted primaries on the same event. Lanes →

Brief drafted by Illumora’s editorial model from the linked primary source. Ops desk reviews flagged pieces. How we write →

Read the source →Vercel AI SDK Changelog — Release @ai-sdk/google@4.0.55 · vercel/ai
Save

On August 27, the Vercel AI SDK released an update to its Google integration, @ai-sdk/google@4.0.55. This patch change focuses on how Google's safety blocks are reported within the SDK.

Key Points

  • The @ai-sdk/google@4.0.55 release occurred on August 27.
  • This update surfaces prompt-level Google safety blocks.
  • These safety blocks are reported even when no candidates are present.
  • They are presented as content-filter results.
  • The results include prompt feedback metadata.
  • A related update to @ai-sdk/xai@4.0.48 preserves web_search action details in tool results.

Context

According to the Vercel AI SDK changelog, the @ai-sdk/google@4.0.55 update specifically addresses the handling of Google's safety features. This ensures that developers receive explicit feedback when a prompt triggers a safety block, even if no model output is generated. The @ai-sdk/xai@4.0.48 update, also released on August 27, ensures that web_search action details, such as query, sources, and open_page, are preserved in tool results from responses.

Why It Matters

This update provides developers using the Vercel AI SDK with more detailed information regarding content filtering by Google's safety systems. Explicitly surfacing prompt-level safety blocks, along with metadata, can help developers understand why certain prompts might not produce output and refine their input strategies. The preservation of web_search details in the XAI SDK also supports better debugging and understanding of tool-use behavior.

What To Do

  • Developers using @ai-sdk/google should update to version 4.0.55 to access enhanced safety block reporting.
  • Review the prompt feedback metadata provided with content-filter results to understand safety block triggers.
  • For those using @ai-sdk/xai, update to version 4.0.48 to ensure web_search action details are retained in tool results.
  • Test existing applications with the updated SDK versions to observe changes in safety feedback and tool result parsing.