Add validation for agent selection and dependency references in planner#207
Open
jack-pfeifer wants to merge 1 commit intoIBM:mainfrom
Open
Add validation for agent selection and dependency references in planner#207jack-pfeifer wants to merge 1 commit intoIBM:mainfrom
jack-pfeifer wants to merge 1 commit intoIBM:mainfrom
Conversation
jack-pfeifer
force-pushed
the
planning-validation
branch
3 times, most recently
from
6d901c0 to
180a424
Compare
Signed-off-by: Jack Pfeifer <jpfeifer@albany.edu>
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
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.
This change improves robustness in the planning workflow by adding validation in two areas:
Agent selection
After a plan is generated, each step is checked to ensure the referenced agent exists in the available agent list. If an unknown agent is returned by the planner, the system now raises a clear error instead of continuing with an invalid step.
Dependency validation
Step dependencies (#S1, #S2, etc.) are now validated during plan parsing to ensure they reference valid earlier steps. Invalid or forward references now raise an error before execution.
These checks help prevent malformed LLM-generated plans from progressing into the execution stage and make debugging planning issues easier as more agents and planning logic are added.