fix: Updated Planner prompt to remove EXCEPTION wording and align with LLM behavior #287
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
UtkarshMishra-Microsoft
requested review from
Avijit-Microsoft,
Fr4nc3,
Prajwal-Microsoft,
Roopan-Microsoft,
Vinay-Microsoft,
aniaroramsft and
marktayl1
as code owners
BoomchainLabs
approved these changes
Jun 26, 2025
UtkarshMishra-Microsoft
requested review from
marktayl1
and removed request for
Avijit-Microsoft,
Prajwal-Microsoft,
Vinay-Microsoft,
aniaroramsft and
marktayl1
marktayl1
approved these changes
Jul 1, 2025
Roopan-Microsoft
approved these changes
Jul 1, 2025
|
🎉 This PR is included in version 2.1.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
blessing-msft
pushed a commit
that referenced
this pull request
Aug 1, 2025
fix: Updated Planner prompt to remove EXCEPTION wording and align with LLM behavior
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Purpose
*This PR modifies the Planner agent prompt template to eliminate the explicit "EXCEPTION" wording from generated steps. The updated prompt instructs the model to:
Continue prioritizing the provided functions to accomplish each step.
Assign steps to the GenericAgent if the task can be handled by a general LLM, without appending 'EXCEPTION' to the action.
Assign steps to the HumanAgent if the task cannot be handled by a general LLM, with clear, professional instructions, without adding 'EXCEPTION' wording.
Retains examples like converting SQL to Python or writing a product strategy to guide model behavior.
Does this introduce a breaking change?
How to Test
What to Check
Verify that the following are valid
Other Information