Unattended remote control FAQ
Choose a task to find direct answers about standing authorization, account risk, pairing, privacy, release readiness, and multi-agent swarms.
Find answers by task
Jump directly to the decision, setup, privacy, evidence, or advanced-agent answer you need.
Before you install or pair
Read these four truths before choosing the current tester path or pairing a computer.
Is a verified RemoteEndpoints-ready download available?
No. The current public Connect tester package has an outer setup EXE that is not Authenticode-signed, and it has not passed a matching RemoteEndpoints plugin check plus an installed production round trip. Use the safe mock unless you knowingly accept those open gates.
What if my account is compromised?
Account access may become access to every computer paired to that account. Passkeys and multi-factor authentication are not implemented yet. Use a unique password, protect the email account used for verification, sign out on shared devices, and revoke anything unfamiliar.
Will someone approve each remote prompt?
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. One-time pairing binds that standing authorization to the owning account.
How do I suspend or end remote control?
Remote Stop requests cooperative cancellation of the active run and does not block later prompts. Pause closes the account delivery gate while preserving pairing. Disabling or uninstalling closes the target-computer extension gate. Revoke invalidates the server-side durable credential, ends the pairing, terminates queued state, signals Connect to stop, deletes retained active pictures, and requires fresh pairing. None of these controls can reverse an effect that already completed, and an offline computer may not receive a stop signal immediately.
Understand remote control
Understand what the website carries, what Connect performs, and where Windows boundaries still apply.
Is this a remote-control product?
Yes. RemoteEndpoints is the account-authenticated remote-control companion for LocalEndpoint Connect. The website carries private prompts, pictures, state, results, and control messages; the installed Connect AI performs the Windows work.
What can I do remotely?
You can see private desktop pictures, prompt Connect AI, follow private run state and results, request stop, pause delivery, and revoke a selected computer. Exact computer actions depend on the installed Connect build, its available tools, the signed-in Windows account, and the current desktop state.
What is LocalEndpoint Connect?
LocalEndpoint Connect is the installed Windows app. Its enabled RemoteEndpoints extension captures the desktop, polls outbound for authenticated prompt leases and control messages, runs Connect AI locally with the signed-in Windows account's available desktop, programs, files, and network, and returns private state and results.
Can this release perform every desktop action remotely?
No. Connect has broad signed-in-user authority, but exact behavior still depends on the installed tools and AI, Windows permissions, application state, locked or secure desktops, network conditions, and failures. A completed status means Connect reported completion; it is not a guarantee that every requested real-world effect occurred.
Does it work at the Windows sign-in or UAC screen?
Not with the current verified interactive-desktop lanes. Keep the intended Windows account signed in and its desktop unlocked. Windows sign-in, UAC, and other secure desktops are outside the verified capability claim.
Does the browser scan localhost?
No. The public website does not probe localhost or private networks, open an inbound tunnel, read local files directly, or invoke Windows APIs. Connect uses outbound authenticated requests for the remote-control path.
Pair and reconnect
Pair once for unattended access, then understand when fresh pairing is required.
How does pairing work?
The implemented persistent protocol starts a short device-code flow in Connect. After the owning user confirms that code in a signed-in browser, Connect receives a durable, revocable device credential—not the website password. The matching public package has not yet passed an installed production round trip.
Does pairing survive restarts?
The persistent protocol and reviewed Connect source are designed to keep the durable device credential through normal browser and Connect restarts. Pair again after revocation, credential loss, or deliberate fresh authorization. This source behavior is not proof that the current public package completes the production round trip.
Does local-only use require an account?
No. LocalEndpoint Connect's local features remain independent of a RemoteEndpoints account, website session, or remote-control pairing. An account is required only for the account-based RemoteEndpoints path.
How does this relate to LocalEndpoints.com?
LocalEndpoints.com is the first-party release and documentation authority for the local app. RemoteEndpoints.com is the separate account-based companion that carries private unattended-control data for an intentionally enabled and paired Connect extension.
Protect private data and your account
Public pages stay synthetic; private computer data remains account-bound.
What can public viewers see?
No live computer data. Public pages contain product documentation and clearly labeled synthetic demo data. Desktop pictures, prompts, results, activity, and device identity require the owning account.
What requires private operator authority?
Paired-computer lists, desktop pictures, prompts, results, activity, command state, stop, pause, resume, credential rotation, and revocation require the owning account or the correctly scoped device credential. Public indexing grants no runtime authority.
Are desktop pictures stored forever?
On the implemented active server path, desktop pictures are account-private, validated, served with no-store headers, limited by count and age, and deleted from retained active storage on revocation. This does not claim immediate deletion from every backup or copy outside that verified path.
Evaluate the demo and release evidence
Separate the safe mock and first-party evidence from a verified public release claim.
Is the demo connected to a real computer?
No. The demo uses clearly marked synthetic data, requires no account, contacts no computer, and does not create production requests. Text entered into its mock form is validated and immediately discarded.
Is this documentation an independent certification?
No. It is first-party product documentation, not an independent audit, certification, security assessment, or guarantee.
What does historical implementation evidence prove?
Only the named, version-specific scope. Historical server, source, browser, or deployment evidence does not prove that the current public Connect package is compatible or that an installed production round trip works unless that exact package is retested.
Is this general production?
No current evidence supports a general-availability claim. Treat the public package and integration as an informed-tester path until a matching signed package and installed production round trip pass the stated gates.
Run multiple agents safely
Preserve parallel agents while preventing name and memory-identity collisions.
Can I run multiple Connect agents as a swarm?
Yes. Powerful systems may run multiple independent Connect instances concurrently. Each active MemoryEndpoints agent must use a distinct normalized name and a distinct immutable .uai memory identity or true branch. Reviewed Connect source enforces the current-Windows-user boundary; hosted cross-computer name and memory leases plus fencing remain unimplemented.
Can two agents use the same .uai memory instance at once?
No. One immutable .uai identity may have one active agent attachment. Copying, moving, or renaming the file preserves that identity and is not a branch. By contract, a true branch must receive a new identity and record its lineage before it may run concurrently with its source. Global hosted enforcement remains a MemoryEndpoints.com requirement.