feat(chat): add thread.stream() method for passing streaming options#346
Open
feat(chat): add thread.stream() method for passing streaming options#346
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Collaborator
|
Wow, really? |
cramforce
requested changes
Apr 7, 2026
Collaborator
cramforce
left a comment
cramforce
left a comment
There was a problem hiding this comment.
Ah, now I get it. Not sure this should merge. We need to think about how to make this work across adapters.
We have the PostableObject abstraction for doing custom things
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.
summary
thread.stream()was documented but didn't exist - users had to bypass the Thread abstraction and callthread.adapter.stream()directly to pass options liketaskDisplayModeorstopBlocksadds
thread.stream(stream, options)which acceptstaskDisplayMode,stopBlocks, andupdateIntervalMswhile auto-populating internal fields (recipientUserId,recipientTeamId) from message context