fix(codex): make the reasoning summary level configurable#33222

open1
main
GitHub fork: codex-reasoning-summary-setting
opened1d agobyRronharel02
View on GitHubTwo-way sync enabledPR last imported 15h ago

Problem

T3 asks Codex for detailed reasoning summaries on every turn. Some OpenAI-compatible API gateways accept only auto and reject the request, so no turn can run through them in T3.

Change

Codex instances get a reasoning summary setting under the runtime section (detailed, auto, concise or none). The adapter sends the selected value as the turn's summary.

For managed ChatGPT instances, the runtime section showed only its own read-only path fields, so the new setting would have been missing there. It now shows below them. Binary path, CODEX_HOME path, shadow home path and launch arguments stay hidden in managed mode, as before.

T3 already requests reasoning summaries on every turn, and the setting only picks their level. It defaults to detailed, so existing setups behave the same unless someone changes it.

Verification

  • vp test run apps/server/src/orchestration-v2/Adapters/CodexAdapterV2.test.ts: the existing turn-params table checks that each value is sent and that a missing setting sends detailed.
  • vp run check:changed: format, lint, knip, typecheck and the affected tests pass.
  • Manual, against an OpenAI-compatible gateway through a Codex instance using an existing CLI: detailed is rejected, auto works.

UI Change

On main:

With the change:

Managed ChatGPT instance (not signed in; layout only):

Written with GPT-6.1 Sol in Codex and reviewed with Claude Opus 5.5 in Claude Code, both running in T3 Code.

Checks

1 failing ยท 22 successful ยท 15 skipped
Some checks failed

Failing1

0b79831

Added 1 commit

  • fix(codex): make the reasoning summary level configurable0b79831

Thanks, @ronharel02, for the fix and gateway verification! #20410, originally by @only21mil, addresses the same rejection by using auto by default and honoring Codex summary preferences, with broader regression coverage. Closing this as a duplicate; please share any gateway-specific findings there.

Synced from GitHub
Codex Review Summary: โœ… Completed

This comment shows the latest Codex review activity on this pull request.

ReviewStatusCommitReview trigger
๐Ÿ“ Code Reviewโœ… Completed 2026-11-09T07:44:46.669638Z0b79831PR opened
โ„น๏ธ 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" or "@codex security review".

Codex reacts with ๐Ÿ‘€ while any review is running, comments if it has suggestions, and reacts with ๐Ÿ‘ once all reviews finish with no findings.

Reopening this as the live fix for the same gateway rejection: its head is current, while #20410 is over two weeks old and main has changed its files. Thanks, @ronharel02, for the fix and gateway verification! Note that honoring existing Codex configuration remains a separate consideration.