Files
sanderling/docs/manual/cli.md
T
pj b554a9ecee docs(manual): correct the flags the cli reference gets wrong
--launcher-activity does not exist in cmd/sanderling/main.go. --device,
--android-app-path and --arm do and were undocumented. runs.md still listed
--max-steps and --exit-on-violation as unshipped, and described --clear-data
as opt-in when the default is already true, contradicting itself ten lines on.
2026-08-15 23:00:16 +05:30

4.0 KiB

title
title
CLI reference

CLI reference

sanderling <command> [flags]

sanderling test

Run a spec against an app for a fixed duration.

Flag Default Description
--spec required Path to the TypeScript spec.
--bundle-id required Target app bundle ID (Android: applicationId).
--device optional (android) Android device serial, as adb devices reports it. Required when more than one device is attached.
--android-app-path optional (android) Path to the APK. Clear-state reinstalls from it instead of running pm clear.
--platform android Target platform: android, ios, or web.
--avd optional (android) Android AVD name to boot if no device is connected. Required only when no device is connected and multiple AVDs exist.
--ios-device optional (ios) iOS target: a simulator name/UDID to boot, or a connected device's name, UDID, or CoreDevice id.
--ios-app-path optional (ios) Path to the .app bundle for clear-state reinstall (simulator via simctl, device via devicectl).
--duration 5m Total test duration (30s, 5m, 2h, 1d).
--max-steps 0 Stop after this many steps (0 = no cap, the duration governs). A step budget is what makes two generators comparable.
--exit-on-violation false Stop the run at the first property violation and exit 2.
--arm optional Experiment label recorded in the run's metadata. Used by the campaign tool to tell one sweep cell from another.
--seed 0 PRNG seed. 0 uses a random seed and records it in meta.json.
--generator seeded Who picks each action: seeded (the run's PRNG) or llm (a vision model). See the LLM generator.
--output ./runs Output directory for traces.
--clear-data true Clear app data before launching so the run starts from a fresh install. Pass --clear-data=false to resume prior state.

Exit codes: 0 the run finished (violations, if any, are in the summary), 2 the run stopped on a violation under --exit-on-violation, 1 something went wrong. CI reads the difference between 2 and 1 to tell a found bug from a broken harness.

sanderling replay [run-or-runs-dir]

Serve a local web UI for browsing traces. The positional argument is optional and may point at either a runs directory (the parent of many runs) or a single run directory (auto-detected by the presence of meta.json). Defaults to ./runs.

Flag Default Description
--port 0 (ephemeral) TCP port to listen on.
--no-open false Skip opening the default browser on startup.
--dev false Reverse-proxy non-API requests to the Vite dev server on 127.0.0.1:5173.

See the replay UI page for the panel reference and keyboard shortcuts.

sanderling doctor

Check the host environment for a working sanderling setup.

sanderling doctor [--platform web|android|ios|ios-device|all]

--platform defaults to all, which runs every platform's checks (deduped). Pass a specific platform to scope the output.

Platform Checks
web headless Chromium can launch (the bundled CDP surface boots a real browser).
android adb and emulator on PATH, or under $ANDROID_HOME, $ANDROID_SDK_ROOT or a standard SDK install location; Java 17+; embedded native sidecar JAR is real.
ios xcrun on PATH; simctl on PATH. The simulator path drives the native companion with no JVM.
ios-device the ios checks plus devicectl; the macOS usbmuxd socket; a connected, paired device; App Store Connect signing credentials present.

sanderling version

Print the CLI version.

Flags coming in v0.1.0

  • --permissions to pre-set OS-level permissions (for example --permissions location=allow,notifications=deny).

Tracked in the v0.1.0 milestone.