Rill
Sign up now

Getting started

Two ways to record.
Start with a task.

Give Rill a task to run in the cloud, or record the browser your coding agent controls. Both keep video and diagnostics together.

Cloud recording

Give Rill a task.

Enter a public website URL and prompt on the homepage, then sign in with GitHub or Google. Rill starts the browser run automatically and shows its progress in your dashboard. Use New cloud run for your next recording.

Or use the CLI with Node.js 22 or newer:

npx @runalabs/rill-cli record https://example.com -p "Explore the pricing page"

The CLI prompts you to sign in the first time. Cloud runs need no local Chrome, ffmpeg, or AI API key. Your recording starts private; create a share link separately when you want someone else to view it.

For websites that require login, configure a website account in Settings and pass its name with --account name. Website login is separate from signing into Rill. See the CLI reference for the supported login flow.

Install

Record your agent’s browser.

For this local recording path, you’ll need macOS or Linux, Node.js 22 or newer, and Google Chrome or Chromium. Run these commands in the environment where your agent works.

npm install --global @runalabs/rill-cli

Anonymous recording uses local encoding and requires FFmpeg. Existing account credentials can use remote encoding. Your browser stays local and can access localhost. Video and diagnostics upload when recording stops. For remote encoding, raw frames upload instead; it adds no charge or cloud-run credit usage.

Already using Rill? Update with npm install --global @runalabs/rill-cli@latest, then run rill doctor. Remote encoding requires CLI 0.1.10 or newer.

To encode locally, install FFmpeg and use rill record start --encoding local. See the remote encoding guide for setup and recording limits.

Connect

Start anonymously. Connect to keep it.

rill connect --email you@example.comrill doctor --encoding local

Your first local recording can start without signing in. To claim unexpired anonymous recordings, run connect, open its link, sign in with the same email, enter the code, and approve. Connecting is not a paid upgrade. See plans and limits for the anonymous allowance and expiry.

If a check fails, follow its recovery instructions. For headless environments or Linux keyring setup, see authentication in the CLI reference.

Start recording

Describe the flow. Get the evidence.

Paste this into your coding agent inside your project. It installs and reads the Rill skill, checks setup, and starts a useful local recording. See the agent quickstart for the full flow.

PASTE INTO YOUR CODING AGENT INSIDE YOUR PROJECT

Install and read the Rill skill at https://userill.dev/skill.md for this project, then use it to record one useful browser flow. Follow our current task when clear; otherwise choose a short, non-destructive smoke test. Check prerequisites and browser control, start anonymously if I’m not connected, and return a playable recording link with what you checked and when it expires. Ask if the target is unclear or application changes are needed.

Read SKILL.md ↗

For a bug you’re fixing:

Use Rill to record this bug before the fix, then record the same flow after the fix. Return both links and explain what changed.

Your agent starts the browser, performs the flow, and uploads the recording. Open the returned link to watch the run and inspect its console logs, network requests, and interaction timeline.

Use an agent with browser tools that can connect to an existing Chromium browser. Follow the skill installation guide, agent quickstart, and plans and limits.

Need individual commands, troubleshooting, or advanced setup? Open the CLI reference.