Skip to content
CC Switch WikiUnofficial Community Wiki

Not installed / not installed or not executable - CC Switch

Quick fix

Upgrade CC Switch to v3.20.0+ for custom npm prefix and macOS detection failures; the false "several installations" on Windows needs v3.16.5+.

Symptom

Section titled “Symptom”
Error output
未安装 / not installed or not executable
English translation

Not installed / not installed or not executable

Cause

Section titled “Cause”

The CC Switch local environment check had several detection logic defects in early versions, producing different anomalies per platform. On Windows, if you changed the npm global package prefix, the old detection logic hard-coded %APPDATA%\npm and falsely reported the tool as not installed. On macOS, a tool installed globally through npm with node installed via brew was not recognised correctly. Separately, the .cmd and similar wrapper scripts npm generates on Windows were misread as several independent instances, producing a false "several installations detected". For WSL and a Windows host, one instance can only manage one config directory.

Fix

Section titled “Fix”

  1. Upgrade CC Switch to v3.20.0 or newer. That version reworked Windows CLI detection (merging the registry PATH and scanning a custom npm prefix) and fixed Codex/Gemini/OpenCode detection on macOS.

  2. For a false "several installations detected" caused by npm wrapper scripts, make sure you are on at least v3.16.5, which adjusted candidate executable enumeration and deduplicates wrapper scripts in the same directory.

  3. To manage Windows and WSL configs separately, set a custom config directory per CLI tool in CC Switch settings (~/.gemini/, for example), or run two CC Switch instances pointing at different config paths.

Affected Versions

Section titled “Affected Versions”
Toolcc-switch
Version< 3.20.0 (affected range)
PlatformsWindowsmacOSLinux

Source Issues

Section titled “Source Issues”

This page is distilled from 4 real issues

FAQ

Section titled “FAQ”
Why does the command run fine in a terminal while CC Switch says not installed?
Usually because you changed the npm global package prefix (npm config set prefix) while older CC Switch only scanned the hard-coded %APPDATA%\npm. Upgrading to v3.20.0+ reads the real npm prefix and detects it correctly.
What is behind "several installations detected" on Windows?
A global npm install on Windows generates an extension-less script plus .cmd/.ps1 wrappers. The diagnostic logic in v3.16.0 to v3.16.4 mistook them for separate installations. Upgrading to v3.16.5+ deduplicates them automatically.
How do I manage config directories on a Windows host and in WSL at the same time?
One CC Switch instance can only manage one directory config. Point the CLI tool directory at the WSL mount path in settings, or run two CC Switch instances managing one each.
Section titled “Related problems”
Restarting the terminal and running gemini asks for an api-key - Gemini CLIUpdate cc-switch for the save-clears-config bug. If it still fails, that is a Gemini CLI read bug — put the environment variables in bash_profile.3 issues mergedInstalled but cannot run in current environment, please check CC SwitchUpgrade to CC Switch v3.16.1+ to fix Windows `cmd /C` quote handling that misreports installed CLI as broken.1 issues mergedclaude cli exists locally but the about settings say not installed - CC SwitchUpgrade CC Switch to v3.16.5 or newer, fixing the false conflict from multiple npm global package entry points on Windows and the garbled paths.3 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.