fix: prevent empty WebSearch.action when maxToolCalls is exceeded (#600) #627
+27
−1
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
… exceeding maxToolCalls (openai#600) Ensure proper fallback and non-empty response handling when tool limit is exceeded. This prevents returning empty responses during DeepResearch multi-call sequences.
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.
DeepResearch could return an empty ResponseFunctionWebSearch.action
after maxToolCalls was reached, causing downstream handlers to see an
empty action and produce no results.
This change adds a safe fallback path once the tool-call budget is
exhausted and guarantees a non-empty, well-formed action. It also
documents the invariant and adds a regression test that simulates
exceeding maxToolCalls.
Why:
Prevents silent empty responses during multi-call DeepResearch flows
and makes behavior deterministic at the tool-call boundary.
Fixes: #600