Codex Current Provider Does Not Exist, Cannot Take Over Live Configuration - Codex

Quick fix

Add a custom provider on the Codex page in CC Switch, then enable Codex local routing.

Symptom

Error outputCopy

切换路由状态失败: Codex 当前供应商不存在，无法接管 Live 配置

English translation

Routing state switch failed: Codex Current Provider Does Not Exist, Cannot Take Over Live Configuration

Cause

Codex local routing in v3.16.1 and v3.16.2 requires a current provider to exist in Codex when taking over the Live configuration. One user reported this error after adding a provider in the Claude Code module but not in Codex; after adding a custom provider on the Codex page, the routing switch worked. The maintainer later explained that v4.0 reworked local routing: enabling routing no longer takes over and backs up the entire Codex configuration, so this error path no longer exists. Another v3.16.1 user initially saw only the generic message “切换路由状态失败: {{detail}}”; after upgrading to v3.16.2 or later, check the specific error details.

Fix

1. 1

   When using v3.16.x, first add a custom provider on the Codex page in CC Switch, then try enabling Codex routing. A user confirmed this worked.

2. 2

   If “无法接管 Live 配置” still occurs, upgrade to v4.0 or later; the maintainer said this error path was removed in that version.

3. 3

   If routing still cannot be enabled on v3.16.2 or later, record the specific detail shown in the dialog and the logs, then report it again.

Affected Versions

ToolCodex

Version3.16.1 - 3.16.2（受影响）；v4.0 重做本地路由后该报错路径已移除

PlatformsmacOS

Source Issues

This page is distilled from 2 real issues

• #3878切换路由状态失败: {{detail}}
• #4170切换路由状态失败: Codex 当前供应商不存在，无法接管 Live 配置

FAQ

Why does Codex routing still fail when I added a custom provider only in the Claude Code module?

A user reported that a provider in the Claude Code module cannot replace a provider on the Codex page; after adding a custom provider on the Codex page, the routing switch worked.

What should I do if it still fails after upgrading to v3.16.2?

Check whether the dialog shows a specific detail. If it still fails, the maintainer recommends reporting the specific detail and logs again to help identify the cause.

Can “无法接管 Live 配置” still occur after upgrading to v4.0?

The maintainer said v4.0 reworked local routing and removed this error path. If the routing switch still reports an error, provide the error and logs.

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