Set up once · return from anywhere

Connect a Windows computer for unattended access.

Make one deliberate visit to the target computer. Enable the independent RemoteEndpoints extension, pair your account, and leave LocalEndpoint Connect running. After that, control its Connect AI while you are away.

The complete handoff
  1. At the Windows computer · once Enable + pair Create standing authorization for this account.
  2. From any signed-in device · later See + prompt + follow + stop No person has to remain at the target computer.
First time with a real computer?

Stop at the release gate before downloading.

The current public Connect tester package is not verified for RemoteEndpoints. It is unsigned early access, lacks a production code-signing chain, and has not passed a matching plugin check plus installed end-to-end RemoteEndpoints round trip.

Use the no-install mock unless you are an informed tester who accepts the open signing, clean-machine, and compatibility gates.

Already paired

Sign in to your private computers.

Returning operators can sign in without entering the first-time download path.

Sign in to My computers
First-time setup

Sign in → enable → pair → control remotely

Only Steps 2 and 3 happen at the target computer. Complete them once, confirm the computer appears in My computers, and then leave.

Check install readiness
  1. Sign inWebsite Start here
  2. EnableTarget computer Next
  3. Pair onceConnect + website Then
  4. ControlFrom anywhere Later
  1. Website · now

    Sign in to the controlling account

    Sign-in requiredRequired for private remote access

    An account owns paired computers, private desktop pictures, prompts, results, and revocation controls. Local-only Connect features remain usable without RemoteEndpoints.

  2. Target computer · once

    Enable the independent extension

    Installation plus one-time pairing is the authorization event.

    Installing and enabling the RemoteEndpoints extension is the intentional authorization for unattended remote control. A person is not expected to be at the target computer to approve each prompt.

    The separate reviewed installer or manifest adds the extension; Plugins reports its status but does not contain pairing controls. Then open the top-level Settings → Remote control tab. Its Remote control on this computer switch pauses or resumes new work; it is not the installer.

    Open the exact Connect screen reference
  3. Connect + website · once

    Pair this account once

    Finish Step 1 first

    After signing in, Connect can bind this installation to the correct private account.

    Pairing binds the extension's standing authorization to this account. Connect starts the flow; the browser never searches localhost, scans your network, or invokes Windows APIs. Connect never receives the account password, and the resulting durable device credential stays in Windows Credential Manager.

    Done means the computer appears in My computers.
  4. From anywhere · later

    Use the real authenticated workspace

    • See its newest private desktop picture.
    • Prompt LocalEndpoint Connect AI in ordinary language.
    • Follow private run state, activity, and results.
    • Pause delivery, stop work remotely, or revoke the computer.
Source-backed mock · this walkthrough contacts no app, account, code, credential, or computer Visual reference for Steps 2 and 3

Recognize the Remote control screen before you leave.

Use these pinned captures while completing Enable and Pair once above. Numbered translucent notes explain the screen; the pictured controls cannot be clicked from this website.

Interface evidence, not release proof Reviewed development UI; public-package compatibility remains open.

Captured from an owned installed Connect 0.2.266.0 build. The same controls and copy remain in reviewed 0.2.267.0 source. This does not prove the current public 0.2.242.0 tester contains or can run the integration.

  1. Check the extension in Plugins

    Plugins reports whether the extension is installed and accepted. It does not contain the pairing controls.

  2. Open the top-level Remote control tab

    In Connect, choose Settings → Remote control. This is the exact source-backed destination for account pairing, the computer label, emergency pause, and recovery controls.

  3. Name the computer and choose Pair account

    Use a display-safe name you will recognize in My computers. Connect opens the fixed RemoteEndpoints device page; it never asks for the account password.

  4. Confirm in the browser, then return

    Sign in, confirm the one-time code, return to Connect, and choose I finished pairing. Connect checks once; it does not poll the account.

  5. Leave unattended access on and save

    Remote control on this computer should read Unattended access on. Save plugin settings and confirm the computer appears in My computers before leaving.

Screen 1 · installed, not paired

Find the real pairing surface.

Mock screenshot · no live connection
LocalEndpoint Connect Settings showing the top-level Remote control tab, an unpaired RemoteEndpoints status, the Computer label field, Pair account, and Refresh status.
Swipe the captured screen sideways to inspect it.

The capture contains only the display-safe default label and an unpaired status. Pair account and Refresh status are available; credential recovery and paired-device actions are disabled.

Open the full-size pairing screen
Screen 2 · extension controls

Know what stays enabled after pairing.

Mock screenshot · no live connection
LocalEndpoint Connect Remote control settings showing Unattended access on, capability and outbound HTTPS notices, pause, stop, and revoke guidance, and Save plugin settings.
Swipe the captured screen sideways to inspect it.

The switch is the local pause or resume control, not an installer. The source-backed notices state the signed-in-user capability, outbound-only transport, and separate pause, stop, revoke, disable, and uninstall paths.

Open the full-size control screen
What you authorize

Standing authorization remains active while both authority gates remain on.

No target-side person approves each prompt. The account delivery gate and the enabled extension jointly allow unattended prompts. RemoteEndpoints carries private prompts, pictures, status, results, and controls; Connect AI performs the Windows work.

Account gateDelivery allowedPause it remotely to stop new work.
Computer gateExtension enabledDisable it locally to stop reconnecting.
Control the authorization

Four different controls for four different outcomes.

Stopping a run does not undo completed effects or remove future authority. Choose the control that matches what you mean.

Current workStop run

Requests cooperative cancellation at the next safe boundary.

New promptsPause delivery

Closes the account gate while preserving the pairing.

This computerDisable extension

Closes the target-computer gate and stops reconnecting.

Pairing + retained picturesRevoke computer

Invalidates its credential, deletes retained pictures, and requires pairing again.

Uninstall and emergency-stop behavior

Uninstalling removes the independent remote-control capability from Connect. Emergency stop must cancel active work and stop reconnecting when the owner-side control is disabled. Neither can reverse an effect that already completed.

Understand the computer capabilities this authorization can expose
Desktop Computer access Connect AI can observe the signed-in desktop and use pointer and keyboard input.
Programs Computer access Connect AI can open and operate programs available to the signed-in Windows account.
Files Sensitive data Programs operated by Connect may expose, create, change, or delete files available to that Windows account.
Network External effects Connect can use browsers and network access available on the target computer.

This is powerful access. A remote operator can direct the Connect AI to use the programs, network, and desktop available to the signed-in Windows account. Protect the RemoteEndpoints account and enable the extension only on a computer you intend to control remotely. Exact behavior depends on the installed Connect build, the signed-in Windows account, and the current desktop state.