Alsalibi ConnectLast updated:
Installation, connection & common errors
Official help for Alsalibi Connect. These prepared answers cover the current clients and their limits. For a new problem, ask the community or contact private support.
How do I install on Windows?
Sign in on this website, select Add device, then download the Windows setup for your account. Extract the whole ZIP and run its Run me.cmd file. Keep the extracted files together. Complete linking on this computer. Windows 2.6.18-rc2 is a public beta; installation on every Windows configuration has not been verified.
#How do I update an existing Windows installation?
On the same Windows computer, open a terminal and run: npx --yes https://alsalibiconnect.com/desktop upgrade . The public beta preserves the existing pairing and the matching legacy desktop helper. Do not remove the device or create a second installation. If MULTIPLE_INSTALLATIONS_FOUND appears, post the error here without keys or pairing codes.
#Why does my computer appear offline?
Check that the computer is awake, online and running Alsalibi Connect. Refresh My devices after a short wait. A website login alone does not start the computer agent. If the device was paused, enable it again. Do not delete the paired device as the first troubleshooting step.
#What do AGENT_BUSY and timeout errors mean?
AGENT_BUSY means earlier work is still running. Let it finish before sending more commands. A timeout does not prove that an operation never ran; check its result before repeating a file edit or installation. Include the error code, OS and agent version in a support question. Long work may need to be split into smaller steps.
#How do I enable screen and keyboard access on a Mac?
On the target Mac, open System Settings → Privacy & Security. Allow Screen Recording for viewing and Accessibility for input for the installed Alsalibi app. Approve macOS prompts yourself, and quit/reopen the app if macOS requests it. Website consent and macOS permissions are separate.
#Why do screen or mouse controls fail on Windows?
Unlock Windows and sign in to the intended desktop. Screen and input need the matching desktop helper in that interactive session. Terminal and file access can work while screen access is unavailable. Keep the helper supplied with your installation; do not mix old and new helper files.
#What works on Linux and Wayland?
Terminal, files and processes are supported by the Linux agent. This client does not implement native Wayland screen/input control. X11 viewing requires xdpyinfo and scrot; keyboard/mouse require xdpyinfo and xdotool. A headless computer has no physical desktop to show.
#How do I connect ChatGPT?
Use the ChatGPT connection page at /chatgpt and sign in to the same Alsalibi account that owns the paired computer. Approve the requested account connection in ChatGPT. Account login, paired-device state and OS permissions are separate. If authentication expires, reconnect the account; do not publish OAuth tokens.
#What should I avoid posting publicly?
Questions and replies here are public. Never post passwords, pairing secrets, device keys, OAuth tokens or private screenshots. Share only the error code, OS/version and a description with sensitive data removed. Use private support at /support for account-specific details. You can delete your own public posts.
#Will the app reconnect after restart?
Check the startup option for this computer in My devices. Windows startup for this client normally runs when the configured user signs in; screen control requires an unlocked interactive session. Verify the behavior on your own machine. A successful connection once does not prove that startup is configured.
#How do I recover my account?
Use Forgot password on the sign-in page, or contact private support at /support. Use the same sign-in method as before; a Google account may use Google sign-in rather than a separate local password. Do not post recovery codes or verification messages in the community.
#How do I report a Windows beta issue or return to the previous version?
Use Ask the community, select Errors, and include Windows version, agent version, error code and what you expected. The download card links to the previous 2.6.16 package. Keep the same installation and saved pairing; do not delete keys to downgrade. If you are unsure, ask here before replacing files.
#