Documentation

Quickstart

Create an account, enroll a machine, and open a remote shell.

Requirements

  • An RC account. The OhRats-managed service supports public passkey signup.
  • A passkey-capable browser for account creation and sensitive approvals.
  • A Linux, macOS, or Windows AMD64 machine to enroll.

Create an account

  1. Open Create account.
  2. Choose your RC user name.
  3. Create a passkey when the browser asks.

The passkey is the account credential. RC does not use account passwords. Every new account receives its own Personal workspace; invitation signup also joins the invited workspace.

Enroll a machine

  1. Sign in and open Devices.
  2. Choose Enroll device and select a workspace you own and the target platform: Linux / macOS or Windows (PowerShell).
  3. Choose Create enrollment commands.
  4. Copy the new-install command, or the already-installed command if RC is present. Run it in a terminal on Linux/macOS or in PowerShell on Windows.

The generated command contains a one-time enrollment token. It downloads and checksum-verifies the current GitHub Release, enrolls the machine, and installs a per-user background service.

The service is a LaunchAgent on macOS, a user systemd service on supported Linux systems, and a per-user Task Scheduler task on Windows. The Windows user must remain logged in for the Node to run. Linux/macOS use install.sh; Windows uses install.ps1.

Verify the Node

$rc status

On Windows, use the installed executable directly if it is not on your PATH:

>& "$env:LOCALAPPDATA\OhRats\RC\bin\rc.exe" status

The command shows local enrollment and the hosted device state. The Devices page should show the same machine as online.

Open a remote shell

You can open a terminal from the device page in the browser, or use the CLI:

$rc login
$rc devices
$rc shell DEVICE

login opens RC for passkey approval. The resulting CLI authorization defaults to until revoked.

For standard OpenSSH tooling, register a public key with rc ssh-key add and add the output of rc ssh-config to your SSH config.

Next

  • Security model explains RC Lock and encrypted control.
  • Authentication covers passkeys, CLI sessions, API keys, and MCP OAuth.
  • CLI, MCP, and API contain interface-specific reference material.