Getting Started

Install

macOS / Linux

curl -fsSL https://remotehost.ai/install | sh

Windows

irm https://remotehost.ai/install.ps1 | iex

This installs the rh command (also available as remotehost).

Log in

rh login

This opens /cli-login on the console in your browser. Copy the token shown there and paste it back into the terminal when prompted:

Opening <console-url>/cli-login...
Copy the RemoteHost CLI token from your browser and paste it here.
Token: ‸

The token is written to ~/.config/remotehost/config.json. You can skip the interactive prompt entirely by setting REMOTEHOST_TOKEN in your environment instead — useful in CI or on a headless machine.

If you run any command while logged out, Remotehost offers to start this same flow for you.

Launch your first sandbox

From inside a git repository:

rh claude

The first time you do this, Remotehost generates a dedicated ed25519 keypair at ~/.config/remotehost/id_ed25519 (reused for every sandbox after that — sandboxes trust the key that created them, not a shared operator key). Then it:

Resolves which org to use (if you belong to only one, that one is picked automatically).
Provisions an isolated host and copies the current repository onto it.
Launches Claude Code inside it over SSH.

Use rh codex the same way to launch Codex instead. Either command accepts flags to target a specific org, project, branch, or machine size — see the CLI Reference for the full list.

See what's running

rh ls

rh attach <name-or-id>   # reconnect to a running sandbox
rh stop <name-or-id>     # stop it (billing stops with it)

Or run rh with no arguments to open the interactive TUI, which lists orgs, projects, sandboxes, and recent activity, and lets you create or attach to a sandbox without leaving it.

Next steps

Read Concepts for how orgs, projects, and sandboxes relate.
Check the Console for team management and billing.
See Pricing & Billing for how usage is metered.