Optional extension trust sheet

Add MemoryEndpoints to LocalEndpoint Connect

Share only owner-selected public-safe decisions and handoffs with approved agents. Local .uai memory stays active; live hosted save and search are still unverified for this build.

Review the 4-step setup See evidence limits Compare extensions

Integration boundary

Shared memory is optional. Keep important memory local.

Local .uai memory remains active and authoritative without MemoryEndpoints. Add hosted sharing only for summaries the owner has reviewed as public-safe.

Setup available
Key stored locally
Local memory remains active
Hosted proof open

Adds: Owner-selected public-safe decisions, status, procedures, evidence references, risks, and handoff summaries for approved agents.
Works without it: Local .uai memory remains active and authoritative.
Destination: MemoryEndpoints.com, only after separate setup and owner enablement.
What may leave: Only summaries the owner has chosen and reviewed as public-safe. Public-safe is an owner decision, not an automatic classification.
Excluded: Workspace keys, credentials, hidden prompts, full files, raw logs, model weights, proprietary training data, and private payloads.
Credential: The workspace key stays in current-user Windows Credential Manager, not this website, the manifest, app settings, prompts, reports, or logs.
Authority: Shared memory, public-safe save, and hosted search remain separate local choices. Installing the manifest grants no runtime authority.

Four deliberate steps

Set up MemoryEndpoints in four deliberate steps.

The published flow still needs workspace and agent identifiers plus a workspace key. URL-only single-agent pairing is not production-proven.

01
Install or update Connect
Use the checksum-backed Windows build, then open Settings > Plugins.
Get LocalEndpoint Connect
02
Add the extension
Save the template as memoryendpoints.com.plugin.json, refresh plugins, and confirm its identity.
Download setup file
03
Choose the memory lanes
Enable only shared memory, public-safe save, or hosted search that you intend to use.
04
Store securely, then test
Enter non-secret IDs, store the workspace key for this Windows user, and require a successful connection test before relying on hosted memory.

The setup file selects the extension for local intake; it does not connect an account, enable hosted access, or approve runtime work.

Evidence, not a badge

Secure-store evidence is historical; hosted memory remains open.

Version 0.2.239.0 installed-UI evidence covered the password input, Store securely, Remove key, redacted status and connection-test output, and removal of the legacy authentication toggle. No real production workspace key was used. Current version 0.2.242.0 has no verified hosted save-and-search round trip.

Evidence supports

Current-user Windows Credential Manager boundary
Redacted key status and connection-test output
Visible store and remove-key controls

Still open

Real workspace and protected identity readback
Live hosted save and search
URL-only single-agent pairing
Server-side rotation, revocation, and disconnect proof

Stop locally: turn off the memory lanes and remove the key in Settings. Removing the local key disconnects this device; it does not prove server-side key revocation.

Keep private material local: do not send credentials, hidden prompts, full files, raw logs, model weights, training data, or private payloads as shared memory.

Setup-file details and technical references

The template includes enabled and userApproved values for accepted local intake. They do not prove a hosted connection or grant runtime authority. Its installedUtc value is template metadata, not this device's connection time.