Skip to main content
This installs a standalone runcloud binary and then starts sign-in, so one command takes you from nothing to an authenticated CLI. Nothing needs to be preinstalled — no Node, no package manager, no sudo. If you already have Node:

What the installer does

  1. Detects your platform: darwin-arm64, darwin-x64, linux-x64, or linux-arm64. Anything else exits with a message pointing at npm.
  2. Reads the release manifest from https://dl.run.cloud/latest.json.
  3. Downloads the binary for your platform and verifies its SHA-256. A mismatch aborts without touching an existing install.
  4. Installs to ~/.run-cloud/bin/runcloud, writing to a temporary file and renaming it into place so an interrupted download cannot leave a partial binary on your PATH.
  5. Adds ~/.run-cloud/bin to your PATH in ~/.zshrc, ~/.bashrc, or ~/.profile — once, not on every run.
  6. Starts runcloud login, unless the environment says otherwise (below).
Re-running the command upgrades in place and is safe to repeat.

Non-interactive installs

CI runners, Dockerfiles, and agents that already hold an API key must not be asked to pick a sign-in method. The installer skips sign-in and exits 0 when any of the following is true: In those cases the binary is installed and the command prints how to sign in later. An agent with a key can use the CLI immediately:
Under curl … | sh the pipe is the script’s standard input, so an interactive prompt has nothing to read there. The CLI opens the controlling terminal itself, which is what lets one command both install and sign in.

Environment variables

Pin a release in CI so a new build cannot change what your pipeline runs. The release id is the version plus the commit it was built from, and every release gets its own permanent path:
https://dl.run.cloud/latest.json names the current release id.

Where things live

RUN_CLOUD_HOME moves both. To uninstall, delete ~/.run-cloud and remove the PATH line the installer added to your shell config.

Verifying a download

Every release publishes a manifest with a SHA-256 per platform, which the installer checks before installing. To verify by hand:
Each entry gives the object path and its digest; artifacts live at https://dl.run.cloud/<release-id>/runcloud-<target>.gz and are never rewritten — a rebuilt binary always gets a new path.

Next steps

Quickstart

Authenticate and open your first sandbox or mobile session.