fix(sdk): drop incomplete streamed tool calls on flush - #39094
Open
nikkstchv wants to merge 1 commit into
Open
Conversation
Bump @ai-sdk/openai-compatible to 2.0.62 and patch flush so dangling tool_call indexes without function.name do not fail the whole stream. Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
|
Thanks for updating your PR! It now meets our contributing guidelines. 👍 |
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.
Issue for this PR
Closes #26412
Type of change
What does this PR do?
OpenAI-compatible providers can stream tool calls where one index gets an
idbut never receivesfunction.name.@ai-sdk/openai-compatible2.0.62 buffers name across chunks, but still throws inflush()when a pending tool call never gets a name, failing the whole agent turn.This bumps the SDK to 2.0.62 and patches flush to clear incomplete pending tool calls instead of throwing. Valid tool calls in the same stream continue to execute.
Related: #24137 (mid-stream name buffering landed in 2.0.58+; this covers the remaining flush case).
How did you verify your code works?
Reproduced with a custom Vesna OpenAI-compatible provider (
vesna_code/VesnaCode): agent tool calls previously failed withExpected 'function.name' to be a stringwhen the provider emitted a dangling tool-call index. After the bump + patch, the same session completes tool calls without that error.Screenshots / recordings
Not applicable (SDK/runtime change, no UI).
Checklist