Skip to content

All Codex settings and plugins reset after restarting CC Switch

Quick fix

Put cross-provider Codex/Claude Code config and plugins into 通用配置 (general config) so a switch cannot wipe them. Recover lost content from the default provider.

Error output
重启CC switch后打开codex,所有的设置、插件、都会丢失重置。
English translation

After restarting CC Switch and opening codex, all the settings and plugins are lost and reset.

From the reports, cc-switch regenerates the target CLI's config from whichever provider is currently active after a switch or restart. If you only wrote your API, plugins, Marketplace, or MCP into one provider's JSON, none of it carries into the next config — which shows up as Codex settings and plugins reset, Claude Code plugins inactive, or the API address gone. General config is the right place to keep this across providers: several reports confirm that writing the config into 通用配置 (general config) avoids the loss, and anything already lost has to be recovered from the default provider or general config.

The same thread has several variants: Codex session history is bound to model_provider, so an old session cannot find its original provider after a switch (#2615); MCP config gets overwritten into a wrong structure and works fine only with cc-switch closed (#946); every configured Codex desktop provider becoming unusable after upgrading to v3.16.5 (#4948); and the config file not existing when generating a terminal command for a specific provider (#1430). All of these point at the config switch/sync logic rather than any provider's own connectivity.

  1. In CC Switch, write the Codex / Claude Code settings, plugins, Marketplace, and MCP config you need across providers into 通用配置 (general config), then switch provider.

  2. If the config is already lost, first check the default provider created when CC Switch was installed or imported. If you deleted it, check whether the original config is still in 通用配置 (general config) (#1459).

  3. For Codex session history: an old session still reporting it cannot find the original provider after a switch is because Codex sessions are bound to model_provider and are not migrated automatically. Switch back to the original provider, or follow the tracking issue for a fix (#2615).

  4. If MCP in Claude Code gains an extra level of nesting and behaves once cc-switch is closed, cc-switch is overwriting the config while open. Put the working MCP config into general config rather than repeating nested copies inside a single provider JSON (#946).

ToolCodex / Claude Code
Version3.12.0 - 3.19.2(受影响范围;未给出统一修复版本)
PlatformsWindowsmacOS
Every Codex setting and plugin is lost after restarting CC Switch on Windows. Is there a workaround?
Yes. Writing the config into 通用配置 (general config) prevents the loss recurring — several reports confirm this workaround.
The Claude Code plugin files are still in ~/.claude/plugins — why are the plugins inactive after switching provider?
The plugin files are not lost, but the config that activates them was overwritten by the switch. Recover it from the default provider or general config, or move the plugin config into general config.
Codex conversation history reports it cannot find the original provider after a switch. Can it be recovered?
Codex sessions are bound to model_provider, so history is affected by a switch. Switch back to the original provider, or follow the tracking issue for the merged fix.

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.