The current build supports Windows 10 or 11 on x64. Managed CPU use is proven; GPU inference is not claimed for this build.
Check requirementsProduct overview
LocalEndpoint in plain language
LocalEndpoint Connect runs reviewed AI models on your Windows PC, keeps local-only chat and memory on the device, and asks before protected actions.
Before you download
Make three decisions, then choose your next step.
LocalEndpoint Connect is an early-access Windows app for private local AI. Start with fit, privacy, and release risk—not internal architecture.
Local chat can run without a website account after files are present. The app may check release metadata; model downloads and optional services have separate network paths.
Review network behaviorVersion 0.2.242.0 is not Authenticode-signed. Windows can show Unknown publisher; verify the SHA-256 and follow device policy.
Read the release trust reportWhat you get today
Local AI first. Optional connections later.
Install the Windows app, choose a reviewed local model, and start with local chat. Remote access and shared memory are separate plugins that remain off until you install and enable them.
Open detailed engineering accounting- Windows app
- 0.2.242.0 unsigned early access
- Local path
- Reviewed model, chat, local memory, and approval
- Website role
- Download, help, checksums, and public documentation
- Optional services
- RemoteEndpoints and MemoryEndpoints stay off by default
Real uses, honest limits
Start with one job you can explain.
Each scenario says what works, where it happens, and which boundary still applies.
Chat with a local model without a website account.
The Windows app owns private work. After model files are present, prompts, replies, and local memory stay on this PC. Model downloads use a separate network path.
Start the local-chat guideReview a protected request before deciding.
Connect can show the request on your PC for a current local decision. This does not prove every action can execute in this build. The website cannot control your computer.
See the approval boundaryPrepare a public-safe MemoryEndpoints connection.
The connector and setup file are present, and the workspace key stays in Windows Credential Manager. Live save-and-search against MemoryEndpoints.com is not proven for this build; local memory remains active.
Review setup and limits