RightSide Docs
Get started

From zero to agent-ready.

Use the stable installer, approve bounded access in your browser, and let the installer connect the coding clients it detects.

Requirements

  • Invite-only closed-beta access for your account.
  • Linux x64, x64 WSL2, or Apple silicon macOS.
  • Node.js 22.13 or newer.
  • Claude Code, Codex, or both for automatic MCP registration.
Disposable beta data. Closed-beta projects and data may be erased before public beta. Do not use RightSide as the only copy of important work.

1. Install

curl -fsSL https://get.rightside.host/install | sh

The installer works under ~/.local by default and does not use sudo. The bootstrap downloads the immutable release and verifies its manifest-pinned checksum before execution, opens browser authorization, registers supported clients, and runs diagnostics.

Trust boundary. The one-line form trusts HTTPS delivery of the bootstrap. The bootstrap verifies the immutable installer and standalone archive against manifest-pinned sizes and SHA-256 digests before execution.

Or ask Claude Code or Codex

Install and set up RightSide on this machine. Verify that Node.js is 22.13 or newer and that this is Linux x64, WSL2 x64, or Apple silicon macOS. Run `curl -fsSL https://get.rightside.host/install | sh`, let me complete browser authorization, and never ask me to paste a token, device code, cookie, or secret into chat. Then run `rightside doctor --json`. If it passes, inspect this project and deploy it with RightSide. Do not claim success until RightSide returns an HTTPS URL and you verify that URL responds correctly.

2. Authorize separately if needed

rightside login --url https://api.rightside.host

For a headless environment, set RIGHTSIDE_NO_BROWSER=1. The CLI prints the verification URL instead of attempting to open a browser.

3. Register your coding client

rightside install claude
rightside install codex

Registration contains the MCP executable path and configuration location. It never contains your bearer token.

4. Verify

rightside doctor
rightside doctor --json

Agents should prefer --json. A warning can mean an optional client is absent. An error means the affected path is not ready.

5. Deploy

cd your-project
rightside deploy . --name my-app

Do not report completion just because the command started or a container built. Capture the returned HTTPS URL and verify the final status.