Why Does Desktop Login Open a Browser, and How to Return to the App?
Understand browser authentication and desktop redirection, and confirm whether the local connection is ready after login.
Initiate from the Desktop App You Need to Use
After selecting login within Hackcat Desktop, the system browser usually opens to complete authentication. This is part of the desktop login process and does not mean you must switch to the web to perform tasks. Please use the authentication page initiated by the current app and verify the login account; if the browser already has another account session, confirm your identity before completing to avoid losing connections under the same account later.
Return to the App Using the Completion Page
After successful authentication, the page will attempt to open Hackcat Desktop; if the browser does not automatically redirect back, click Open Hackcat and follow system prompts to open the app. Only use this completion page generated by this login; do not bookmark or share the full URL containing authentication information with others. If prompted that the session has expired or the request was not initiated from this app, return to the desktop and restart login instead of refreshing the old link.
Verify Execution After Returning to the App
Successfully returning to the chat interface does not mean the local environment is immediately ready to execute. The desktop will establish its own command connection, which can be checked under Settings → Remote Control by verifying “Desktop App Connected,” then selecting the Agent and the corresponding computer. If web login succeeds but the desktop remains unlogged, troubleshoot according to desktop redirection; if logged in but the computer is unavailable, check the connection without immediately resetting the Local Agent token.