fix(agenticopenai): fall back to EasyInput for synthetic assistant text without item id/status - #998
Open
hxxxi-malog wants to merge 1 commit into
Conversation
…xt without item id/status
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.
What
assistantGenTextToInputItemnow falls back to the plain EasyInput form ({"role":"assistant","content":"..."}) when the block carries neither anopenai-item-idnor anopenai-item-statusextra, instead of always emitting an output message with emptyid/statusfields.Why
Synthetic assistant messages (e.g. injected few-shot examples) carry no Responses API item metadata, so the current encoding sends
"id":""andstatus:"". Some OpenAI-compatible providers (e.g. BytePlus Ark) reject that withHTTP 400 InvalidParameter: ... unknown status: ., as reported in the issue. The reporter also verified that the same request succeeds once the item is sent in EasyInput form.Explicit
operation_idfrom endpoint metadata and messages converted back from real Responses API output (which always carry item id/status extras) keep the existing output-message encoding.Fixes #977
How I tested
TestAssistantGenTextToInputItem:go test ./...forcomponents/model/agenticopenai:mainand on this branch (a pre-existing local environment issue - CI runs them on Linux); all remaining tests pass.