Skip to content

When using deepseek with openai-response in the Codex app, an error is encountered: #1594

Closed as not planned

Description

@lusile2024

Client or integration

Codex App

Area

Proxy and routing

Summary

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.

Activity

  1. added
    proxyHTTP proxy, routing, reverse-proxy / management auth
    on Aug 13, 2026
  2. coderabbitai commented on Aug 13, 2026

    @coderabbitai
    Contributor
    ⚠️ Possible Duplicate Issue(s)
    🔗 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 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!

  3. lidge-jun commented on Aug 14, 2026

    @lidge-jun
    Owner

    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가 필요하며, 현재 정보만으로는 진단이 어렵습니다.

  4. chenli1989 commented on Aug 14, 2026

    @chenli1989

    @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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingproxyHTTP proxy, routing, reverse-proxy / management auth

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions