Agent Connected but Running Tool Shows 'command not found' - What to Do?
Check the tool installation, path, and execution user on the target host; do not mistake tool errors for connection errors.
Confirm Execution Occurs on the Intended Machine
First verify the environment selector, then have the Agent report the actual system and working directory. A tool existing on your browser computer or in the cloud does not mean it is installed on the selected remote host. A command returning 'not found' usually indicates the execution chain has returned a result; repeatedly reconnecting or resetting tokens may not help. You should first identify which executable is missing.
Verify Installation and Startup Environment
Confirm whether the tool is installed on the target machine and whether the user who started Desktop or CLI can access it. Different shells, user paths, or execution entries may see different programs; do not directly copy command syntax from another platform. First, check the executable location and version in read-only mode to avoid running operations that modify the system or access many targets just to confirm the tool's existence.
Decide to Install, Substitute, or Change Environment
If the tool is indeed missing, you can choose an installed alternative, a machine with the required dependencies, or explicitly authorize installing the needed tool. Before installation, check the source, permissions, and impact scope; connection applications do not guarantee all security tools are pre-installed, nor should all missing issues be assumed solvable by administrator privileges. After meeting the conditions, retry small steps before continuing the original task to avoid repeating completed parts.