What to Do If the Terminal Says It Can't Find node, npx, or hackcat-local?
First fix the runtime environment of the target terminal, then start using the standard command in the settings.
First Determine Which Program Is Missing
If node or npx is unrecognized, it usually means the current terminal does not have an available Node runtime environment; the current client requires Node.js 18 or higher. Check should be done under the same system user and terminal on the target computer. Another terminal or machine running it does not guarantee the current process sees the same path. After preparing the environment, reopen the terminal to confirm the program is available.
Do Not Treat Optional Global Installation as Mandatory
If only hackcat-local is not found, first confirm whether you have actually performed a global installation. The usual process is to copy the entire command from Settings → Remote Control; it will prepare and start the client and does not require you to first enter a globally installed short command. Do not run only the last part of the command, and do not treat the source build process in the developer documentation as the only fix method.
After Starting, Continue to Check the Connection Phase
After the program starts, account credentials, current service address, and network are still required; finding the command does not mean it is connected. Wait for the terminal to show Local sandbox is ready!, then check the hostname in the interface. Keep specific error messages if the run fails, distinguishing runtime environment issues, download failures, and authentication errors; do not run the entire connection program as administrator just to make the command recognized.