Skip to content
Luotsi Luotsi

Installation

Luotsi is distributed as a self-contained CLI through GitHub Releases. The quickest path is the per-user release installer for your platform.

Windows

Section titled “Windows”
Terminal window
iex (irm https://github.com/digablesolutions/luotsi/releases/latest/download/luotsi-install.ps1)

After the install finishes, open a new terminal and verify the command:

Terminal window
luotsi --version
luotsi version
luotsi devices

macOS and Linux

Section titled “macOS and Linux”
Terminal window
curl -fsSL https://github.com/digablesolutions/luotsi/releases/latest/download/luotsi-install.sh | sh

Then verify the install:

Terminal window
luotsi --version
luotsi version
luotsi devices

Manual release archives

Section titled “Manual release archives”

If you do not want to run the installers, download a self-contained archive from GitHub Releases. Each archive includes the CLI executable and companion files emitted by publish.

Build from source

Section titled “Build from source”

The repository is pinned to .NET SDK 10.0.300.

Terminal window
dotnet build Luotsi.sln
dotnet test Luotsi.sln
dotnet run --project Luotsi.Cli -- devices

First-run validation

Section titled “First-run validation”

Once a device is visible over adb, let Luotsi validate the setup it owns:

Terminal window
luotsi doctor
luotsi doctor --device <serial>
luotsi doctor --device <serial> --fix

Use doctor when you want the broad first-run report. Without --device or --device-query, it lists adb-visible devices and returns exact next commands for selecting the target. With a selected device, it wraps adb checks, optional package preflight, and the same live-view readiness path exposed by view setup and view-doctor. The JSON result includes a readiness_plan with status, blockers, next_command, and recommended_commands for operator or agent handoff; ready package-aware reports route to discover first, then keep package preflight in the recommended follow-up list.

Next steps

Section titled “Next steps”