LIMEN COMMANDER

Install. Connect.
Stay in control.

A first-party setup path for connecting your AI client to LIMEN Commander. Install once, approve exactly what you want, and let the system verify the connection before it calls anything ready.

AccountSign in or resume

RegisterVerify & pair this device

InstallOpen LIMEN Commander

ConnectChoose your AI client

AuthorizeApprove exact access

VerifyEvidence before READY

CUSTOMER ACCESS

Sign in to your OAIQO account

Your customer account is the identity used for plan access, installer eligibility, device enrollment and AI-client connection. Existing sessions are detected automatically; manual sign-in stays available here.

One customer identity Automatic session detection Google or email sign-in

02 · DEVICE REGISTRATION

Verify once. Bind the device to your account.

The account creates a short-lived one-time pairing ticket. LIMEN Commander or the qualified manual connector creates the device key locally, proves possession of that key, and consumes the ticket. The private key never leaves the device.

Account verified One-time pairing ticket Local Ed25519 private key

SurfaceOAIQO LIMEN

VerificationSIGN IN REQUIRED

Device registryNOT CHECKED

ONE-TIME PAIRING TICKET —

Expires in 10 minutes. The ticket is consumed once.

03 · MANUAL LAPTOP ROUTE

Register this laptop, then start the relay.

The manual route creates or loads the laptop’s existing local Ed25519 identity, proves possession of that private key, binds the DeviceID to your verified Owner account, then starts the existing outbound-only LIMEN relay.

Local device identity No inbound router ports No password or MFA export

Detecting your platform… The installer stays locked until the exact release earns independent qualification.

04 · CONNECT

Choose your AI client

Select the client you already use. LIMEN Commander handles the normal connection path and shows manual details only when a client actually needs them.

05–06 · AUTHORIZE & VERIFY

Nothing turns green before it is verified.

Approve the exact device and requested capabilities. LIMEN then checks identity, connection freshness, authorization state and the governed work path before presenting READY.

Device identityVerified locally

Secure connectionFreshness checked

AuthorizationExplicit approval

Ready stateEvidence required