Home Troubleshooting
đź”§

Troubleshooting

Fix common issues in SoLo Support.
By Jeremy Smith
• 2 articles

Troubleshooting SoLo Support

Start here Retry the action once, confirm SoLo Support is current, and review any permission or connection message shown by the app. Checking for native app updates SoLo Support 0.1.16 adds startup update notices and Check for Updates controls. If you installed an earlier version, download and install the current app once from the official downloads page. Restarting an older version cannot add the new checker. - Windows, macOS and Linux technician apps: use Software Updates → Check for Updates in the native menu, or Settings → Software updates. - Desktop Host Agents: open Settings → Software Updates. The technician app and the Host Agent on a remote computer are separate installations; update each one. - Android technician: use Software updates on the sign-in screen or in Settings. Android Host Agent has a Software Updates panel. For an older Host Agent, install the official Android Host Agent APK once. Android controls permission to install the downloaded APK. - Quick Support: use Check for Updates. If an update exists, finish the session and ask your technician for a fresh Quick Support link. - iOS technician: use Software Updates on the sign-in screen or under Profile. Signed iOS distribution is not currently available; the app reports when its release channel is unavailable. Checks do not install software automatically. Follow the offered installer, finish installation and reopen the app. A connection error means the app could not check; it does not mean the installed version is current. The current macOS release uses the Open Anyway installation flow. After downloading from the official SoLo Support site and attempting to open the app, use macOS System Settings → Privacy & Security → Open Anyway if Gatekeeper blocks it. Do not disable Gatekeeper globally. For the macOS Host Agent, replace the app in Applications with the downloaded version and reopen it. Identifying and installing the Host Agent Starting with 0.1.17, Host Agents use a shield icon with a small monitor badge. The main app, technician apps, and Quick Support keep their original icons. Update each installation separately to receive its matching release. For a new Host Agent installation that enrolls automatically, download from your organization’s SoLo Support page. That download supplies a one-time enrollment token. The generic public downloads page does not select an organization and does not embed a token. If a fresh Linux installation reports Enrollment token is required, use a fresh Host Agent download from your organization page instead. Do not post enrollment tokens in support messages. An update should retain the device’s existing enrollment. If an already enrolled installation unexpectedly asks for a token, contact your technician before removing or resetting its configuration. Copying text and images between computers Version 0.1.18 adds image clipboard transfer in both directions for Windows, macOS and supported Linux (Xorg) desktops. Update both the desktop technician app and the remote Host Agent, then reconnect. Click the remote screen before using your normal Copy, Cut or Paste commands. Copy the image itself, such as Copy Image in an application or a screenshot, then paste into an app that accepts images. Copying an image file or folder in a file manager is a file-transfer operation and is not supported by clipboard sync. Plain text, including multiple lines, is also supported. In a browser, allow clipboard access if asked. If the browser requires a fresh click after receiving an image, choose Copy image in the session notice, then paste into your local application. The desktop technician app uses its native clipboard. Images above 16 MiB after PNG conversion, 16 megapixels, or 8192 pixels in either dimension are rejected with a message. Interrupted or rejected image transfers do not paste an older clipboard image. Android and iOS image clipboard transfer is not included in this desktop release. Still need help? Open the in-app support experience and describe the step that failed. Do not send passwords, private files, or other sensitive information.

Last updated on Sep 07, 2026

Personal remote access: sign-in and connection help

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 shortly. Reconnect required means the saved sign-in is invalid; reconnect from the AI service as described below. Neither message means 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. MCP computers show Reconnect required or Unavailable computer A saved AI connection can lose its sign-in while its computer permissions remain listed. This does not mean the computers are offline. Signing into the MCP webpage alone does not replace the saved connection inside ChatGPT, Claude or another AI service. 1. Open the AI service’s settings for apps or connectors and choose SoLoSupport. 2. Reconnect the service. If only Disconnect or Remove is offered, remove that connection and add SoLoSupport again. 3. Complete the fresh SoLoSupport sign-in, choose the intended organization and approve the computers this connection may access. 4. Return to the MCP page and select Refresh status. In a fresh chat, ask Show my authorized computers in SoLoSupport. Reconnect only affected connections. A temporary Status unavailable message calls for a retry; an Offline device needs its Host Agent brought online. Keep unattended access and Allow AI access enabled on the intended computers. The central MCP address lists computers approved for AI connections. Your organization console lists the full managed inventory. Each AI connection is restricted to the selected organization and computers. Connecting from another browser After signing in through a new browser, or choosing to sign in again, select the intended organization and approve the computers for that connection. A previous approval in another browser does not authorize the new browser session. Returning through a browser that already has valid computer approval can reuse that approval. If a connection fails before you see Choose computers, restart it from the AI service after checking the service status. Do not change enrollment, share tokens or grant access to a different organization to work around a connection error.

Last updated on Oct 22, 2026