Local routing failure Codex

Quick fix

Upgrade cc-switch from 3.16.1 to 3.16.4 and observe whether the issue recurs; this version includes hardening for Codex routing takeover.

Symptom

Error outputCopy

本地路由失败

English translation

Local routing failure

Cause

When using a third-party model routing proxy for Codex on Windows, initial conversations and model switching work normally, but local routing can fail after running for some time, with a 400 response in the logs. Another user reported that the issue recurs intermittently.

The maintainer stated that 3.16.2 through 3.16.4 include several hardening changes for Codex routing takeover, including serialized switching, Live configuration refresh after hot switching, and boundary fixes for the Chat Completions and Responses paths. These changes may cover this issue, but the original post did not confirm whether it still recurred after upgrading.

Fix

1. 1

   Upgrade cc-switch from 3.16.1 to 3.16.4, then monitor for several days to see whether the issue still recurs.

2. 2

   If it still recurs, add the specific provider or preset, complete logs including the 400 response body at the time of the error, and whether local routing takeover is enabled to the source Issue.

Affected Versions

ToolCodex

Version3.16.1（受影响版本）

PlatformsWindows

Source Issues

This page is distilled from 1 real issues

• #36613.16.1 路由代理不稳定

FAQ

(No FAQ yet)

Related problems

stream disconnected before completionUpdate CC Switch to 4.0 or the latest version and retry; the maintainer recommended this, but the original issue did not confirm a resolution.1 issues mergedProxy not working, constant reconnect after entering a question; CodexThe separate proxy feature in cc-switch was removed; set the proxy via $env:http_proxy in PowerShell, then run Codex.1 issues mergedToggling proxy or switching third-party accounts invalidates official Codex sign-inNo verifiable solution was provided; the issue was suggested for further reporting to cc-switch-cli.1 issues merged