How it works

Set up once. Control the computer while you are away.

RemoteEndpoints authenticates the remote operator and carries prompts, control messages, private desktop pictures, and status. The enabled RemoteEndpoints extension lets LocalEndpoint Connect AI perform the work on the target computer; the website itself does not invoke Windows APIs.

Real-device readiness

Current public Connect download is not yet verified for RemoteEndpoints.

The no-install mock is available now. A matching RemoteEndpoints plugin check and an installed production end-to-end round trip remain open.

Review package, signing, and compatibility facts
Set up once

Prepare the target computer

  1. Install ConnectInstall LocalEndpoint Connect on the Windows computer you own or administer.
  2. Enable the independent extensionVerify the RemoteEndpoints extension source, install it, and intentionally enable unattended control.
  3. Pair the accountUse the short device-code flow once so Connect receives a durable device credential without your password.
  4. Leave Connect runningKeep the intended Windows account signed in and its desktop unlocked while you are away.

After one-time account pairing, Remote control is active while the RemoteEndpoints extension is enabled in LocalEndpoint Connect and account delivery is not paused. Pause delivery or disable the extension to suspend unattended access; revoke the computer to end the pairing.

For each request

See, prompt, follow, and stop

  1. Choose the computerSelect a paired Connect computer from the private workspace.
  2. See its desktopReview the newest private desktop picture and its capture time.
  3. Prompt Connect AIDescribe the outcome in ordinary language; no person is expected at the target computer.
  4. Follow or stop the workWatch private run state and activity, then request remote cancellation when needed.
  5. Pause or revoke accessPause account delivery, disable the extension locally, or revoke the durable pairing.
Authority map

The website carries the private connection; Connect operates Windows.

  1. Operatorselects a paired computer and prompts Connect AI
  2. Browsersends the authenticated private prompt
  3. RemoteEndpointsqueues and leases it to the paired device
  4. Enabled extensionis the persistent setup authorization boundary
  5. LocalEndpoint Connect AIobserves, plans, and uses computer capabilities
  6. Windows desktopruns under the signed-in user's permissions
Return path: LocalEndpoint Connect returns private desktop pictures, activity, run state, and results. None of that is published on a public status page.

Browser

Shows the authenticated control surface and private pictures; it does not scan localhost or directly call Windows APIs.

RemoteEndpoints

Authenticates operators and carries encrypted web traffic for prompts, pictures, state, stop signals, and revocation.

LocalEndpoint Connect

Runs on the computer, receives leased work, captures the desktop, and gives its AI the enabled local capabilities.

Exact interface · synthetic data

Preview the real operator workspace without an account or computer.

The Demo uses the same console renderer as the authenticated workspace with fixed mock data. Mock badges remain visible, every interaction is discarded, and no production API or computer is contacted.

Technical lifecycle and trust boundaries

RemoteEndpoints authenticates the remote operator and carries prompts, control messages, private desktop pictures, and status. The enabled RemoteEndpoints extension lets LocalEndpoint Connect AI perform the work on the target computer; the website itself does not invoke Windows APIs.

  1. Operator / account Sign in The operator authenticates through the shared account system.
  2. Local owner Enable the extension Installing and enabling the independent extension authorizes unattended remote control.
  3. LocalEndpoint Connect Pair once Connect completes device authorization and stores a durable, revocable credential.
  4. LocalEndpoint Connect Publish pictures Connect uploads bounded desktop pictures into account-private no-store storage.
  5. RemoteEndpoints Carry private prompts The service authenticates the operator and leases prompts to the paired Connect installation.
  6. LocalEndpoint Connect AI Observe, plan, and work Connect AI uses enabled computer capabilities under the signed-in Windows account.
  7. RemoteEndpoints / browser Return private state Pictures, activity, results, and stop state remain in the authenticated workspace.
  8. Owner or operator End access Pause delivery, disable the extension, or revoke the computer and its credential.
Historical implementation evidence (version-specific)

LocalEndpoint Connect accepts authenticated prompts from an enabled RemoteEndpoints extension, plans work with its local AI, and uses its Windows desktop-control lanes to operate programs, browser sessions, pointer input, keyboard input, and the network available to the signed-in Windows account. Exact capabilities depend on the installed Connect build and Windows session state.

Evidence boundary: This first-party record is historical and version-specific. It is not third-party certification and does not establish compatibility for a currently offered package.

Machine-readable contract

Developers and automated tools should read the manifest, OpenAPI document, public route index, and llms.txt before making assumptions about this service.