You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
When using deepseek with openai-response in the Codex app, an error is encountered: #1594
When using deepseek with openai-response in the Codex app, an error is encountered: The reasoning_text in the thinking mode must be passed back to the API.
Reproduction
1.ocx start
2.add deepseek with openai-response
3.ocx sync
4.codex desktop
Version
2.12.0
Operating system
windows 10
Provider and model
No response
Logs or error output
Screenshots and supporting files
No response
Redacted configuration
Checks
I searched existing issues and documentation.
I removed secrets, tokens, account details, request credentials, and personal data.
Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.
Create Plan
🧪 Issue enrichment is currently in open beta.
To disable automatic issue enrichment, add the following to your .coderabbit.yaml:
issue_enrichment:
auto_enrich:
enabled: false
💬 Have feedback or questions? Drop into our discord!
Closing as needs-info — diagnosing this requires a redacted wire capture showing the actual request/response exchange with the DeepSeek provider. If you can provide the capture (with secrets redacted), please reopen. 재현을 위한 wire capture가 필요하며, 현재 정보만으로는 진단이 어렵습니다.
@lusile2024 I encountered the same issue, and the following solution worked for me:
Adding the preserveResponsesReasoningContent property and enabling it within the configuration for the relevant provider resolves the issue. I hope this helps.
Activity
coderabbitai commentedon Aug 13, 2026
🔗 Related PRs
#906 - fix(deepseek): preserve Responses reasoning replay on continuations (
#875) [open]#1499 - fix(deepseek): keep parallel reasoning replay on continuation [open]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.🧪 Issue enrichment is currently in open beta.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!
lidge-jun commentedon Aug 14, 2026
Closing as needs-info — diagnosing this requires a redacted wire capture showing the actual request/response exchange with the DeepSeek provider. If you can provide the capture (with secrets redacted), please reopen. 재현을 위한 wire capture가 필요하며, 현재 정보만으로는 진단이 어렵습니다.
chenli1989 commentedon Aug 14, 2026
@lusile2024 I encountered the same issue, and the following solution worked for me:
Adding the
preserveResponsesReasoningContentproperty and enabling it within the configuration for the relevant provider resolves the issue. I hope this helps.