Getting Started

Install

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

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

The CLI is published to npm, so if you would rather not pipe a script into a shell, or you already manage global tools with npm, install it directly. This is what the script above does:

npm i -g @remotehost/cli

Either way you get the remote command, with rh as a shorter alias for the same binary. It needs Node.js 22 or newer and has no other dependencies.

Log in

remote login

This runs the OAuth device flow: the CLI prints a short code, opens the verification page in your browser if it can, and waits for you to confirm.

  your code: WDJB-MJHT
  opening your browser:
  https://console.remotehost.ai/device?code=WDJB-MJHT
  no browser here? open that link on any device.

  waiting for you to confirm in the browser  ctrl-c to cancel

Because approval happens in a browser rather than a callback to this terminal, an SSH session on a machine with no browser signs in exactly like a laptop does — open the link anywhere.

The session is written to ~/.config/remotehost/config.json. Access tokens last an hour and refresh transparently, so this is a one-time step per machine. You can skip the interactive prompt entirely by setting REMOTEHOST_TOKEN to a key from remote keys create — which is how CI and agents authenticate.

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:

remote 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:

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

Use remote 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

remote ls

remote attach <name-or-id>   # reconnect to a running sandbox
remote ssh <name-or-id>      # open native SSH
remote sleep <name-or-id>    # put it to sleep (billing stops with it)
remote wake <name-or-id>     # wake it where you left off

Or run remote 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.