Which Programs Need to Stay Running When Using Local Agent?
Distinguish between chat pages, desktop applications, and CLI processes to avoid mistaking leaving the interface for task completion.
Keep the Actual Execution Endpoint Available
If you select Desktop, Hackcat Desktop on the target machine must remain running and connected to the internet; if you select Local Agent, the terminal process running the client must remain available. The chat page in the browser only displays tasks and cannot receive local commands for desktop applications or CLI that have been closed. When chatting from another machine, you must also ensure the target computer is online.
Leaving the Page Is Different from Stopping a Task
Switching away from the chat page, brief network interruptions, or output stopping refresh cannot be used to judge that a task has been canceled. The task may still be running, waiting to resume, or may have failed. You should open the original task to check the latest status. To end execution, use the stop operation provided on the page and verify success; do not just close the interface and immediately repeat the same file modification in a new chat.
Restore Connection Before Sleep or Exit
Computer sleep, network changes, and client exits can all affect the local connection. After recovery, first wait for the desktop to automatically reconnect or restart the CLI, then verify the environment selector and original task output. The CLI also has an automatic exit mechanism after about one hour of no command activity, so the terminal showing a successful connection once does not mean it will stay online permanently. It is best to perform a clear, small-scale check again before starting important tasks.