Optional connections

Optional extensions

Local chat, local models, and local memory work without an extension. Add protected remote review or public-safe shared memory only when you choose.

Compare extensions See setup steps

Current catalog

Choose the capability. Keep the boundary visible.

The current catalog lists two optional extensions that LocalEndpoint Connect recognizes. A listed setup file is not independent security review, runtime permission, or proof that every hosted workflow has passed end-to-end testing.

Remote workflowsCatalog listed · live proof open

RemoteEndpoints.com

Review protected requests when you are away from your PC. A separate account, extension setup, local enablement, and visible approval are required. The latest bounded dispatch proof is historical, not a current live round trip.

Purpose: Away review of protected requests
Network: Only after separate setup and sign-in
Authority: Installation does not approve an action

Review RemoteEndpoints setup and limits

Shared memoryCatalog listed · hosted proof open

MemoryEndpoints.com

Share selected public-safe decisions and handoffs with approved agents while local .uai memory stays active. The workspace key stays in Windows Credential Manager for the current user.

Purpose: Public-safe shared project memory
Network: Only after separate setup and owner enablement
Current limit: Live hosted save and search are not yet verified end to end for this build

Review MemoryEndpoints setup and limits

Three local steps

Add one extension without changing the core app.

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, then verify
Complete the extension's separate sign-in or key setup, enable only the options you intend to use, and confirm visible status before relying on it.

Before network use

Installation describes a connection. It does not authorize one.

Core app

Local chat, downloaded models, local memory, and protected-request decisions continue without either extension.

RemoteEndpoints

Only approved remote-workflow data is sent after separate setup, sign-in, local enablement, and approval.

MemoryEndpoints

Only owner-enabled public-safe summaries are eligible to leave the device. Keep important memory local while hosted save-and-search proof remains 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.