CLI install can fail with no error message

[lee-b]

Before submitting your bug report

• I've tried using the "Ask AI" feature on the Continue docs site to see if the docs have an answer
• I'm not able to find a related conversation on GitHub discussions that reports the same bug
• I'm not able to find an open issue that reports the same bug
• I've seen the troubleshooting guide on the Continue Docs

Relevant environment info

- OS: Linux

Description

The CLI install script can exit with no more explanation than "Installation failed. Cleaning up":

==> Found Node.js v22.22.2
+ version_gte 22.22.2 20.20.1
++ printf '%s\n' 20.20.1 22.22.2
++ sort -V
++ head -n1
+ '[' 20.20.1 = 20.20.1 ']'
+ success 'Node.js meets requirements (>= v20.20.1)'
+ printf '\033[0;32m==>\033[0m \033[1m%s\033[0m\n' 'Node.js meets requirements (>= v20.20.1)'
==> Node.js meets requirements (>= v20.20.1)
+ return 0
+ setup_npm_path
+ local npm_bin
++ npm config get prefix
+ npm_bin=/bin
+ cleanup
+ local exit_code=127
+ '[' 127 -ne 0 ']'
+ warn 'Installation failed. Cleaning up...'
+ printf '\033[1;33m==> Warning:\033[0m %s\n' 'Installation failed. Cleaning up...'
==> Warning: Installation failed. Cleaning up...
+ '[' false = true ']'
+ exit 127

Seems that the nodejs package was only partially installed in this case, and npm was missing.

To reproduce

No response

Log output

[pandego]

The interesting clue in the shell trace is this line:

++ npm config get prefix
+ npm_bin=/bin

So the installer has already accepted the Node binary, but then it falls into setup_npm_path assuming npm is present and sane. In the failure case you described, that assumption is false, which is why the script exits later with the generic cleanup path instead of a useful diagnosis.

Two concrete hardening tweaks seem worth making here:

1. Do an explicit command -v npm check right after the Node version check, before setup_npm_path.
2. If npm config get prefix resolves to something suspicious like /bin or the command fails, emit a targeted error like Node.js was found but npm is missing or misconfigured.

That would turn this from a silent install failure into an actionable package-manager problem, which is especially useful on distros where nodejs and npm are split packages.