Get started
Get started
Install LocalEndpoint Connect, verify the download, choose a local model, and send your first message in four clear steps.
Your first local session
From download to your first local chat in four steps.
No account is needed for local-only use. Install the tester build, verify it, choose a model already on your computer, and send a message.
- 1Download
- 2Verify
- 3Choose model
- 4Start chat
Keep it simple
A clear first session, with approval in your hands.
The website provides the installer and checksum. LocalEndpoint Connect handles the model, memory, message, and every protected approval on your computer.
01 / Download
Get the Windows tester build
Download the single installer from the current release page.
Open download
02 / Verify
Match the SHA-256
Compare the installer with the published checksum before you run it.
View checksums
03 / Model
Choose a local model
Open Models in the app and select a reviewed model stored on this computer.
Model guide
04 / Chat
Send your first message
Chat locally. Protected actions remain separate and ask for approval.
Review the safety boundary
Advanced browser validation and evidence tools
First-run flightcheck
A safe first session has four visible signals.
Before Desktop enters the story, the quickstart should prove the boundary in public: a known sample, local validation, a readable receipt, and a clear stop before runtime authority.
Sample
Known public input
Start with example data so no private endpoint details are needed for the first review.
Validator
Browser-only checks
Schema and boundary checks run in the tab without upload intake or localhost probing.
Receipt
Portable proof
The result is a redacted artifact that shows what passed and what remains unclaimed.
Handoff
Local decision point
Desktop is considered only after the person understands the public proof and wants local review.
Flightcheck rule
Use public sample
Validate in browser
Export receipt
Stop before runtime
First-session cockpit
Try the system without giving the website a machine.
The first session is designed to be useful before it is powerful: no private endpoint, no secret, no localhost probe, no command dispatch. You should leave with a receipt and a clearer decision.
Input
Safe manifest sample
Start from a known-good public example instead of private device data.
Choose example
Local check
Browser-only validator
Run schema checks in the tab and keep the public server out of the payload.
Validate sample
Output
Portable evidence receipt
Export a review artifact that says what passed and what it does not prove.
Receipt model
Decision
Desktop remains a separate local step
Install Desktop after the boundary makes sense, not before.
Download path
Denied during first session
Private uploads
Localhost scans
Desktop commands
Credential prompts
Safe first run
A dry run that earns the next click.
Use the public sample to learn the contract before installing anything: the browser checks schema shape, evidence language, and denied behavior while your machine stays unaddressable.
- 01Pick the public sample
Start with known example data instead of private endpoint details.
- 02Run browser checks
Validate in the tab with no upload, machine probe, or website command channel.
- 03Read the receipt
Confirm what passed, what failed, and what the receipt does not claim.
- 04Choose the local path
Move to Desktop only when visible local review adds value.
First-run proof
Invited-user handoff
Leave with a redacted artifact you can discuss with someone you know before anyone touches a private endpoint.
Start dry run
Website channel remains closed
No localhost probe
No private file read
No command dispatch
No credential prompt
First-session contract
Public explanation only
Browser-local validation
Redacted evidence
Desktop review when needed
Try nowValidate the safe sample
The browser validator opens with a valid example and generates a receipt locally.
Open validator
NextMap your own endpoint
Use schemas to define allowed operations, denied operations, input limits, output shape, and evidence policy.
View schemas
Operating boundary
Public clarity, local authority.
Public product, docs, download, and validation pages do not dispatch desktop commands, probe localhost, upload files, collect runtime telemetry, or claim runtime safety certification. Account credentials are accepted only on dedicated account routes.
