Is codex no longer supported now that it became ChatGPT? - cc-switch
Quick fix
Upgrade to cc-switch v3.17.0, which supports provider switching after Codex merged into ChatGPT Desktop, so old config is not overwritten.
Symptom
Section titled “Symptom”codex升级为ChatGPT后不适配了吗，之前配置了codex+deepseek。但是codex升级后，现在是ChatGPT了，同步把chatgpt的名字改回codex了，但是也无法使用。另外 ccswitch最新版本 前台的config文件也无法修改了，是我遇到了这个问题还是大家都遇到了呢？Is codex no longer supported now that it became ChatGPT? I had codex + deepseek configured before. After the codex upgrade it is now ChatGPT; I renamed chatgpt back to codex to match, but it still will not work. Also, the config file in the front end of the latest ccswitch can no longer be edited. Is it just me or is everyone hitting this?
After Codex became ChatGPT Desktop, where and how the login state, sessions, and local MCP config are read and written changed, while older cc-switch still writes and takes over along the old Codex config paths. Switching to a third-party provider such as DeepSeek then fails, and users see the config file "reverting to how it was after saving" along with a scrambled login state and sessions. A maintainer confirmed in #5280 that v3.17.0 supports official-account proxy takeover after the Codex merge into ChatGPT Desktop, and can switch to a third-party provider while preserving the official login.
Several variants sit in the same batch of upgrade feedback and need separating: #3945 is the "Anthropic system message hoisting" (#3775) introduced in v3.16.2 rewriting the prefix of requests to DeepSeek and breaking prefix cache reuse, reverted and with statistics corrected in v3.16.4. #4341 is Codex using the OpenAI Responses API tool call protocol while the third-party upstream returns Chat Completions style, so the two-way conversion in the adaptation layer fails and it "answers once then stops" — still open. #3922 is the model list in the Codex config no longer being fetched automatically after 3.15.0, requiring manual entry — still open. And #4338 notes Claude Code 2.1.178 can reach DeepSeek directly without enabling local routing.
Upgrade cc-switch to v3.17.0, which supports official-account proxy takeover after Codex merged into ChatGPT Desktop (confirmed by a maintainer in #5280).
After upgrading, close ChatGPT Desktop first, complete the switch to DeepSeek or another provider in cc-switch, then reopen ChatGPT Desktop. Users who upgraded directly report the new models showing correctly this way.
If Codex still stops after one turn, or the model list can only be typed in by hand, keep following #4341 / #3922. If the DeepSeek cache hit rate dropped, confirm you are on at least v3.16.4.
Affected Versions
Section titled “Affected Versions”Source Issues
Section titled “Source Issues”This page is distilled from 5 real issues
- Did you reinstall from clean or upgrade in place on codex?
- People have tried both. Some upgraded in place and switch between DS and GLM fine; others had their old config scrambled by the older cc-switch and had to reinstall. After upgrading to v3.17.0 and switching, a reinstall should not be necessary.
- Why does the config file revert to how it was after saving?
- Older cc-switch still writes the ChatGPT Desktop config along the old Codex config paths, so it is overwritten again after you save. v3.17.0 supports the new config takeover.
- Does closing ChatGPT, switching provider in cc-switch, then reopening ChatGPT work?
- Users who upgraded Codex directly report DS and GLM both showing the new models in that order — provided cc-switch is already on v3.17.0, since older versions may still overwrite the config.
Related problems
Section titled “Related problems”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.