🤖 fix: stabilize streaming barrier token count in stories #744
Conversation
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
The interval callbacks that maintain streaming state were adding 1 token every 2 seconds, causing flaky token counts (72 vs 73) depending on test timing. Setting tokens: 0 keeps streaming state active without affecting the displayed count. _Generated with mux_
ammario
approved these changes
Nov 25, 2025
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.
The interval callbacks that maintain streaming state were adding 1 token every 2 seconds, causing flaky token counts (72 vs 73) depending on test timing. Setting
tokens: 0keeps streaming state active without affecting the displayed count.Generated with
mux