runcloud command-line interface. Install
it from npm:
runcloud --version to print the installed version and
runcloud <command> --help to inspect the exact options supported by that
version.
Authentication
Use
runcloud login --manual when the browser cannot return to the local
callback automatically. runcloud account --json returns machine-readable
output.
Mobile sessions
The iOS and Android command groups share the same lifecycle:ios create and android create accept:
iOS sessions also support
runcloud ios tunnel <id> and
runcloud ios tunnel-status for connecting a local development service to the
remote simulator. See Run an iOS Simulator for the full
workflow.
Assets and samples
asset also accepts the plural alias assets; sample accepts samples.
Sandboxes
Sandboxes are the single compute noun. Persistence and a stable public hostname are capabilities you turn on — not a separate product:sandbox create accepts:
sandbox expose accepts --port <port> (default 3000), --name <name> for a
first exposure (defaults to the sandbox name), and --reconcile to retry
hostname routing.
See Persistent Sandboxes for creation and routing examples.
Images
See Custom Images for the full workflow, including CI pre-baking.
Deprecated: runcloud box
Earlier releases modeled an exposed persistent sandbox as a separate box
noun. Every runcloud box … command still works as a deprecated alias and
prints a pointer to its sandbox equivalent:
SSH config blocks written by older releases keep connecting: the
box proxy
transport remains supported, and re-running setup-ssh rewrites the block to
the current form.
Demos and agent skills
Available demos are
eight-device-mosaic and live-camera-relay. Pass --open
to open the viewer automatically.
Automation
Commands that return structured data accept--json. A typical shell workflow
captures IDs rather than copying placeholders: