Repository navigation
Accept built-in tool parts in message builders - #367
Merged
Merged
Conversation
The message builders accept Part values, but their runtime type check omitted BuiltinToolCallPart and BuiltinToolReturnPart. This made them reject stored provider-tool turns even though both types belong to Part. Include the existing types in the check and cover a built-in call and return followed by text. No new part type or parameter is added.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
msullivan
approved these changes
Nov 18, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We were rejecting built-in tool calls and returns in the message builders even though they're already valid parts.
ai.assistant_message(*stored.parts)now works for turns with a provider tool like web search.