Skip to main content
Use the CLI for interactive terminal workflows or the TypeScript SDK for API-key based applications, CI, and agents.

Install the CLI

This installs the CLI and starts sign-in. With Node already available:
See Install the CLI for pinned versions, install paths, and how sign-in is skipped in CI, containers, and agent environments.

Authenticate

CLI commands can use a saved browser-authenticated session:
For CI and other non-interactive CLI use, provide both the API key and API URL:
The TypeScript SDK uses an API key created in the run.cloud dashboard:
The SDK does not require 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

The CLI example extracts the returned sandbox ID and releases the sandbox when the shell exits. See Linux sandboxes for sizing, snapshots, and the full API.

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

Create returns a signed browser URL, device id, lease id, and session id. For CLI scripts, prefer JSON:
See Run an iOS Simulator and Run an Android Emulator for platform-specific command references. See Control a Simulator for taps, gestures, text, keys, buttons, screenshots, MP4 screen recordings, and other interactions. For full runnable SDK source, see newly-app/run-cloud-examples/sdk-ios-android.

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:
Run the live camera relay explicitly when you want to connect your webcam to one broadcaster simulator and two receivers:
Both demos release their sessions automatically.

Upload and install an app

Download checksum-verified onboarding apps with the CLI:
Or download the same public fixtures with curl:
The iOS download is a simulator-compatible .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:

Clean up

Sessions are metered while active. Explicit release charges the final started minute. If the organization reaches its run.cloud credit ceiling, active sessions are closed automatically.