CC Switch config import / sync not taking effect
Quick fix
Upgrade CC Switch to v3.16.1+, and check that WebDAV / cloud sync and the config write path are syncing correctly.
Symptom
Section titled “Symptom”cc-swtich管理的本地自定义技能在技能更新后没有更新,导致无法通过云同步更新另外一台机器的自定义技能A local custom skill managed by cc-swtich did not update after the skill itself was updated, so the custom skill on the other machine cannot be updated through cloud sync.
This problem spans CC Switch's config import, sync, and persistence path. In some cases the UI or a config write never reaches the target app's config file — Hermes updating only the model: block while providers: stays empty, for instance. In others, cloud sync, WebDAV, SQL import/export, or a local skill update does not refresh. Closed issues show v3.16.0 / v3.16.1 fixed Windows environment detection, Codex config and takeover switching, model catalogue refresh, tool and plugin restoration, and some provider format conversions. But WebDAV sync, SQL import performance, cloud sync of updated local skills, and the jobs directory not being cleaned after deleting a session are all still unresolved in the issues provided.
Upgrade CC Switch to v3.16.1 or newer, then re-check config switching, provider saving, and environment detection.
If ~/.hermes/config.yaml is missing its providers: block after a Hermes provider switch, copy the provider config from the CC Switch database into config.yaml by hand as a stopgap.
~/.hermes/config.yaml providers:# 从 CC Switch 当前供应商配置复制 api_key / base_url 等字段If you sync cc-switch.db with OneDrive, Nutstore, or WebDAV, make sure the sync directory holds only the config data that needs syncing. A cc-switch-<hostname>.db appearing means several machines wrote to the same SQLite file and the cloud drive made a conflict copy.
If a SQL import hangs on "importing" for a long time, upgrade to v3.19.2 or newer and retry. That version switched the export to batched writes and merged the restore into a single transaction.
If CC Switch does not sync a local custom skill after you update it, re-import the skill. The issues do not yet offer a confirmed auto-refresh fix.
Affected Versions
Section titled “Affected Versions”Source Issues
Section titled “Source Issues”This page is distilled from 23 real issues
- #502多设备 onedrive 同步数据出现多个 cc-switch.db
- #1335现在的sqlite设计会拖垮坚果云/OneDrive
- #1436WebDav异常
- #1925skill导入现有的,没有做防抖,点击2次会导入重复的skill
- #1990云同步时使用tailscale做的内网穿透报502错误
- #2100SQL导出导入问题
- #2134[Bug] UI freeze in Sessions Management when handling large number of sessions or long content
- #2244Claude编辑供应商页面中,模型一键设置按钮点击后,haiku模型和sonnet模型的输入框中没有根据选择的主模型进行同步模型id
- #2558配置文件同步不及时
- #2870出现非常多的500的请求,不知道从何而来
- #3107重新从ZIP安装导入本地skill,无法导入
- #3130最近频繁出现ccswitch卡死需要强制退出情况,更多是在轻量模式切换的时候
- #3375设置的关于页面本地环境检查问题
- #3712Claude Desktop 不支持深度链接添加配置
- #4198claude desktop win无法注入3p配置或使用供应商切换
- #4284在CC Switch切换时,Hermes提供者未与config.yaml同步
- #4749路由模式下安装插件没有同步到供应商配置文件
- #4854[BUG] 删除 agents 模式会话后,claude agents view 仍显示已删除的会话条目
- #5154作者吃赞助能理解,越加越多也理解,gpt5.6的价格能不能更新一下?
- #5621WebDAV 同步完全不可用:NAS 对已存在目录 MKCOL 返回 400,逐层建目录中止连累上传/下载
- #5700删除 Claude 会话后 ~/.claude/jobs/ 目录未同步清理
- #5880cc-swtich管理的本地自定义技能无法通过webdav云同步更新
- #6141应用通用配置时,供应商配置数组字段被整体覆盖 "permissions.deny" 原有条目丢失
- Why does the Hermes local environment check still fail after upgrading?
- Users report version detection problems with hermes even after updating, for example uv trampoline failed to spawn Python child process Caused by: entity not found (os error 2). Keep checking the hermes executable path and whether the Python/uv environment is usable.
- Why does putting cc-switch.db on OneDrive or Nutstore cause problems?
- cc-switch.db holds runtime data. Switching provider, request logs, and health checks all rewrite the SQLite file frequently, causing constant cloud uploads and sync lag, and possibly a cc-switch-<hostname>.db conflict copy.
- WebDAV sync reports MKCOL failed. What now?
- On a 502 Bad Gateway, check your tunnel, reverse proxy, or WebDAV service reachability first. If a NAS returns 400 Bad Request for a directory that already exists, analysis in the issue argues CC Switch needs to treat 400 as an already-exists case; no fix is confirmed yet.
- Why does the Agents panel still show a Claude Code session I deleted?
- When deleting a session cc-switch may remove only the transcript file, without cleaning the session index or job data under ~/.claude/jobs/, so the Claude Code Agents view still shows ghost entries.
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.