feat(agents): support persistense feature for planner agents#1786
Open
antoniibelyshev wants to merge 7 commits intodevelopfrom
Open
feat(agents): support persistense feature for planner agents#1786antoniibelyshev wants to merge 7 commits intodevelopfrom
antoniibelyshev wants to merge 7 commits intodevelopfrom
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 PR extends the persistense feature to be available for the planner agents.
Example:
note:
data class AgentCheckpointDatawas updated: fieldsnodePath,lastInput, andlastOutputwere removed (they are now stored in theproperties: JSONObjectwhich was there before). Since the intended use-case for this class from the user perspective is to only serialize-deserialize it, the users should not be affected by that, therefore I do not mark this as a braking change.closes KG-673