App Setup and Pairing

Register development apps with the resident host and issue one-use enrollment QRs from the local player or CLI.

The resident host keeps a local app registry so enrollment invites, connected installations, sessions, tests, and quality history have a stable app ID. Open Apps in the local player to inspect registered apps and their current session state.

Scan-once flow

  1. Install and initialize the Ansight SDK in a development or QA build.
  2. Register the app with ansight app register or the guided setup workflow.
  3. Start the resident host and open the local player.
  4. Use the QR action in the player, or run ansight pairing issue <app-id> --qr.
  5. Open the SDK scanner in the app and scan the one-use invite.
  6. The SDK stores its enrollment state privately and reconnects on later launches while the enrollment remains active.

The player can issue a general pairing QR from its header. Use the CLI when you need to pin the invite to a specific app, duration, host address, or tool-policy ceiling.

What an invite contains

An enrollment invite contains:

  • the target app ID and display name when one is selected;
  • reachable addresses for the local host;
  • an unguessable, one-use access token;
  • invite and enrollment expiry times;
  • the maximum remote-tool policy (read, write, or critical).

The first installation consumes the invite. That installation can reconnect with its stored enrollment; a different installation needs a fresh QR.

Trust boundary

Treat the QR as a bearer credential and issue it only on a trusted development or QA network. App registration and pairing do not grant unrestricted access to the app: the SDK tool guard and per-tool policy continue to decide which reads or mutations are allowed.

Use ansight app list --json, ansight app register, ansight pairing issue, and ansight pairing list for structured app and enrollment management. See CLI Commands.