Nothing open on GitHub. Fix merged in #15690 on 25 Apr 2026. Check it covers your case.
The short answer
0open issues
0open PRs
3items grouped
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #15690. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #15690. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address an issue where assistant message content incorrectly used 'input_text' instead of 'output_text' in the Codex Responses API, causing 400 errors. A fix was proposed and a corresponding pull request was submitted.
Open issues0
Open PRs0
Fixes on record
-
#15690 fix: use output_text for assistant content in Codex Responses API
files:
agent/codex_responses_adapter.py,tests/run_agent/test_provider_parity.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#15691 fix(codex-responses): use output_text for assistant message content (#15687) · merged via another change →
#15690
Closed issues · 1
- Closed#15687Codex Responses API 400: input_text invalid on assistant message content
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #15690
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 25 Apr 2026. This confirmation is old and may be out of date (a revert or reopen would not have invalidated it here); re-verify.