Skip to content
CC Switch WikiUnofficial Community Wiki

Opening a terminal does not use the complete configuration - CC Switch

Quick fix

Extract through the "shared configuration" panel and tick write, so a full overwrite does not lose plugins and other shared config.

Symptom

Section titled “Symptom”
Error output
通过打开终端的这个功能打开claude，没使用完整的配置，只会覆盖env的api相关字段，这些在env外自定义的不会生效。
English translation

Opening claude through the open-terminal feature does not use the complete configuration — it only overwrites the api-related fields of env, and anything customized outside env does not take effect.

Cause

Section titled “Cause”

cc-switch tried field-level merging in v3.11.0, but it introduced complicated state conflicts and was rolled back to full overwrite in v3.11.1. So when you launch Claude Code through "open terminal", the tool overwrites only the API-related environment variables and does not preserve provider-specific non-API configuration (plugins, hooks, and so on).

The project addressed this with a "shared configuration" mechanism: extract plugins, hooks, and other shared configuration into the shared configuration, and leave "write shared configuration" ticked by default when switching or creating a provider, so that configuration carries across providers and is not wiped by the full-overwrite logic.

Fix

Section titled “Fix”

  1. Go into cc-switch settings and edit the current provider configuration.

  2. Find the "shared configuration" panel and click "extract from current provider" to pull out the plugins and other non-API configuration.

  3. When creating or switching a provider, make sure "write shared configuration" is ticked (it is by default) so that shared configuration is preserved.

Affected Versions

Section titled “Affected Versions”
ToolClaude Code
Versionv3.11.1+
PlatformsWindowsmacOSLinux

Source Issues

Section titled “Source Issues”

This page is distilled from 2 real issues

FAQ

Section titled “FAQ”
Why did my plugin configuration disappear after opening a terminal?
Because cc-switch uses a full-overwrite strategy and keeps only the API-related fields. Use the "shared configuration" panel to extract them and tick "write shared configuration" to preserve plugins and other shared config.
Could it do field-level merging instead of full overwrite?
Not planned for now. v3.11.0 tried field-level merging but introduced state conflicts, so v3.11.1 rolled it back. The recommended way to manage shared settings today is the "shared configuration" mechanism.
Section titled “Related problems”
Connecting gpt5.5 in the codex desktop client, image input and reasoning strength switching do not work - CodexDelete the cc-switch config file under Codex and let it rebuild, or edit cc-switch-model-catalog.json to add the missing reasoning tiers and image modality.2 issues mergedOpening cc on Windows 11 gives a process but no window - cc-switchOn Windows 11, try Windows 7 compatibility in the exe properties. If that fails, use cc-switch-cli to bypass the Tauri 2 GUI white screen.6 issues mergedcc-switch white screen / black screen / crash / no window on launchWork out whether it is corrupt window state, a WebView2/OS compatibility problem, or security software. Handle per symptom; use the CLI build if needed.14 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.