Is Global Installation Required for Local Agent, and What Are the Differences with Temporary Running?
The standard process uses the startup command generated by the settings; global installation is an optional path.
Regular Connection Does Not Require Prior Global Installation
The command generated under Settings → Remote Control prepares and runs the client. You can directly use this complete command to connect to the target machine. The prerequisite is that the target computer has a compatible Node environment and can access the client package. For users who only need to establish a connection, there is no need to clone the source code first, run builds, or manually assemble tokens; also, do not blindly copy old installation commands from unknown sources.
Global Installation Does Not Eliminate Connection Parameters
The official client documentation provides an optional global installation method. After completing installation according to the official instructions, you can use the local hackcat-local command, but you still need to keep the identity and backend parameters generated by the current settings. Global installation only changes where the client starts from; it does not permanently save account connections in a no-verification state, nor does it allow offline machines to automatically restore online status.
When Encountering Differences, Prioritize Returning to the Current Process
If the globally installed version fails to start, the command is not found, or old parameters become invalid, first check the errors and try the standard connection method provided by the current settings. Do not start many different versions simultaneously to try your luck. Version, Node environment, and running user can all affect behavior. Confirm the terminal shows a ready prompt before selecting the machine, and press Ctrl+C to end use; regardless of installation method, the command still acts directly on the host without container isolation.