Skip to content
Luotsi Luotsi

Device Readiness

Luotsi is most effective when device selection and first-run health checks are explicit. The CLI has separate commands for lab-wide visibility, a selected device’s readiness, and package-specific preflight.

Lab-level checks

Section titled “Lab-level checks”

Use these when multiple transports are attached, devices are offline, or you want Luotsi to explain ambiguous selection results.

Terminal window
luotsi devices
luotsi doctor
luotsi lab status
luotsi lab doctor
luotsi adb reconnect offline

Selected-device checks

Section titled “Selected-device checks”

Use these after you know which transport you want to operate on.

Terminal window
luotsi device-status --device <serial>
luotsi wait-for-device --device <serial>
luotsi screen-state --device <serial>

Package-aware preflight

Section titled “Package-aware preflight”

When the workflow depends on a target app, include the package and let Luotsi capture a device fingerprint as part of the readiness story.

Terminal window
luotsi preflight --device <serial> --package <app.id>
luotsi doctor --device <serial> --package <app.id>
luotsi doctor --device <serial> --package <app.id> --fix

doctor is the broader onboarding entry point. Without a selected device, it lists adb-visible devices and returns exact next commands for choosing one. With --device or --device-query, it reuses adb checks, optional package preflight, and the same live-view readiness flow exposed by view setup and view-doctor. Its readiness_plan tells you whether the selected device is ready or blocked, which checks still block production use, and which exact command to run next. When a package-aware report is ready, next_command points to discover, followed by package preflight, inspect, screen-state, persisted quickstart handoff, scenario validation, run, and live view commands in recommended_commands.

If selection itself is ambiguous, start with lab status or lab doctor. If the selected device is known but the workflow still is not ready, switch to doctor, view-doctor, or view setup --fix so Luotsi can explain the missing prerequisite.

When each command matters

Section titled “When each command matters”
  • devices: raw inventory of adb-visible transports
  • lab status: why a selector matches or rejects devices
  • lab doctor: stale or ambiguous lab state with remediation commands
  • device-status: readiness details for one resolved transport
  • preflight: package-aware device and app context
  • doctor: device-selection guidance, then a single first-run report with optional repair behavior

Next steps

Section titled “Next steps”