Why does Agent still show the computer as unavailable even though the desktop application is open or logged in?
Login, connection readiness, and task permissions are independent conditions. First, restore the currently selected computer.
Opening the application does not mean the connection is ready
The desktop will attempt to establish a local execution connection only after logging in. During this process, it may display connecting, reconnecting, or unavailable. The input area restricts sending when the selected computer is not ready to avoid starting tasks in an unavailable environment. First, check Settings → Remote Control for the desktop status, and confirm that the environment selector points to the current computer, not an offline old connection or another machine.
Use the desktop's own recovery entry
If it is still connecting, keep the network and application running and wait for the status to change; if it clearly fails, use 'Reconnect' or the desktop connection retry entry. The desktop will automatically handle some temporary faults but does not retry indefinitely. If you have selected the desktop of another computer, you must open the application and log in with the same account on that machine; starting the local CLI will not automatically fix that remote desktop connection.
Check other restrictions after readiness
After the connection is restored, verify the Agent mode, account available environments, and task approvals. File upload permissions, model quotas, or missing local tools can independently block certain operations and should not all be attributed to connection failure. First, send a small scope read-only verification to confirm the actual working directory. If it is still unavailable, record the connection status, selected computer, and error messages to avoid repeatedly trying by resetting all tokens.