Choose a different Google account

On the web sign-in screen or the Codex connection screen, choose Use another Google account. Google will ask you to choose an account or use another account. Select the personal identity you used to enroll your computers. Your business identity still opens its business workspace; selecting an account does not transfer computers or convert your account. If the browser prevents the redirect, retry the Google button after it becomes available again, or reload the sign-in page. Enter credentials only in the browser.

I am being asked for a company workspace

For personal remote access, open remote.solosupport.app. The business console also offers a Personal remote access link. Existing business accounts return to their company workspace; do not create another account to bypass its permissions.

My computers could not load

Try again when your connection and the support service are available. A temporary outage keeps your saved sign-in. If the issue continues, contact support through the help center.

My computer is offline

Open the Host Agent on the remote computer and check its connection. Verify that enrollment was approved, the computer is powered on, and the Host Agent can reach the support service. Downloading or installing the technician viewer does not enroll the remote computer.

An old session is stuck

From My computers or Computer details, choose End open sessions, confirm, then start a new connection. This action can interrupt a live session. It is separate from removing the computer.

I installed the Host Agent but My computers is empty

Download a fresh Host Agent from My computers and install it within 30 minutes. An older installation may still belong to a different account. The corrected Windows and Linux installers add your personal account while preserving existing access. If Windows asks to add access, check the account name and approve it. If enrollment fails or the installer is expired, download a new copy and try again.

On Linux, an “already installed” message does not confirm that the new account was enrolled. From the folder containing your fresh download, run sudo apt install --reinstall ./SoLoHostAgent-Linux-v0.1.29.deb and approve the operating-system password prompt. Keep the installer private. Avoid uninstalling or purging as a workaround because that removes saved access. Refresh My computers after installation finishes.

Connecting an AI agent

First enroll your computer and approve Allow AI access in its details. Start the SoLoSupport connection from Codex, sign in with that same identity if asked, select computers and choose Allow selected computers. Google sign-in proceeds to the next step automatically. The device approval and computer selection are permissions, not additional password logins.

The product dashboard and agent connection currently keep separate browser sessions, so first setup may ask you to sign in to each. A saved connection refreshes credentials without another Google or password prompt during normal use. If the chooser is empty, complete enrollment and AI opt-in in My computers (business accounts: your workspace), return to the chooser and select Refresh computer list. Change account shows the sign-in screen; Use another Google account opens Google’s chooser. Do not re-run connect or clear saved credentials before every desktop session.

A revoked or expired connection needs a fresh connection started from Codex. An old Google callback cannot be replayed. Manage access at Connected agents; disabling device AI access is a separate control. Windows, Linux and macOS hosts are eligible subject to their local capture/input permissions and organization policies.

Choose and manage AI computers

The connection chooser offers Add a computer, Manage computers and Refresh computer list. Add and Manage open computer management, which routes personal accounts to My computers and organization accounts to their workspace Devices page. The dashboard uses a separate sign-in from the agent connection; use the same SoLoSupport account. For an organization, an owner or administrator manages device enrollment and permissions in that workspace. Enroll the Host Agent against the intended customer organization, enable unattended access and Allow AI access, then return to Connected agents and select Edit computers. Organization membership and device permissions still limit what each agent can access; switching accounts does not transfer computer ownership. Reuse the enrolled Host Agent. Enable Allow AI access, then explicitly select the computer. In Connected agents → Edit computers, change the connection selection without relinking Codex. Enrollment alone does not grant AI access. A saved computer can be offline while its Host Agent is stopped or disconnected; bring that account/workspace connection online, then refresh. Desktop Commander connectivity is separate from SoLoSupport.

An AI screenshot expired

A screenshot permits one action for up to 30 seconds, including model and approval time. If it expires, obtain a new screenshot before acting, then verify the result with another screenshot. Consent, permissions and recording requirements still apply to every action.

Check an agent’s computer status

Open Connected agents to see each selected computer’s online/offline status and any setup requirements. Authorized means the saved permission is active; it does not mean the AI application is running. Status refreshes every 30 seconds while the page is visible. Choose Refresh status to check again or search by agent/computer name. Status unavailable means the check failed; retry or sign in again rather than assuming the computer is offline. Revoke access asks for confirmation, stops that agent’s sessions and removes its access. Reconnect from the AI service to authorize it again.

Installed in Codex, but unavailable in this chat

Installation, account authorization and tool availability are separate. An online computer or a saved connection does not confirm that the current chat has loaded SoLoSupport. Ask Show my authorized computers in SoLoSupport in the chat where you want to work. A successful computer list verifies access there; an empty list is different from missing tools.

A private hosted SoLoSupport connection passed computer listing and screenshot/disconnect/reconnect checks in ChatGPT and managed cloud Work on October 10, 2026. The desktop-local installation and the hosted account connection are separate. Public plugin store approval remains pending.

For private hosted setup, open Plugins → Add custom MCP server, enter https://mcp.solosupport.app/mcp and choose OAuth. Sign in with the identity that can access your computers, select the intended computers and choose Allow selected computers. Use Try in chat, or select SoLoSupport from Plugins in cloud Work, then check the computer list in a fresh chat. Reuse your enrolled Host Agent; no separate AI agent installation is needed.

If tools are missing, check that the plugin is enabled for the intended surface and retry in a fresh chat. Inspect initialization errors; restart the local app if needed. Preserve working authorizations; repeated sign-in cannot load an unavailable plugin. Start a fresh connection for expired or revoked authorization. Never paste credentials into chat or change computer enrollment to recover missing tools.

For a harmless acceptance check, close sensitive windows, ask the agent to connect to your selected computer, inspect one screenshot without clicking or typing, and disconnect. Verify the session ended. Device consent, account boundaries and recording policy still apply.

AI connection expires after ten minutes

A hosted AI connection needs permission to renew its sign-in automatically (offline_access) as well as desktop access (mcp:tools). If this renewal permission was omitted during OAuth setup, the first connection can work and then ask for sign-in again when its ten-minute access token expires. Fix the plugin’s OAuth scope configuration before reconnecting your intended account once. Reconnecting without that correction repeats the problem.

After reconnecting, verify the selected computer list and a screenshot again after the original token has expired. The organization account, device AI permissions and selected computers still apply. Never paste tokens into chat, extend token lifetimes or disable revocation to avoid sign-in.