Repository navigation
fix: clarify the default HITL modification feedback so the LLM uses the modified tool result - #13384
Merged
Merged
Conversation
…he modified tool result
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
sjrl
marked this pull request as ready for review
October 22, 2026 06:24
Contributor
Coverage reportClick to see where and how coverage changed
This report was generated by python-coverage-comment-action |
||||||||||||||||||||||||
anakin87
approved these changes
Oct 22, 2026
This branch was successfully deployed
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.
Related Issues
Proposed Changes:
modify_templateofBlockingConfirmationStrategyto tell the LLM the user wants the modified result used and not to call the tool again with the original arguments.How did you test it?
Unit tests, plus the live script below on main vs this branch with
gpt-5-mini: 2/5 runs repeated the tool call on main, 0/5 on this branch.Notes for the reviewer
With the old wording the model often treated the modified result as a tool failure ("I tried to fetch Berlin, but the weather tool keeps returning Munich") and called the tool again.
Reproduction script (needs OPENAI_API_KEY)
Checklist