Skip to content
CC Switch WikiUnofficial Community Wiki

DeepSeek Responses conversion causes low cache hit rate, Codex

Quick fix

For a low cache hit rate with Codex and DeepSeek, check request logs and the proxy conversion path; no confirmed fix is available.

Symptom

Section titled “Symptom”
Error output
Codex DeepSeek 代理中 Responses→Chat 格式转换导致 DeepSeek 前缀缓存命中率极低
English translation

Codex DeepSeek proxy: Responses→Chat format conversion causes an extremely low DeepSeek prefix cache hit rate

Cause

Section titled “Cause”

These issues cover several problems involving Codex and DeepSeek: DeepSeek V4 does not support the Responses API, Codex subagents cannot be used, network connections fail after the proxy is disabled, and prefix cache hit rates are low after Responses conversion. The author of the cache issue believes that unstable serialization when cc-switch converts Responses to Chat Completions causes cache misses. That issue remains open, and the corpus contains no maintainer confirmation of this analysis or a fix. The other problems have no verifiable common cause.

Fix

Section titled “Fix”

  1. Check wire_api, the proxy address, and the target model in the Codex configuration, then review cc-switch proxy_request_logs and compare the request's cache hit data. The issues do not provide a confirmed configuration fix.

  2. If subagents are unavailable, maintainers recommend upgrading to the latest version. If the issue still occurs, provide the CC Switch and Codex versions, direct/routed/aggregated mode, subagent error, and corresponding logs.

Affected Versions

Section titled “Affected Versions”
ToolCodex
Versioncc-switch 3.16.5（缓存问题评论）；3.19.1（子代理 issue）
PlatformsWindows

Source Issues

Section titled “Source Issues”

This page is distilled from 5 real issues

FAQ

Section titled “FAQ”
DeepSeek V4 does not support Responses. Can cc-switch proxy and convert the protocol?
In issue #2463, a maintainer said this request was being tracked in #2461; the corpus does not specify its later support status.
What should I do if DeepSeek in Codex stops working after I disable the proxy?
The maintainer on issue #6952 suggests trying the 4.0 release. If the issue still occurs, provide the version and reproduction steps. The issue gives no specific network fix.
Can the cc-switch proxy reduce DeepSeek prefix cache hit rates?
The author of issue #4763 attributed the low hit rate to the conversion layer from Responses to Chat Completions, but the issue remains open and the corpus contains no maintainer confirmation or solution.
Section titled “Related problems”
cc-switch Usage Statistics Differ from DeepSeek Official Site / Stop UpdatingUpgrade to v3.19.2 or later, then run “Rebuild Codex Usage” once on the “Usage Statistics” page to correct historical overcounts or missing records.22 issues mergedThe proxy takeover claude switch cannot be ticked in Claude Desktop modeIn claude-desktop mode, the takeover section hard-codes the Claude Code (claude) switch instead of the Claude Desktop one, so clicking does nothing.2 issues mergedThe apply_patch tool is unavailable with the Codex proxy onUpgrade to cc-switch v3.16.2 or newer. On a relay, make sure the backend model matches what Codex expects or tool calls fail with routing on.2 issues merged

This is an unofficial community wiki with no affiliation to the cc-switch authors or the project itself. Its content is compiled from the project's public GitHub issues. This site distributes no software.