Product documentation

CLI status and responsibilities

See what belongs on the local device and why installation commands are not yet public.

Release status

Development

Outcome

Use the CLI for local discovery, serving, device identity, private pairing, and loopback mounting after a release channel is validated.

Prerequisites

  1. A supported operating system
  2. Compatible loopback model runtimes
  3. A published and verified release channel

Current path

  1. The CLI owns device-local discovery and model connections.
  2. The web account owns account-wide device revocation, Network Sharing policy, and public API-key management.
  3. The CLI obeys effective server policy and cannot independently enable Network Sharing.
  4. Install and update commands will be published only after signed distribution and upgrade behavior are validated.

Authoritative success state

A released CLI reports its own identity and local state while the web account reports durable account state. The public distribution contract is not yet fixed.

Common failures and recovery

  1. Do not download binaries from an undocumented channel.
  2. Use account device revocation if a local device credential is at risk.

Security and privacy boundary

The CLI connects only to local model endpoints you choose. Device approval does not grant OpenToken raw machine access.

Next valid action

Read getting started