Install the CLI
Authenticate
CLI commands can use a saved browser-authenticated session:RUN_CLOUD_API_URL; it defaults to the production API.
The CLI accepts either the saved runcloud login credential or the API key and
API URL together. It does not require both login and an API key. See the
TypeScript SDK guide for the walkthrough, or use the
CLI reference and SDK reference for the complete
surface.
Create a Linux sandbox
Stop reinstalling dependencies on every boot
If your sandbox installs the same system packages or project dependencies every time it starts, bake them into an OCI image and register that image once:runcloud image create converts the image to a bootable microVM filesystem
ahead of time and waits until it is ready. Later sandboxes reuse that prepared
image instead of repeating setup work on every boot. Publish the OCI image to a
registry first; local Dockerfile build contexts are not supported yet.
See Custom images for deterministic digest pins, CI
pre-baking, refreshes, and build status.
Create a mobile simulator
Run a bundled demo
The CLI includes its maintained demos, so you can launch the default eight-device mosaic from any directory without cloning a repo or installing project dependencies:Upload and install an app
Download checksum-verified onboarding apps with the CLI:curl:
.app bundle packaged as
.tar.gz. The Android download is a signed APK. Their filenames, sizes, and
SHA-256 checksums are published in the
sample manifest.
To install your own build instead:
--install accepts app artifacts for the target platform. iOS Simulator
reliability depends on a simulator-compatible build; Android emulator sessions
expect an APK or another Android-compatible artifact.
You can also upload once and reuse the asset: