Troubleshooting

"Command not found" after install

The launcher was added to your PATH, but your current shell session may be stale. Restart the terminal, or re-source your shell config:

source ~/.zshrc      # macOS / modern Linux
source ~/.bashrc     # classic bash

Install script blocked on Windows

PowerShell may restrict remote scripts by default. Re-run the installer with an execution-policy bypass:

powershell -ExecutionPolicy Bypass -c "irm https://cli-launcher.veyl.in/install.ps1 | iex"

An agent won't install

Most install failures come down to a missing runtime. Check the in-app dependency panel — it reports Node.js and Python status. Then:

• Node-based agents need a current Node.js LTS. Run node -v to confirm.
• Python-based agents need Python 3.10+. Run python3 --version to confirm.
• If a tool is still missing, install it through the panel's catalog rather than your global environment so CLI Launcher keeps managing it.

Update failed or stuck

Updates download from GitHub releases. If one fails, check your network connection and retry from the agent's Update button. A stuck entry can usually be cleared by restarting the app.

Theme looks wrong after an update

A cached stylesheet can lag behind. Hard-refresh the app (or clear its cache) and confirm your theme choice in the top-bar toggle. See Theming for how themes resolve.