fix: #2426 persist streamed run-again tool items to session#2433
Merged
fix: #2426 persist streamed run-again tool items to session#2433
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This pull request resolves #2426: a streamed session persistence gap where
Runner.run_streameddid not save tool call items when the turn ended withNextStepRunAgain, causing follow-up turns to miss prior tool execution context (for example, repeated tool calls in multi-turn flows, including handoff scenarios).The streamed loop now persists turn session items in the run-again path, aligning behavior with non-streaming
Runner.run. A regression test that verifies bothfunction_callandfunction_call_outputare stored in session history for streamed tool-call turns is also added.