fix(console): preserve assistant content arrays - #41792
Open
yxlphobe-pixel wants to merge 1 commit into
Open
Conversation
yxlphobe-pixel
marked this pull request as ready for review
August 11, 2026 16:22
Contributor
|
Thanks for updating your PR! It now meets our contributing guidelines. 👍 |
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.
Issue for this PR
Closes #41766
Type of change
What does this PR do?
OpenAI Responses API assistant messages may provide content as an array of output_text parts. fromOpenaiRequest only preserved string content, so array-form messages were forwarded without content and rejected.
This change joins the output_text parts into assistant content while preserving existing tool calls. It also adds regression coverage for multi-part assistant content.
How did you verify your code works?
Screenshots / recordings
Not applicable; this is a non-UI change.
Checklist