command not found

Exit code 127 means the shell could not start it

This is distinct from a program that runs and fails. Nothing executed.

command -v jq
type -a python3

ls -l /usr/local/bin/tool
echo $PATH

Local installs often land in /usr/local/bin, which some minimal PATHs omit.

ls -l ./script.sh

Missing execute bit gives 126, not 127. Both surface as "not found" to many users.

head -1 ./script.sh
ls -l $(head -1 ./script.sh | cut -c3-)

Scope: failure mode: Exit code 127, and the PATH problem behind it.

CliHelper documents failure modes of third-party command line tools. No software is stored or distributed here.