A default Gemini config appears and cannot be deleted - CC Switch
Quick fix
default is the expected provider CC Switch creates by importing your existing live config. Switch the current provider in settings first, then delete it.
Symptom
Section titled “Symptom”产生一个default配置。而且提示正在使用无法删除。A default config appears. And it says it is in use and cannot be deleted.
On first takeover or config sync, CC Switch imports your existing live config into a `default` provider so the original config is not lost — so seeing a single `default` config is usually expected behaviour. Only "several `default` entries created repeatedly" or "regenerated on every launch" is a different anomaly, needing a version number and reproduction steps to investigate.
The cluster also holds a related variant: a user reported being unable to delete their only Gemini config even though it did not work. Current behaviour protects the provider that is "in use" from deletion. The way through is not to force the delete but to switch to another working provider first (add the official Gemini provider preset, for example), then delete the old config. Another user mentions that on a fresh install, the Gemini tick state under "show on main page" settings does not match what is actually displayed — a display problem from the UI default fallback disagreeing with the backend default, unrelated to how `default` configs are generated.
Check whether the `default` config was created by CC Switch importing your existing live config. If there is only one `default` and its content matches the Gemini / Codex config already on your machine, that is usually expected and you need not delete it.
If you do not want that `default` config, add or switch to another working provider first. For Gemini you can use the official Gemini provider from the presets; once switched, the `default` config is no longer "in use".
Then try deleting the provider config you do not want. If it still says it cannot be deleted, confirm the target is no longer marked in use, or restart CC Switch, switch again, and delete.
If a `default` is regenerated on every launch, or several `default` configs appear, that is not expected. Record your CC Switch version, operating system, the app involved (Gemini CLI / Codex), reproduction steps, and a screenshot, and file or reopen an issue.
Affected Versions
Section titled “Affected Versions”Source Issues
Section titled “Source Issues”This page is distilled from 4 real issues
- Why does a default config keep appearing?
- CC Switch imports your existing live config into a `default` provider so the original config is not lost. A single `default` is usually expected; only several being generated repeatedly needs investigating.
- The default config says it is in use and will not delete. What now?
- Switch to another working provider first so `default` is no longer the config in use, then delete it. The current version protects the provider in use to avoid losing your CLI config by accident.
- I have only one Gemini config and it does not work — can I really not delete it?
- Users have reported this. Maintainers point at the README FAQ explaining that deletion is protected by the "in use" state. Add or switch to another provider first, then delete the broken config.
- I configured a Gemini API and cannot use an official Gemini account. What now?
- Add an official Gemini provider (it is in the presets) and switch to it.
- Gemini does not show on the main page on a fresh install. Is that the same problem?
- That is a related but separate display settings problem: the front-end fallback default is `gemini: false` while the backend default is `gemini: true`, so the settings tick state and the home page display disagree. It is not the same as `default` config generation.
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.