Reachpad Cli

reachpad CLI

Run coding agents in durable cloud workspaces: the disk survives the machine underneath, so a paused workspace costs nothing and picks up from its last save. Files survive a pause; running processes do not.

Install

With Homebrew on Apple silicon macOS or x86_64/arm64 Linux:

brew install reachpad/tap/reachpad

With npm, anywhere Node 18+ runs:

npm install -g @reachpad/cli

Or with the checksum-verifying installer:

curl -fsSL https://reachpad.dev/install | sh

Linux x86_64/arm64 (musl, static) and macOS arm64/x86_64. The script fetches the latest release from this repository, verifies its checksum against SHA256SUMS, and installs to `~/.local/bin/reachpad` (override with `REACHPAD_INSTALL_DIR`).

All three deliver the same binary. `@reachpad/cli` is a launcher around it, not a second implementation — see [`npm/README.md`](npm/README.md), which also explains the macOS quarantine problem npm sidesteps.

Get started

Run Reachpad:

reachpad

On first use, the CLI shows a short code, opens WorkOS hosted sign-in, and then lists your workspaces. WorkOS handles the account login and any required MFA or SSO. After approval, Reachpad exchanges the short-lived WorkOS token once and saves a user-scoped Reachpad credential and the production endpoint with mode 0600. No password or authentication factor is entered into Reachpad.

On a remote machine without a usable browser, run `reachpad auth login --no-browser` and open the displayed URL on another device. The manual credential flow remains available from [reachpad.dev/connect](https://reachpad.dev/connect) as a recovery path.

Then create a workspace, work in it, and put it away:

reachpad create scratch
reachpad list
reachpad attach 
reachpad run  -- cargo test
reachpad pause 

`create` prints the workspace id the other verbs take. The name is only a label; there is no lookup by name.

Useful maintenance comma