Local Claude CLI installed but Settings says it isn't - CC Switch
Quick fix
Upgrade CC Switch to v3.16.5 or later to fix false installation conflicts and garbled paths on Windows.
Symptom
Section titled “Symptom”本地有claude cli但是关于设置里显示未安装,点了安装又说有了,安装失败The local Claude CLI is installed, but Settings says it isn't. When I click Install, it says it is already there, then reports that installation failed.
On Windows, tools such as nvm can cause npm to generate multiple entry files with the same name for one global package (for example, an extensionless Unix shell script and a `.cmd` batch file). Older versions of CC Switch treated these files as separate installations and reported a conflict during local environment checks. This feature was also disabled entirely in v3.11.1 due to a side effect from a protocol handler. In addition, the conflict diagnosis interface in v3.16.2 had a frontend rendering bug that garbled displayed file paths (for example, showing `gemmini` instead of `gemini`).
Upgrade CC Switch to v3.16.5 or later. This version fixes the logic for merging `.cmd`/`.exe` and extensionless shims on Windows, and anchors version detection to the actual runnable entry point, preventing false reports of multiple installation conflicts.
Affected Versions
Section titled “Affected Versions”Source Issues
Section titled “Source Issues”This page is distilled from 3 real issues
- #1266[Bug] v3.11.1 completely disables env check on Windows, breaking CLI version detection
- #4122[Bug] Local environment check UI displays garbled/nonsensical file paths on Windows (e.g. 'opeencode' instead of 'opencode', 'opencode.crmd' instead of 'opencode.cmd')
- #4666本地有claude cli但是关于设置里显示未安装,点了安装又说有了,安装失败
- What should I do if nvm reports an installation conflict?
- On Windows, npm generates multiple entry files (such as `.cmd` and extensionless scripts), which older versions of CC Switch incorrectly reported as a conflict. Upgrade to v3.16.5 to fix this.
- Why is CLI tool version information completely missing on Windows?
- In v3.11.1, environment checks were temporarily disabled due to a side effect from a protocol handler. Upgrade to the latest version to re-enable this feature.
- Why does the environment check interface show misspelled file paths (such as opeencode)?
- This is a frontend text rendering bug in v3.16.2; the actual filesystem paths are correct. Upgrade to v3.16.5 or later to fix it.
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.