Skip to main content
Troubleshooting

Installation and Upgrade Issues

Troubleshoot common issues related to Qoder CLI installation, upgrades, PATH, and permissions.

This page summarizes common issues and solutions when installing or upgrading Qoder CLI. For installation steps, see Installation and Upgrade.

command not found

If running qoder after installation results in a command not found error, it is usually because the directory containing the executable is not in your PATH.
  • After a global installation via npm, ensure the global bin directory is added to your PATH:
    npm config get prefix   # Check the global installation prefix
    # Add <prefix>/bin to PATH
    
  • After modifying your PATH, apply the changes: on Linux / macOS, after editing the shell configuration file (such as ~/.zshrc or ~/.bashrc), restart the terminal or run source; on Windows, after modifying system environment variables, restart the terminal.
  • Verify the installation location:
    # Linux / macOS
    which qoder
    
    # Windows
    where qoder          # Command Prompt
    Get-Command qoder    # PowerShell
    
  • If installation fails or no binary is available on Windows arm64 devices: this platform is not currently supported. See Installation and Upgrade.

permission denied

  • If you encounter permission errors during global installation, avoid forcing the installation with administrator privileges. It is recommended to change the npm Global Directory to a user-writable path and then reinstall.
  • Using a Version Manager (such as nvm) to manage your runtime can avoid permission issues with system-level directories.

Upgrade Failed or Version Not Updated

  • First, run the built-in update command:
    qoder update
    
  • If the old version is still displayed after upgrading, first check which binary is currently being invoked (use where qoder on Windows):
    which qoder
    qoder --version
    
  • If installed via multiple channels (e.g., using both npm and Homebrew), multiple qoder may exist, and the one appearing first in your PATH will be invoked. Uninstall the versions from redundant channels and keep only one.
  • After cleanup, reinstall the latest version via the original channel: for script installations, use curl -fsSL https://qoder.com/install | bash -s -- --force to force a reinstall; for npm installations, use npm install -g @qoder-ai/qodercli@latest. See Installation and Upgrade for details.

Duplicate Installations / Multi-Version Conflicts

  • List all matching executables to check for multiple copies: use which -a qoder on Linux / macOS, and where qoder (Command Prompt) or Get-Command qoder -All (PowerShell) on Windows.
  • Keep only one installation channel and remove the others to avoid version confusion.

Verify Installation

After installation is complete, run the following commands to confirm it is working:
qoder --version
qoder --help
If both commands produce normal output, the installation was successful.

Next Steps