FrameworksOfficial

AI SDK preserves repaired tool identity across signed approval resume

AI SDK 7.0.147, released October 20, keeps the repaired tool name in streamed UI messages so a signed approval does not become invalid when execution resumes.

Why it matters

Approval in a generative interface must bind to the tool that will actually run. Divergent display, message-conversion and signature identities can make an already approved action impossible to resume reliably.

A closer look

The official commit says that when repairToolCall corrected a tool name during streaming, processUIMessageStream updated state and input but retained the old static part type. convertToModelMessages then reconstructed the stale name and signature verification failed. The patch synchronizes the static part type to the completed tool name before approval-requested state and adds regression coverage.

Who this is for

Teams using AI SDK streaming tools, repairToolCall and approval resume

Original sources

Revisions & corrections (1)

— Verified official release and fix commit; distinct October 20 framework event with bilingual analysis and explicit limits.

Related events

Frameworks

assistant-ui's October 28 release tightens prompt review, tool-result ownership and configuration writes

assistant-ui released a coordinated package set on October 28. Generative Frame 0.0.9 fills the composer with widget and MCP App prompts for review before sending; assistant-stream 0.3.55 fixes stale model content surviving a later tool response and pending results moving when tool-call IDs are reused; the CLI also narrows configuration paths and plan-revision boundaries.

Frameworks

AI SDK 7.0.155 removes runtime checks already guaranteed by static types

Released October 27, AI SDK 7.0.155 stops revalidating message history against the ModelMessage schema in text and object generation and removes several shape checks covered by TypeScript, reducing a linear cost in long conversations and multi-step runs.