Nightly OSS: Responses API: undocumented reasoning+message pairing constraint breaks multi-turn conversations#3187
Conversation
…ssage pairing constraint breaks multi-turn conversations Nightly Codex produced a focused contribution for openai#3009. Constraint: Automated nightly run; keep changes small and reviewable. Confidence: medium Scope-risk: narrow Tested: See uploaded nightly artifacts and workflow logs. Not-tested: Maintainer CI beyond this workflow.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 35e5878fef
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| @@ -0,0 +1,5 @@ | |||
| Wrote [NIGHTLY_REPORT.md](/home/runner/work/oss-nightly-control/oss-nightly-control/target/NIGHTLY_REPORT.md) and did not change repository code. | |||
There was a problem hiding this comment.
This commit adds run-specific bookkeeping artifacts (.codex-nightly-retry-1.md, NIGHTLY_CODEX_FINAL_ATTEMPT_1.md, and NIGHTLY_CODEX_FINAL_ATTEMPT_2.md) that are not part of the SDK or user-facing docs and contain ephemeral CI details (including absolute runner paths and point-in-time issue status). Keeping these tracked will create ongoing maintenance noise and confuse contributors about project documentation, so they should be excluded from the change.
Useful? React with 👍 / 👎.
1 participant
Automated nightly Codex contribution for #3009.
Verification:
This PR is generated by xodn348/oss-nightly-control and is opened ready for maintainer review when the local nightly verification step succeeds.