Loboot for Openclaw

1. Install the Loboot CLI separately by following the official installation guide. The skill does not install the CLI or modify services as a setup step.
2. Confirm that loboot is available on PATH and check its version. CLI version and help output are text, including when --json is supplied.
3. Read installed help before using unfamiliar commands. For JSON responses, check the exit status, schema_version (loboot.cli/v1), and ok; inspect error.code and error.message on failure, and preserve unknown fields, states, and warnings.
4. Before mutations or diagnoses involving partial progress, ownership, or native activation, read the skill’s references/safety.md guidance.

command -v loboot
loboot --version
loboot --help
loboot list --json

For a new direct-argv definition, use an absolute executable and working directory, and make consequential defaults explicit. Keep Loboot flags before the -- separator; Loboot does not expand shell syntax or variables.

loboot add ID --cwd /absolute/directory --mode service --restart never -- /absolute/executable ARG

For an offline plan or test, provide an absolute physical root and a supported platform. --platform requires --root; do not remove the root to bypass a refused offline operation.

loboot --root /absolute/physical/root --platform linux list --json

Definitions and inputs

• A Loboot service ID contains 1–63 lowercase letters, digits, or hyphens and starts with a letter.
• A reusable TOML manifest must supply all six fields: id, executable, args, cwd, mode, and restart. Use args = [] when there are no arguments. Unknown fields are errors, and manifest settings cannot be overridden by direct-add options.
• The executable and working directory must exist and use absolute physical paths with no symlink components. Arguments are literal; Loboot does not perform shell or variable expansion.
• Supported modes include service and once; once requires restart policy never. Service restart policies are never, on-failure, and always.

Files and sandbox data

An offline root isolates Loboot’s state/ and native/ files and prohibits manager execution. Offline add, update, and remove can write sandbox files unless run as dry-runs. Offline runtime and activation operations require --dry-run. Dry-run itself creates no directories, locks, files, or repairs. The skill does not specify a separate generated report format.