Local chat, local models, and local memory work without an extension. Pair RemoteEndpoints for unattended control, or add MemoryEndpoints for public-safe shared memory.
The current catalog lists two optional extensions that LocalEndpoint Connect recognizes. A listed setup file is not independent security review or proof that a hosted workflow passed end-to-end testing. RemoteEndpoints becomes different only after the owner installs, enables, and one-time pairs it for standing unattended authority.
Unattended remote controlCatalog listed · new package required
RemoteEndpoints.com
Control the target PC while nobody is there. Independent extension install, local enablement, and one-time pairing establish standing authority; later prompts require zero target-side approvals. Public Connect version 0.2.242.0 is not verified for this contract.
Purpose
Unattended remote AI control of the paired Windows computer
Execution
Authenticated browser intent; Windows work performed by Connect
Shared memoryDevelopment pairing implemented · production proof open
MemoryEndpoints.com
Share selected public-safe decisions and handoffs with approved agents while local .uai memory stays active. Installed development 0.2.273 uses one-use browser PKCE and stores only a bound per-agent connector credential for the current Windows user.
Purpose
Public-safe shared project memory
Pairing
Settings → Connect securely in browser, then approve exact company/workspace/project scope
Current limit
No real production round trip or publicly downloadable artifact is qualified
Add one extension, then complete its explicit authority step.
01
Choose one
Core local chat needs neither extension. Review its purpose, network use, and current limitation first.
02
Place the setup file
Save it in %LOCALAPPDATA%\LocalEndpoint\Connect\Plugins, open Settings > Plugins, and choose Refresh plugins.
03
Configure, authorize, then verify
For RemoteEndpoints, sign in, enable, and pair once to establish standing unattended authority. For MemoryEndpoints, choose Settings → Connect securely in browser, approve exact company/workspace/project scope once, and then enable only the intended memory lanes.
Before network use
Installation selects the extension. Remote pairing authorizes unattended work.
Core app
Local chat, downloaded models, local memory, and protected-request decisions continue without either extension.
RemoteEndpoints
After independent install, sign-in, local enablement, and one-time pairing, private authenticated prompts can run with zero target-side per-prompt approvals. Connect performs the Windows work.
MemoryEndpoints
Only owner-enabled public-safe summaries are eligible to leave the device. Installed development 0.2.273 implements browser pairing; production roundtrip and public artifact qualification remain open.
Documentation
LocalEndpoints.com and RemoteEndpoints.com are related first-party services. These pages are product documentation, not independent certification.
For developers: build or review an extension
Developer resources
Use the published contract and submit redacted evidence.
New extension IDs stay blocked until catalog review and desktop intake support agree. Public manifests describe capabilities; they do not grant runtime authority.
