{"slug": "reachpad-cli-spin-up-free-sandboxes-in-seconds-to-develop-and-host-apps", "title": "Reachpad CLI – Spin up free sandboxes in seconds to develop and host apps", "summary": "Reachpad has released a command-line interface (CLI) that lets developers spin up free cloud sandboxes in seconds to develop and host apps, with durable workspaces that survive machine pauses. The CLI, installable via Homebrew, npm, or a checksum-verifying script, supports macOS and Linux and integrates with WorkOS for authentication. It is source-available under copyright of Tako Research, with release binaries built from the repository and signed build-provenance attestations.", "body_md": "Run coding agents in durable cloud workspaces: disk and memory survive the machine underneath, so a paused workspace resumes mid-session.\n\nWith Homebrew on Apple silicon macOS or x86_64/arm64 Linux:\n\n```\nbrew install reachpad/tap/reachpad\n```\n\nWith npm, anywhere Node 18+ runs:\n\n```\nnpm install -g @reachpad/cli\n```\n\nOr with the checksum-verifying installer:\n\n```\ncurl -fsSL https://reachpad.dev/install | sh\n```\n\nLinux x86_64/arm64 (musl, static) and macOS arm64/x86_64. The script fetches\nthe latest release from this repository, verifies its checksum against\nSHA256SUMS, and installs to `~/.local/bin/reachpad`\n\n(override with\n`REACHPAD_INSTALL_DIR`\n\n).\n\nAll three deliver the same binary. `@reachpad/cli`\n\nis a launcher around it, not\na second implementation — see [ npm/README.md](/Reachpad/reachpad-cli/blob/main/npm/README.md), which also\nexplains the macOS quarantine problem npm sidesteps.\n\nRun Reachpad:\n\n```\nreachpad\n```\n\nOn 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.\n\nOn a remote machine without a usable browser, run `reachpad auth login --no-browser`\n\nand open the displayed URL on another device. The manual\ncredential flow remains available from\n[reachpad.dev/connect](https://reachpad.dev/connect) as a recovery path.\n\nThen list, create, or attach to a workspace:\n\n```\nreachpad ws list\nreachpad ws create --name scratch\nreachpad attach <workspace-id>\n```\n\nUseful maintenance commands:\n\n```\nreachpad doctor\nreachpad update\nreachpad completions bash\nreachpad completions zsh\nreachpad completions fish\n```\n\n`reachpad update`\n\nrespects how Reachpad was installed: Homebrew installs are\ndirected to `brew upgrade reachpad`\n\nand npm installs to `npm install -g @reachpad/cli@latest`\n\n, while installer-managed binaries are updated in place\nafter the release checksum is verified. Whoever installed the binary owns it —\na second writer is how a working install becomes a broken one.\n\nDocs: [reachpad.dev/docs/cli](https://reachpad.dev/docs/cli)\n\nThis repository carries the full CLI source: the `reach`\n\npackage (shipped\nbinary name `reachpad`\n\n) and its three library crates (`proto`\n\n, the frozen\nwire protocol; `authz`\n\n, Biscuit verify and offline attenuation; `runtime`\n\n,\nthe config and tracing shell). Release binaries are built from this source\nby [the release workflow](/Reachpad/reachpad-cli/blob/main/.github/workflows/release.yml) on GitHub's\nrunners, and every release carries a SHA256SUMS the install script verifies.\nTo build it yourself (needs Rust and `protoc`\n\n):\n\n```\ncargo build --release -p reach\n./target/release/reachpad --version\n```\n\nEvery release tarball also carries a signed build-provenance attestation, so the chain is checkable without trusting us:\n\n```\ngh attestation verify reachpad-<target>.tar.gz --repo Reachpad/reachpad-cli\n```\n\nThat proves the bytes came out of this repository's release workflow at the commit the tag names. It rests on no key of ours — the signing identity is a short-lived credential minted for that one workflow run, and the record is in a public transparency log.\n\nThe snapshot is synced from a private monorepo on every release, so file an\nissue rather than a PR for changes; a PR here would be overwritten by the\nnext sync (the sync script and its header in `Cargo.toml`\n\nsay the same).\nThe CLI is an ordinary client of a public API: it holds no platform secrets\nand nothing it does is privileged (the server refuses anything a stranger\ncould not do).\n\nSource-available; copyright Tako Research, all rights reserved.", "url": "https://wpnews.pro/news/reachpad-cli-spin-up-free-sandboxes-in-seconds-to-develop-and-host-apps", "canonical_source": "https://github.com/Reachpad/reachpad-cli", "published_at": "2026-08-25 23:59:10+00:00", "updated_at": "2026-08-26 00:14:22.092689+00:00", "lang": "en", "topics": ["developer-tools", "ai-tools"], "entities": ["Reachpad", "Tako Research", "WorkOS", "Homebrew", "npm", "GitHub"], "alternates": {"html": "https://wpnews.pro/news/reachpad-cli-spin-up-free-sandboxes-in-seconds-to-develop-and-host-apps", "markdown": "https://wpnews.pro/news/reachpad-cli-spin-up-free-sandboxes-in-seconds-to-develop-and-host-apps.md", "text": "https://wpnews.pro/news/reachpad-cli-spin-up-free-sandboxes-in-seconds-to-develop-and-host-apps.txt", "jsonld": "https://wpnews.pro/news/reachpad-cli-spin-up-free-sandboxes-in-seconds-to-develop-and-host-apps.jsonld"}}