fix: encode structured programmatic tool errors as JSON#3932
Merged
Conversation
seratch
enabled auto-merge (squash)
July 24, 2026 03:08
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
1 participant
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 pull request fixes HTTP 400 errors when programmatic function tools with structured output schemas are rejected, blocked by guardrails, or time out.
SDK-generated errors are now encoded as JSON objects in provider-facing tool outputs while preserving existing public output values and direct function-call behavior. Approval rejections also retain valid outputs across streaming, serialized state, and resumed execution.