fix: isolate nested agent-tool resume cache by RunState scope#2501
Merged
fix: isolate nested agent-tool resume cache by RunState scope#2501
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 fixes cross-state interference when nested agent-tool interruption state is restored from JSON multiple times in the same process. The agent-tool pending result cache is now scoped per restored
RunState, and the scope is propagated through resume execution paths andToolContextcreation so cache lookup/consume/drop always stays within the correct run-state boundary. It also updatesRunStatenested-state serialization/deserialization to use the scoped cache consistently, and extends regression coverage to verify two independently restored states from the same payload can both be approved and resumed successfully.