Skip to content
CC Switch WikiUnofficial Community Wiki

env: node: No such file or directory - cc-switch

Quick fix

Upgrade cc-switch to v3.18.0+, which fixes node not being found when updating Codex because a macOS GUI launch has no PATH.

Symptom

Section titled “Symptom”
Error output
env: node: No such file or directory

Cause

Section titled “Cause”

On macOS, launching cc-switch from Finder or the Dock gives the GUI process a system PATH that does not include the Homebrew directories (/opt/homebrew/bin). Since the npm and Codex launch scripts rely on `#!/usr/bin/env node`, the missing PATH means node cannot be resolved and update or lifecycle commands fail.

Note the cluster also holds other environment detection variants. On Windows, the extension-less codex shim npm generates was once misread as a separate install, producing a "several installations detected" warning (fixed in v3.16.5). Conversations disappearing after a WSL environment switch is a Codex problem in its own right.

Fix

Section titled “Fix”

  1. Upgrade cc-switch to v3.18.0 or newer. That version injects the correct PATH when calling npm, so node resolves properly.

  2. If you cannot upgrade right away, launch cc-switch from a terminal on the command line so it inherits the terminal's full PATH, rather than from Finder or the Dock.

Affected Versions

Section titled “Affected Versions”
Toolcc-switch
Version3.16.2 - 3.16.4 (受影响范围)，v3.18.0 修复
PlatformsmacOSWindows

Source Issues

Section titled “Source Issues”

This page is distilled from 5 real issues

FAQ

Section titled “FAQ”
Windows reports "several installations detected" and the extension-less codex shows as unrunnable. What now?
That is a misjudgement in cc-switch v3.16.4 and earlier. On Windows, npm generates codex, codex.cmd, and codex.ps1 together; upgrading cc-switch to v3.16.5 or newer merges them into one detection automatically.
My project conversations disappeared after switching the agent environment from PowerShell to WSL in cc-switch.
That is a problem in the Codex app itself rather than a cc-switch bug — report it to Codex.
Section titled “Related problems”
bash: cannot set terminal process group - cc-switchA known 3.18.0 bug when checking the local proxy environment on Linux. Downgrade below 3.18.0 and configure the proxy in the terminal by hand.5 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 mergedcc-switch loses Claude Code / Codex MCP configurationUpgrade cc-switch, disable or use unified MCP takeover carefully, find the one broken MCP entry, and fix rewritten command/type/path fields.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.