Skip to content
CC Switch WikiUnofficial Community Wiki

Codex kimi keeps sending requests when using the proxy - CC Switch

Quick fix

This is Codex App client behaviour, not a cc-switch fault. Check the client retry or keepalive mechanism.

Symptom

Section titled “Symptom”
Error output
当代理打开，并且通过codex对话后，请求会一直持续发送
English translation

With the proxy on, after a conversation through codex, requests keep being sent continuously

Cause

Section titled “Cause”

Using the Codex App (the Microsoft Store build) with the Kimi provider and the cc-switch proxy, users find requests still going out in the background after the conversation ends, and worry about burning through their quota. Maintainers analysed it: cc-switch only forwards requests as a transparent proxy and cannot initiate a request upstream itself, and in single-provider mode it is bounded by the retry count, so it does not keep sending on its own. The behaviour is confirmed to be the Codex client itself (streaming connection keepalive, background polling, or retry logic), unrelated to cc-switch. This was merged as a duplicate of Issue #3822.

Fix

Section titled “Fix”

  1. Confirm whether the requests come from the Codex App client. Since cc-switch generates no extra traffic, use a packet capture tool or the proxy log to see the source process and URL of the continuing requests, and verify whether it is the Codex client keepalive or retry mechanism.

  2. If it is confirmed to be client behaviour, look in the Codex App settings for options such as "keep connection", "auto retry", or "background sync" and adjust them, or follow the fix upstream in the Codex project.

Affected Versions

Section titled “Affected Versions”
ToolCodex
Version3.16.3
PlatformsWindowsmacOS

Source Issues

Section titled “Source Issues”

This page is distilled from 2 real issues

FAQ

Section titled “FAQ”
Was a cause ever found for this?
Yes — it is confirmed to be the network behaviour of the Codex client itself (App or CLI), such as retry or keepalive, not anomalous requests generated by the cc-switch proxy. cc-switch only forwards; it does not initiate requests.
How do I tell whether a request comes from cc-switch?
cc-switch generates no requests itself. If you see continuous requests, use the proxy log or a packet capture tool to check the source IP and process name. If they come from the Codex process, it is client behaviour.
Section titled “Related problems”
502 Bad Gateway Codex proxy takeover overwrites config.tomlDisable global proxy and switch to rule mode with direct connection to 127.0.0.1, or upgrade cc-switch to avoid fully overwriting config.toml.29 issues mergedHTTP 401 exceeding the 256K context limit - CC Switch & CodexLower the AUTO COMPACT trigger threshold in the Codex config.toml so the real token count of the request body stays under the Kimi 256K limit.2 issues mergedunsupported call: - CodexUpgrade cc-switch to v3.16.4+ to fix tool call name/id overwritten by empty deltas during streaming conversion.1 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.