No DEEPSEEK settings in the json config file - cc-switch
Quick fix
Upgrade cc-switch to v3.20.0+, tick the reasoning level in the model mapping and save again, to fix config not being written or overwritten by a template.
Symptom
Section titled “Symptom”json文件配置里没有相关DEEPSEEK配置项There are no DEEPSEEK settings in the json config file
When switching or saving a provider in cc-switch (DeepSeek, or a custom openai_responses provider), the config generator has a defect and fails to sync base_url, provider-specific settings, or reasoning_levels into the underlying config file of the target app (Claude, Codex, Hermes). On top of that, when enabling or hot-switching, cc-switch overwrites the target app's catalogue file (~/.codex/cc-switch-model-catalog.json and similar) wholesale from a conservative built-in template — one carrying only none/high reasoning levels, for instance — resetting your custom model parameters and producing model-not-found errors, 429s, or config that simply never applies.
Upgrade cc-switch to v3.20.0 or newer to get the fixes for missing config fields and the catalogue overwrite logic.
For a Codex openai_responses custom provider, tick the correct 思考等级 (reasoning level) for each model under 供应商表单 -> 模型映射 (provider form > model mapping) in cc-switch, so it persists into the config store.
Click 启用 (enable) or 保存 (save) again to trigger a config rewrite, so the target app's JSON/YAML config file holds the complete DeepSeek or custom model parameters.
Affected Versions
Section titled “Affected Versions”Source Issues
Section titled “Source Issues”This page is distilled from 6 real issues
- Why does ~/.codex/cc-switch-model-catalog.json revert after a restart or switch when I edit it by hand?
- cc-switch overwrites that catalogue file wholesale on enable, save, or hot switch to keep state predictable. Do not edit it by hand — tick the reasoning level in the 模型映射 (model mapping) screen in cc-switch v3.20.0+ and let the program write it during generation.
- Codex reports 429 too many requests or model not found after switching to DeepSeek. What now?
- That usually means older cc-switch did not write base_url or the model mapping correctly, so requests still go to the default endpoint or use the wrong test model. Upgrade to the latest version and save the provider config again to force a refresh of the underlying config file.
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.