Runs and notifications
Run a command
Put the complete original command after --:
RunBuoy preserves the original exit code, mirrors output locally, and optionally sends a safe status projection. A normal detached start returns after the Worker-ready nonce/Socket ACK and run.started handoff; the caller can then exit. To wait and receive the original command’s exit code:
Provide a title that contains no paths, arguments, or sensitive information:
Send a one-time notification
You can send a status notification without starting a managed Run:
Built-in demos require no arguments:
Local commands
These commands run on the current computer:
Neither the iPhone nor the server can invoke them.
These local commands remain available without pairing and while the Server is unreachable. Pending events can be retried later with runbuoy sync --json.
list shows active Runs by default; -a/--all includes completed history. Times use the local time zone and include seconds. status, logs, attach, and cancel accept a unique Run ID prefix; @latest selects the most recent Run.
Preview and prune older local records and logs:
Pruning asks for confirmation and cannot be undone. Runs with unsynchronized events are kept unless --include-unsynced is explicitly provided.
Preview remote data
Inspect what would be visible remotely without starting a command:
Optional safe log snippet
Full logs always stay local. When needed, explicitly upload up to 100 redacted trailing lines:
The iOS app clearly labels the uploaded snippet, and the server retains it for at most 24 hours.