Skip to content
CC Switch WikiUnofficial Community Wiki

Claude Code preference changes are not synced back during proxy takeover

Quick fix

Upgrade to v4.0.0; when switching providers, Claude Code preferences remain in ~/.claude/settings.json.

Symptom

Section titled “Symptom”
Error output
The changes made in Claude Code do not sync back to CC Switch.

Cause

Section titled “Cause”

In CC Switch 3.20.2, the proxy takeover path uses the configuration in the database and bypasses the regular switching flow that writes live settings back to Common Config. As a result, preferences changed through Claude Code’s `/autocompact` or `/config` do not sync automatically; a later hot switch may also overwrite them with old values. The possibility of a later overwrite comes from the issue’s code path analysis; the author did not retest that scenario after applying the manual fix.

The maintainer said that v4.0.0 removed generic configuration fragments and live writeback. When switching providers, it replaces only key fields such as the address, credentials, and model, while other preferences remain in `~/.claude/settings.json`, so syncing them back to CC Switch is no longer necessary.

Fix

Section titled “Fix”

  1. Upgrade to v4.0.0 or later. The maintainer says that when switching providers, the new version preserves preferences in `~/.claude/settings.json`.

  2. To change global settings, adjust the `settings.json` content after switching at the bottom of the provider editor; these settings are written directly to the live file.

Affected Versions

Section titled “Affected Versions”
ToolClaude Code
Version3.20.2（受影响的 CC Switch 版本）；维护者称 v4.0.0 已从机制上消除此问题
PlatformsWindows

Source Issues

Section titled “Source Issues”

This page is distilled from 1 real issues

FAQ

Section titled “FAQ”
After upgrading to v4.0.0, do preferences changed through `/config` still need to sync to Common Config?
The maintainer says no. When switching providers, v4 preserves preferences in `~/.claude/settings.json` and no longer syncs them through live writeback.
Which settings does switching providers change in the new routing mode?
The maintainer says that routing mode writes only a local address and placeholder credentials; switching providers replaces only key fields such as the address, credentials, and model.
Section titled “Related problems”
Codex desktop cannot see modelsSign in to official ChatGPT, enable “Keep official login when switching to third parties,” and enable local routing. Restart Codex.6 issues mergedRequest exceeds the context windowNo verified solution was provided in the original post; this issue was closed as a duplicate related to catalog configuration and automatic compression.1 issues mergedsettings.json overwritten by cc-switchWrite non-env custom settings to “General Configuration” and select “Write General Configuration”; field-level merging is not planned.4 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.