Skip to content
CC Switch WikiUnofficial Community Wiki

Common Issues After Upgrading cc-switch

Quick fix

Upgrade to v4.0 or later; most sync, switching, and display issues from older versions are fixed.

Symptom

Section titled “Symptom”
Error output
打开新版本没有API，显示“还没有添加任何供应商”。
English translation

Opening the new version shows no API and displays “还没有添加任何供应商”。

Cause

Section titled “Cause”

Most of these issues occurred in cc-switch 3.13.0 and earlier. At the time, flaws in configuration writes, database upgrades, and interface refresh logic caused data to become unsynchronized after upgrades or switching. v4.0 rewrote the provider switching and configuration writing workflows, and improved automatic backups before database migrations.

Fix

Section titled “Fix”

  1. Back up the current configuration: do not delete any files under ~/.cc-switch

  2. Download and install the latest version (v4.0 or later)

    下载地址
    https://github.com/farion1231/cc-switch/releases/latest

  3. After upgrading, check that the provider list displays correctly

  4. If the issue persists, check the log file /.cc-switch/logs/cc-switch.log and provide it to the developers

Affected Versions

Section titled “Affected Versions”
Toolcc-switch
Version3.13.0 及更早版本
PlatformsWindowsmacOS

Source Issues

Section titled “Source Issues”

This page is distilled from 5 real issues

FAQ

Section titled “FAQ”
What should I do if all my previous API configurations disappeared after upgrading?
Do not delete the ~/.cc-switch directory yet; it may contain automatic backups. Install v4.0 or later; the new version automatically backs up the database before upgrading it. If the list is still empty, check the log file and contact the developers.
What should I do if the list does not update after restoring from a cloud backup?
This is a known issue in v3.13.0; you need to restart the app to see the update. v4.0 rewrote the interface refresh logic, so the list should update automatically after downloading a backup.
Why does switching models show an error even though the switch succeeded?
This is a concurrency state issue in v3.13.0. v4.0 rewrote the switching workflow and added an application-level lock; write results and failure reasons are recorded in the log.
Why is the Hermes latest version displayed inaccurately?
This is because hermes-agent stopped being updated on PyPI, while upstream switched to publishing releases through GitHub Releases. The fix has been committed to the main branch and will be released with the next version.
Section titled “Related problems”
Codex conversations with third-party models frequently stop automaticallycc-switch loses function call name/call_id during Responses API conversion. Connect DeepSeek directly to Codex, or upgrade cc-switch and retest.7 issues mergedCC Switch flashes once when clicking any buttonOn Windows, use WebView2 152.0.4191.62 Fixed Version only for CC Switch to avoid click flashing with WebView2 153.0.4234.32.2 issues mergedsettings.json gets reset - Claude CodeWrite shared fields like plugins and hooks into "Common Config" and check write-back on switching; if takeover mode misbehaves, disable it, switch provider…12 issues merged

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.