Resolve common issues with Qoder CLI CN installation, upgrades, PATH, and permissions
This page collects common issues and solutions when installing or upgrading Qoder CLI CN. For installation steps, see Installation and Upgrade.
If running
After installation, run the following commands to confirm it works:
If both produce normal output, the installation succeeded.
Command not found
If running qodercn after installation reports command not found, the directory containing the executable is usually not on PATH.
-
After a global npm install, confirm the global bin directory is on
PATH: -
Changes to
PATHneed to take effect: on Linux / macOS, reopen the terminal or runsourceafter editing your shell config file (such as~/.zshrc,~/.bashrc); on Windows, reopen the terminal after changing system environment variables. -
Verify the install location:
- If installation fails or no binary is available on Windows arm64 devices: that platform is not supported yet; see Installation and Upgrade.
Permission denied
- If you hit permission errors during a global install, avoid forcing the install with administrator privileges. Instead, change the npm global directory to a user-writable path and reinstall.
- Using a version manager (such as nvm) to manage the runtime avoids permission issues in system-level directories.
Upgrade fails or version does not change
- First run the built-in update command:
- If the old version still shows after upgrading, first confirm which binary is being invoked (use
where qodercnon Windows): - If you installed through multiple channels (such as both npm and Homebrew), multiple
qodercnbinaries may exist, and the one earlier onPATHis invoked first. Uninstall the versions from the extra channels and keep only one. - After cleanup, reinstall the latest version through the original channel: for the script install, use
curl -fsSL https://static.qoder.com.cn/qoder-cli-cn/install.sh | bash -s -- --forceto force a reinstall; for npm, usenpm install -g @qodercn-ai/qoderclicn@latest. See Installation and Upgrade for details.
Duplicate installs / multi-version conflicts
- List all matching executables to confirm whether multiple copies exist: on Linux / macOS use
which -a qodercn; on Windows usewhere qodercn(Command Prompt) orGet-Command qodercn -All(PowerShell). - Keep one installation channel and remove the rest to avoid version confusion.
Verify the installation
After installation, run the following commands to confirm it works:
Next steps
- Installation and upgrade guide: Installation and Upgrade.
- Network issues during download or installation: Network, Proxy, and VPC Issues.
- Sign-in issues: Sign-in and Authentication Issues.