Optional extension trust sheet

Add RemoteEndpoints to LocalEndpoint Connect

Control your PC while nobody is at it. Installing, enabling, and pairing the independent RemoteEndpoints extension once establishes standing unattended authority; later prompts require zero target-side approvals. Version 0.2.242.0 is not yet verified for this contract.

Review the 4-step setup See evidence limits Compare extensions

Unattended authority model

Pair once. Run unattended. No target-side approval per prompt.

Core local chat, models, memory, and ordinary protected local actions need no RemoteEndpoints account or extension. Installing, enabling, and pairing this independent extension is the owner's deliberate act that authorizes later remote work while nobody is at the PC.

New Connect package required
Independent extension
One-time pairing
0 target approvals per prompt

Adds: Unattended remote control through the LocalEndpoint Connect AI while the target computer has no human present.
Works without it: All core local use remains account-free after the app and model files are present.
Execution path: The authenticated browser carries private intent. RemoteEndpoints relays it. LocalEndpoint Connect and its local AI perform Windows work; the browser does not call Windows APIs.
Private workflow data: Prompts, desktop pictures, progress, and results belong to the authenticated private channel, never to public pages or evidence.
Credentials: Website authentication uses its dedicated sign-in flow. LocalEndpoint Connect does not collect or store the website password.
Authority: Install alone is not enough. Install, enable, and one-time pair together establish standing unattended authority. Exact session, instruction, target, expiry, capability, and revocation state still bind work, but no human at the target approves each prompt.

Four deliberate steps

Set up standing remote authority in four deliberate steps.

Nothing on this public LocalEndpoints page grants authority. The owner's install, local enablement, and one-time pairing inside the independent extension do.

01
Wait for the qualified Connect release
Do not use public version 0.2.242.0 to evaluate unattended control. Confirm the future release explicitly says RemoteEndpoints compatibility passed.
Check release readiness
02
Install the independent extension
Save the accepted template as remoteendpoints.com.plugin.json, refresh Settings > Plugins, and verify the identity before enabling it.
Download setup file
03
Sign in, enable, and pair once
Use the separate authenticated service flow, enable Remote access on this PC, and complete the one-time pairing ceremony. This is the standing-authority decision.
Open the connection guide
04
Test from another device
With nobody approving at the target PC, send a harmless prompt, verify desktop pictures and private results, then separately rehearse Stop, Pause, Disable, and Revoke.

The setup file alone only selects the extension. Installing, enabling, and one-time pairing together grant standing unattended authority; later prompts require zero target-side approvals.

Evidence, not compatibility by implication

The old approval proof does not verify the new unattended model.

Historical version 0.2.241.0 evidence exercised a simulated authenticated session that still required one local approval. That is a different authority model. It was not rerun for 0.2.242.0 and cannot qualify one-time-paired, zero-per-prompt unattended control.

Historical evidence supports only

Recognition of the optional plugin path
One bounded simulated authenticated-session dispatch under the old approval model
Denial after old local gates were disabled

Required before release

New built and signed Connect package
Independent standing-authority contract audit
Installed clean-machine unattended round trip with no target-side prompt approval
Private desktop-picture and multi-turn result flow
Distinct Stop, Pause, Disable, and Revoke rehearsal

Stop: request that active work stop as soon as the local executor can do so safely.

Pause: stop accepting or advancing work while preserving resumable state.

Disable: turn off the extension on this PC so it accepts no new remote work.

Revoke: invalidate the pairing or service authority so future authenticated requests fail closed.

No rollback claim: none of these controls undoes Windows effects that completed before the control took effect.

Ownership: RemoteEndpoints.com is a related first-party service. This is product-owned integration documentation, not an independent security audit.

Setup-file details and technical references

The template includes enabled and userApproved values for accepted local intake. The file alone does not prove a connection or pairing. Its installedUtc value is template metadata, not this device's connection time. Standing unattended authority begins only after the independent extension is installed, enabled, and one-time paired.