Command-line interface
Install the CLI, run projects headlessly, and use exit codes.
Command-line interface
The busloom binary runs without Tauri or a WebView. It reads the same schema-1 project, freezes the selected run profile and connection profile, and invokes the same native automation runner as the desktop application.
Install and verify the command
Install from Busloom
Open Application Preferences → Command-line interface and install the launcher into a directory on your PATH.
Open a new terminal
Shells cache command lookup. Start a new terminal or refresh the shell after installation.
Verify
Run busloom --help and busloom license status before relying on the command in CI.
Run saved automation
busloom run ./device.busloom.json \
--run-profile "Smoke test" \
--connection "Bench RTU" \
--dry-run \
--report junit \
--output ./report.xml| Exit | Meaning | Typical CI action |
|---|---|---|
| 0 | Automation completed and passed | Continue the pipeline |
| 1 | Automation ran and failed | Publish the report and fail the test stage |
| 2 | Invalid command usage or input | Fix arguments, names, or paths |
| 3 | Setup, license, project, or connection failure | Fix the environment before treating it as a device test failure |
License operations
busloom license status
busloom license request --output ./machine.busloom-license-request
busloom license install ./machine.busloom-license
busloom license inspect ./machine.busloom-licenseThe CLI supports offline activation. Export a request on the target machine, turn it into a device license in My Busloom on a connected machine, then install the signed response on the target. Use the desktop app for the online device-code flow.