-
Notifications
You must be signed in to change notification settings - Fork 236
[ai] Fix collectUiMessages option by accumulating chunks in a separate step call #784
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
VaguelySerious
merged 15 commits into
main
from
peter/fix-durable-agent-collectUiMessages
Jan 16, 2026
Merged
Changes from all commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
2be861f
[ai] Fix collectUiMessages option by refactoring it to use AI SDK's
VaguelySerious bfc7d12
Fix test warnings
VaguelySerious ddb5b4b
Iterate
VaguelySerious bcc5e4a
Wording
VaguelySerious b7b2249
[core] Fix step attempting to serialize `this` value when it shouldn't
VaguelySerious 0e8fe8c
fix(core): only capture `this` for registered serializable classes
VaguelySerious 869216b
Merge branch 'peter/fix-step-serialization' into peter/fix-durable-ag…
VaguelySerious 1fcd243
DCO Remediation Commit for Peter Wielander <mittgfu@gmail.com>
VaguelySerious 22a1b23
Fix: Tool output UIMessageChunks are lost when multiple tool calls ar…
vercel[bot] 171d1b2
Fix
VaguelySerious 23dd14f
Merge branch 'main' into peter/fix-durable-agent-collectUiMessages
VaguelySerious e9dacd2
Undo
VaguelySerious eaca726
Merge branch 'main' into peter/fix-durable-agent-collectUiMessages
VaguelySerious 425f858
Use generateId to fill in messageIds for accumulated uiMessage objects
VaguelySerious 6d2df7d
Merge branch 'main' into peter/fix-durable-agent-collectUiMessages
VaguelySerious File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| --- | ||
| "@workflow/ai": patch | ||
| --- | ||
|
|
||
| Fix `collectUIMessages` option failing in workflow context |
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Client-side would do
sendStart: falsein that case, no?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the user can decide to do that, but would then have to handle the start themselves, which I think is fine. The ID seems unlikely to cause issues unless message persistence is mixed between client and server side