Help center

Direct answers

Direct answers for humans, developers, and invited testers who need to know what LocalEndpoint does today and what it refuses to do from the public site.

Start quickstart Read security boundary

Direct answers

The short version: public clarity, local authority, reviewable evidence.

LocalEndpoints.com explains and validates; Connect owns authority and performs Windows work. Ordinary protected local actions are owner-gated. The independent RemoteEndpoints extension becomes a separate unattended mode after install, enablement, and one-time pairing.

Does the public site connect to my machine?

No. It serves metadata, docs, schemas, examples, and browser-local validation. It does not probe localhost, upload private files, dispatch commands, collect telemetry, or request credentials.

Who is this for right now?

Invited users, people you directly know, developers, reviewers, and early testers who want a local-first AI connection workflow before broad public distribution claims are made.

What makes it useful before broad release?

The site already gives visitors the story, public boundaries, schemas, route index, safe examples, quality gates, download artifacts, and browser validator path.

Can anyone download it from the website?

Technically yes, the current path is a checksum-backed portable package and offline toolkit. The copy stays clear that installer signing, store approval, and broader certification gates are future readiness work.

What does Desktop add?

Connect owns private authority state and performs Windows work. Ordinary protected local actions wait for the owner's current decision; separately installed, enabled, and one-time-paired RemoteEndpoints prompts use standing unattended authority.

Does every RemoteEndpoints prompt need approval at the target PC?

No. Independent install, local enablement, and one-time pairing are the owner's deliberate standing-authority decision. Later authenticated private prompts require zero target-side approvals. Public Connect 0.2.242.0 is still a legacy tester and is not verified for this contract.

How should AI agents treat the site?

Agents can read discovery files, route indexes, schemas, examples, and quality gates. They should stop before runtime authority and hand off to human-controlled local review.

Answer resolver

Every common question resolves to one of four safe surfaces.

The FAQ turns uncertainty into routing logic: public pages explain, browser tools validate, Connect resolves ordinary owner decisions or paired RemoteEndpoints authority, and receipts prove what happened without exposing private endpoint state.

Public site Explains without control

Questions about what LocalEndpoint is resolve to overview pages, docs, route metadata, and security boundaries.

Browser Validates without upload

Questions about trying it safely resolve to manifest checks, examples, and local receipt exports.

Connect Owns two visible authority modes

Ordinary protected work waits for the owner. One-time-paired RemoteEndpoints prompts run unattended with zero target-side approvals.

Evidence Proves without secrets

Questions about readiness resolve to checksums, schemas, quality gates, and redacted review artifacts.

Resolver rule Explain publicly Validate locally Choose ordinary or paired authority Share evidence only

Visitor decision spine

Ask like a human. Move only when the boundary is clear.

The FAQ is designed to turn uncertainty into a safe next step: understand the split, verify with public data, choose whether a download makes sense, then keep private authority state in Connect.

01Understand the split
The website explains the public model; it does not become the endpoint.
02Verify with samples
Use public schemas, examples, and browser-local checks before private data enters the conversation.
03Download with evidence
Use checksum-backed artifacts while installer signing and broader distribution gates remain visible.
04Choose authority deliberately
Use a current owner decision for ordinary work or pair RemoteEndpoints once for unattended work.

Public siteExplains and validates

Browser tabChecks without upload

ConnectOwns ordinary and paired authority

ReceiptProves what happened

Answer router

Every answer points back to the same boundary: learn here, execute through Connect.

The public LocalEndpoints site is not a control surface. Authenticated private RemoteEndpoints intent is a separate workflow, and Connect—not the browser—performs Windows work.

Question What is LocalEndpoint?

Start with the public-to-local model and the permission membrane.

Question Can I try it safely?

Use the browser-local validator before any private endpoint review.

Question Can invited users download it?

Follow checksum-backed artifacts and keep broad-launch claims separate.

Question Which authority mode applies?

Use an owner decision for ordinary local work or a valid one-time RemoteEndpoints pairing for unattended work.

FAQ boundary Public clarity Browser-local checks Explicit authority mode Evidence, not secrets

Public webExplains

Pages, schemas, examples, discovery files, and quality evidence.

BrowserValidates locally

Manifest checks and receipts happen in the tab without upload intake.

ConnectOwns authority state

Ordinary local work is owner-gated; one-time-paired RemoteEndpoints work runs unattended.

Release pathInvited first

Useful now, with broader distribution gates still visible.

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.