fix: #2797 accept raw image_url content parts on chat completions input#2799
Merged
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
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 #2797 a Chat Completions input compatibility gap in the Python Agents SDK. When callers selected the
chat_completionsbackend and passed raw Chat Completions-style content parts such as{"type": "text"}and{"type": "image_url"}, the SDK rejected the request before it reached the model even though the backend request shape itself was valid.The change keeps
input_imageas the canonical SDK input shape, but adds alias handling in the Chat Completions conversion path so rawtextandimage_urlparts are accepted and normalized consistently. It also aligns the official-OpenAI preflight validation path with the converter, which removes the backend-specific preflight failure for image inputs.