Should I Use the Desktop Application or the Command Line Local Agent?
Choose the connection entry point based on usage method and understand the shared local execution boundaries of both.
Desktop Is Suitable for Direct Use of Local Workflows
Hackcat Desktop provides a chat interface and attempts to connect to the local execution environment after login. It also supports desktop features such as binding project directories via the system file picker. If you want to browse tasks, select directories, and execute tools on your own computer, you can start by using the desktop application; the installer and development environment serve different purposes, and normal use does not require compiling the application first.
CLI Is Suitable for Accessing Target Machines from the Terminal
The Local Agent runs in the terminal of the target computer. You can connect by copying the full connection command from Settings → Remote Control. It requires Node.js and depends on the process running this program to remain available; a successful desktop connection does not guarantee that the CLI on another machine is also connected. Both methods have their own execution entry points and recovery paths, so specify which one you are using when troubleshooting.
Neither Is an Offline Model or Isolated Container
Both the desktop and CLI use the target host’s files, network, and tools, executing commands with the permissions of the user who started the program, without container isolation. A successful connection does not remove account model, quota, or attachment restrictions. Regardless of which you choose, first verify the target machine, working directory, and approval method; if you need content from another machine, connect to that machine and confirm the selected environment before sending tasks.