How to Confirm Local Agent Is Connected, Not Just Logged In?
Check the terminal readiness prompt, connection list, and the currently selected execution environment simultaneously.
The Terminal Goes Through Multiple Stages
The Local Agent first authenticates with the service, then connects to the command relay, and only after subscribing is it ready to receive tasks. The terminal showing 'Authenticated' only indicates the authentication stage is complete; you should continue to wait for 'Local sandbox is ready!'. If it gets stuck connecting to the relay or reports errors afterward, handle the terminal errors first. Do not repeatedly send execution tasks to this connection just because the account has been verified.
Verify the Specific Computer in the Interface
Go back to Settings → Remote Control, and check that the hostname in the connection list shows 'Remote Control Connected'. Desktop application connections will show a different status 'Desktop Application Connected', which is a different entry point from the CLI. When multiple machines are online, the green connection indicator only means there is an available connection in the list; you should also confirm in the Agent environment selector that the currently selected machine is the one you want to execute tasks on.
Use a Small Read-Only Task to Complete Verification
You can have the Agent report the current working directory, system type, or the contents of a specified test folder to verify if the results match the target machine. If the button still prompts to check the connection or that the computer is unavailable, wait for status synchronization or use the reconnection option for that connection. A ready connection does not guarantee that the target tools, system permissions, and account quotas all meet requirements; subsequent command errors should be handled according to their own error messages.