fix(codex): always include output_tokens_details.reasoning_tokens in …#3514
Merged
farion1231 merged 2 commits intoJun 3, 2026
Merged
Conversation
…chat→responses transform Codex CLI strictly requires reasoning_tokens in the response.completed usage object. Custom providers using /chat/completions often omit completion_tokens_details, causing repeated parse failures and retries.
Owner
|
@codex review |
![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: 85d795c109
ℹ️ 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".
Contributor
Author
|
补充问题现象及修复后正常运行的截图 修复后不在反复重试，正常运行： |
AnXiYiZhi
pushed a commit
to AnXiYiZhi/DevCLaw-old
that referenced
this pull request
Jun 9, 2026
farion1231#3514) * fix(codex): always include output_tokens_details.reasoning_tokens in chat→responses transform Codex CLI strictly requires reasoning_tokens in the response.completed usage object. Custom providers using /chat/completions often omit completion_tokens_details, causing repeated parse failures and retries. * fix(codex): guard non-object completion_tokens_details before insertion --------- Co-authored-by: yeeyzy <yeeyzy@[email protected]>
gfunc
pushed a commit
to gfunc/cc-switch
that referenced
this pull request
Jun 19, 2026
farion1231#3514) * fix(codex): always include output_tokens_details.reasoning_tokens in chat→responses transform Codex CLI strictly requires reasoning_tokens in the response.completed usage object. Custom providers using /chat/completions often omit completion_tokens_details, causing repeated parse failures and retries. * fix(codex): guard non-object completion_tokens_details before insertion --------- Co-authored-by: yeeyzy <yeeyzy@[email protected]>
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
2 participants
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.
fix(codex): always include output_tokens_details.reasoning_tokens in chat→responses transform
Codex CLI/Codex Desktop strictly requires reasoning_tokens in the response.completed usage object. Custom providers using /chat/completions often omit completion_tokens_details, causing repeated parse failures and retries.
Summary / 概述
Codex CLI 在解析 responses API 的 usage 对象时，严格要求存在
output_tokens_details.reasoning_tokens字段。当使用自定义 provider（走 /chat/completions 格式）时，上游往往不返回completion_tokens_details，导致转换后的 usage 缺少该字段，Codex 解析失败并反复重试。本 PR 在 chat→responses 的 usage 转换逻辑中确保
output_tokens_details.reasoning_tokens始终存在：output_tokens_details: { reasoning_tokens: 0 }completion_tokens_details但缺少reasoning_tokens时，补零completion_tokens_details时，插入默认值Related Issue / 关联 Issue
Fixes #3081
Screenshots / 截图
N/A（纯后端逻辑修改，无 UI 变动）
Checklist / 检查清单
pnpm typecheckpasses / 通过 TypeScript 类型检查pnpm format:checkpasses / 通过代码格式检查cargo clippypasses (if Rust code changed) / 通过 Clippy 检查（如修改了 Rust 代码）