Developers

RemoteEndpoints developer contract and API

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. Public information is sanitized; private operator data requires authenticated operator authority.

Current availability

The reviewed LocalEndpoint Connect source now implements persistent account pairing, secure Windows credential storage, outbound check-in and work polling, private desktop-picture upload, prompt execution, private results, stop handling, credential rotation, and revoke recovery. That matching source has not yet been published as the current public download or proven in an installed production round trip. Use the interactive mock for evaluation until a matching Connect release is published and verified end to end.

Current unattended-control contract

Start device authorization in Connect, confirm the short code in an authenticated browser, exchange the one-time access token, and register the extension installation for a durable revocable device credential.

After enrollment, Connect checks in, uploads private desktop pictures, atomically leases prompts, reports strict command-state transitions, receives stop signals, and survives normal browser or Connect restarts without another target-side handoff.

While one command is running, Connect polls /work-items?control_only=1. That exact authenticated mode returns stop requests and the current extension, account, and effective authority gates without claiming the next queued prompt.

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.

This first-party documentation is not an independent audit or certification. Do not infer current package compatibility from historical evidence unless that package has been retested.

Auth and token classes

Account session: owns computers and private operator data; accepted from an HttpOnly cookie or explicit API bearer.
Device code: short-lived browser confirmation code used only during initial pairing.
Device access token: single-use exchange token that can register one Connect installation.
Durable device token: returned once to Connect, purpose-scoped, rotatable, and invalidated on revoke.
Command claim token: binds an atomic work lease and terminal acknowledgement to one worker attempt.

API endpoints

RemoteEndpoints public and private API contract
Route	Method	Auth	Description
`/api/public-route-index.json`	GET	none	Public route inventory.
`/api/health`	GET	none	Minimal service health response.
`/api/account/infrastructure`	GET	none	Read boolean-only account-service and persistent-control readiness status.
`/api/account/register`	POST	email address	Accept a generic email-only create-or-reissue verification request without returning account state.
`/api/account/login`	POST	account credentials	Create an HttpOnly account session.
`/api/account/session`	GET	account session	Read the current account session.
`/api/account/device-authorizations`	POST	none	Start website-login device authorization for LocalEndpoint Connect.
`/api/account/device-authorizations/approve`	POST	account session	Confirm a pending one-time device pairing code.
`/api/account/device-authorizations/token`	POST	device code	Poll a pending device authorization without website credentials.
`/api/remote/devices/register`	POST	one-time device access token	Register the enabled extension and issue a durable device credential once.
`/api/remote/devices/{device_id}/check-in`	POST	device bearer	Publish extension-enabled state, version, capabilities, and heartbeat.
`/api/remote/devices/{device_id}/work-items`	GET	device bearer	Atomically lease authenticated prompts, or use the exact control_only=1 query to read stop signals and authority gates without claiming queued work.
`/api/remote/devices/{device_id}/commands/{command_id}/status`	POST	device bearer plus command lease	Acknowledge a valid private Connect AI command-state transition.
`/api/remote/devices/{device_id}/desktop-frames`	POST	device bearer	Upload a bounded private JPEG, PNG, or WebP desktop picture.
`/api/remote/devices/{device_id}/token/rotate`	POST	device bearer	Atomically rotate the durable device credential and invalidate the old value.
`/api/operator/devices`	GET	account session	List account-owned RemoteEndpoints computers.
`/api/operator/devices/{device_id}`	GET	account session	Read one private computer workspace snapshot.
`/api/operator/devices/{device_id}/commands`	POST	account session	Queue an authenticated prompt for Connect AI.
`/api/operator/devices/{device_id}/commands/{command_id}/stop`	POST	account session	Request remote cancellation of a queued or running command.
`/api/operator/devices/{device_id}/pause`	POST	account session	Pause new account-side remote prompts without changing local extension state.
`/api/operator/devices/{device_id}/resume`	POST	account session	Resume account-side prompt delivery only while the local extension remains enabled.
`/api/operator/devices/{device_id}/revoke`	POST	account session	Revoke a paired computer and its durable credential.

Command status enum

queued: Authenticated prompt is waiting for an atomic Connect work lease.
running: A Connect worker holds the current claim token and lease.
completed: Connect AI finished and returned a private result.
stopped: The run was stopped before or during execution.
rejected: Connect could not accept the prompt under its implemented capability contract.
failed: Connect AI reported a private execution failure.

Device authority status

active: Both the local extension and account delivery gates are enabled.
paused: One authority gate is disabled; no new prompt lease is issued.
revoked: The durable device token is invalid and retained pictures have been removed.

Reported capabilities

Connect reports the capabilities available in its installed build, such as desktop pictures, Connect AI, program/browser control, pointer and keyboard input, and network access. The server records these labels; Connect remains responsible for implementing and validating them.

Two independent authority gates

Effective remote control is extension_enabled AND account_enabled AND NOT revoked. Device check-in cannot undo an operator pause, and browser resume cannot override a local extension disable.

Retired short-lived session routes return 410 Gone. New integrations must use persistent device registration, leased prompts, private desktop pictures, and explicit stop or revocation signals.

Optional advanced architecture

The swarm design keeps each active agent name and memory instance exclusive.

Powerful systems are designed to run multiple LocalEndpoint Connect instances in parallel. Each parallel instance is intended to use its own MemoryEndpoints connection, a distinct active agent name, and its own .uai memory instance or branch.

Exclusive identities

Two active agents must not use the same MemoryEndpoints agent name.
One active agent may attach to a specific .uai memory instance at a time.
If either identity is already active, the next instance must wait or use a distinct name and memory branch.

Parallel branches

Branch the .uai memory when parallel agents need to continue from the same starting context.
Each parallel Connect instance uses a distinct agent name, connection, and memory instance or branch.
There is no one-agent-per-computer limit; the invariants prevent collisions without diminishing swarm capacity.

Design contract, not a current RemoteEndpoints server claim.

This server does not yet negotiate or enforce MemoryEndpoints agent-name ownership, .uai active-instance ownership, or memory branches. A matching MemoryEndpoints.com integration contract is still required before this can be presented as hosted enforcement.

Safe examples

Authorization: Bearer <one_time_device_access_token>
POST /api/remote/devices/register
{"installation_id":"<stable_installation_id>","device_label":"Studio computer","app_version":"<version>","capabilities":["desktop_picture","connect_ai"]}

Authorization: Bearer <durable_device_token>
GET /api/remote/devices/<device_id>/work-items

Authorization: Bearer <durable_device_token>
GET /api/remote/devices/<device_id>/work-items?control_only=1

Authorization: Bearer <durable_device_token>
POST /api/remote/devices/<device_id>/commands/<command_id>/status
{"status":"completed","result_message":"<private_result>","claim_token":"<command_claim_token>"}

Examples must use placeholders. Do not include real account, device, or claim tokens, credentials, prompts, results, desktop pictures, device identifiers, or private logs.

OpenAPI Well-known manifest llms.txt Route index