App not installed
Review the first-party package, current signing and Windows-warning status, and published SHA-256 before installing LocalEndpoint Connect. The website cannot inspect whether the app is present.
Review the tester package factsRemoteEndpoints connection troubleshooting
Use these recovery paths without pasting secrets or asking the browser to inspect the local machine.
Quick recovery
Choose the first symptom you see
Each link moves to a stable recovery section. Start with the smallest safe step, verify picture and heartbeat timestamps, and revoke access if the device or account state is unexpected.
Detailed checks
Computer, picture, prompt, and stop recovery
RemoteEndpoints extension is not installed
Install the independent RemoteEndpoints extension from the reviewed LocalEndpoint Connect plugin source, confirm its installed and accepted identity in Settings > Plugins, and then open the top-level Settings > Remote control tab to pair it on a computer you intend to control remotely. Installing Connect alone does not authorize RemoteEndpoints access.
Review extension installationRemoteEndpoints extension is installed but disabled
In LocalEndpoint Connect, use Settings > Plugins to confirm the independent RemoteEndpoints extension identity and that its status is disabled. Re-enable it only on a computer you intend to control remotely, then use the top-level Settings > Remote control tab to resume its local authorization gate. Installation plus one-time account and device pairing creates standing unattended authorization; pausing does not uninstall the extension.
Review extension setupWindows did not open the one-time setup handoff
Open LocalEndpoint Connect directly, return to the top-level Settings > Remote control tab, and start Pair account there. The custom-protocol handoff is only a setup convenience; unattended control uses the durable device credential created after pairing, not a browser protocol launch for every prompt.
Review the setup handoffPairing code expired
Start Pair account again from the top-level Settings > Remote control tab in Connect. The short device code is intentionally single-use and short-lived; completing pairing creates a durable device credential for later unattended reconnects.
Review account pairingComputer appears offline
Confirm the target computer has power, its intended Windows account is signed in with an unlocked desktop, Connect is running, and outbound HTTPS is available. No person must stay there after those conditions are established.
Open My computersDesktop picture is stale or missing
Check the capture time first. A stale picture can mean Connect is offline, the extension is disabled, the desktop is locked, capture failed, or a network upload was blocked. Never assume an old picture represents the current desktop.
Refresh the private workspacePrompt is queued but not starting
Confirm the latest Connect heartbeat, that both the extension and account delivery gates are enabled, and that no earlier run still owns a work lease. Do not create repeated duplicate prompts while diagnosing the queue.
Inspect private run stateRemote stop is pending
Stop is cooperative: Connect AI must receive the signal and reach its next safe cancellation boundary. If the computer is offline, the signal remains visible until Connect checks in. Revoke the computer for immediate server-side credential invalidation.
Review stop and revoke behaviorConnect AI reported a failure
Read the private result and activity without sharing sensitive details publicly. The installed Connect build may lack a required capability, the target app may have changed, or Windows may be locked or showing a secure desktop that interactive automation cannot control.
Review capability boundariesRemoteEndpoints sign-in expired
Sign in again with the account that owns the paired computer. Account-session cookies and durable device credentials are never placed in public status pages or recovery URLs.
Sign in againProxy or firewall block
LocalEndpoint Connect needs outbound HTTPS access to pair, renew heartbeats, lease prompts, upload private desktop pictures, and return private state. No inbound port is required. Follow the computer owner's network policy before changing proxy or firewall rules.
Review the public service contractRedact private computer data before asking for help
You may share the Connect version, sanitized error wording, and relevant UTC timestamps. Do not share account or device tokens, command claim tokens, credentials, prompts, results, desktop pictures, active application names, file paths, device identifiers, or private logs.