feat(ai): pass result provider metadata across the stream#13181
Merged
aayush-kapoor merged 4 commits intomainfrom Mar 6, 2026
Merged
feat(ai): pass result provider metadata across the stream#13181aayush-kapoor merged 4 commits intomainfrom
aayush-kapoor merged 4 commits intomainfrom
Conversation
tigent
bot
added
ai/core
felixarntz
reviewed
Mar 6, 2026
|
|
||
| // Bundle size limits in bytes | ||
| const LIMIT = 570 * 1024; | ||
| const LIMIT = 580 * 1024; |
Collaborator
There was a problem hiding this comment.
Curious what's our "policy" on bundle size limits - do we just increase this based on demand? cc @lgrammel who just mentioned bundle size in another call earlier today
felixarntz
approved these changes
Mar 6, 2026
aayush-kapoor
added
the
backport
vercel-ai-sdk bot
pushed a commit
that referenced
this pull request
Mar 6, 2026
## Background faced the issue while implementing #13157 - for multiturn conversation, the item Ids weren't properly being mapped within aisdk and there was a mismatch between what we were sending to the openai api and what was expected. we were attching the same tool call id as the `tool-call` object to the `tool-result` which caused duplicate ID found errors + incorrect ids sent for certain parts ## Summary - since the item_id for tool_search_output is propagated via providerMetadata - we ensure the providerMetadata is preserved through the UI stream. - similar change needed for generate text as well ## Manual Verification will be done in #13157 ## Checklist - [x] Tests have been added / updated (for bug fixes / features) - [ ] Documentation has been added / updated (for bug fixes / features) - [x] A _patch_ changeset for relevant packages has been added (for bug fixes / features - run `pnpm changeset` in the project root) - [x] I have reviewed this pull request (self-review)
vercel-ai-sdk
bot
removed
the
backport
Contributor
|
✅ Backport PR created: #13184 |
vercel-ai-sdk bot
added a commit
that referenced
this pull request
Mar 6, 2026
…13184) This is an automated backport of #13181 to the release-v6.0 branch. FYI @aayush-kapoor Co-authored-by: Aayush Kapoor <83492835+aayush-kapoor@users.noreply.github.com>
Contributor
|
🚀 Published in:
|
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
2 participants
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.
Background
faced the issue while implementing #13157 - for multiturn conversation, the item Ids weren't properly being mapped within aisdk and there was a mismatch between what we were sending to the openai api and what was expected.
we were attching the same tool call id as the
tool-callobject to thetool-resultwhich caused duplicate ID found errors + incorrect ids sent for certain partsSummary
Manual Verification
will be done in #13157
Checklist
pnpm changesetin the project root)