Repository navigation
feat: add durable pending input to RunState - #4325
Merged
Merged
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
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 adds durable pending input to resumable
RunStateinstances throughRunState.add_input(). Pending input is serialized with the state, admitted only immediately before the next model request after unfinished work completes, evaluated by input guardrails, and persisted exactly once across client-managed Sessions and server-managed conversations.It also checkpoints accepted model responses and tool execution progress so retries do not resend pending input or replay completed side effects. Streaming and non-streaming resume paths share the same behavior, while terminal states and states that cannot reach another model call reject new input before mutation.
This pull request resolves #4323.