Record it yourself
Show a bug or walk through a change.
Sign in, then choose Record my screen. Allow your browser to capture a tab, window, or screen. Capture choices depend on your browser. You can add microphone narration and record for up to 10 minutes.
Stop and preview the video before saving. Saving uploads it to your workspace; create a share link separately when you want someone else to view it. To invite someone else to record without a Rill account, create a recording request.
What each route captures and shares
| Route | Captured context | Access |
|---|---|---|
| Record it yourself | Screen video and optional microphone narration. No automatic console or network diagnostics. | Preview before upload. Saved to your workspace; sharing is a separate action. |
| Record an agent | Supported Chromium browser video, console messages, network requests, and interaction timeline. Network bodies depend on capture settings. | Local CLI recordings upload to Rill. Anonymous and connected-local recordings get an unlisted share link when ready; connecting an account does not make those links private. |
| Let Rill run it | Cloud browser video and captured console, network, and timeline events. | Guest results are available in the originating browser and through a secure emailed link for seven days. Signed-in runs start private to your workspace. Create a share link separately to let others view it. |
Anyone with an active share link can view the recording, included diagnostics, and comments. Rill does not mask sensitive content in the video. Review the capture before sharing. Share-link expiry is separate from recording retention. Read plans and access details.
A recording shows captured behavior. Error counts are browser observations, not a verdict that the task passed or failed.
Let Rill run it
Run a browser task on a public website.
Enter a public website URL, a task, and your email on the homepage or browser check page, then choose Run my free check. The guest trial browses for up to two minutes without website credentials or form submissions. Watch the recording and inspect its diagnostics without signing in. Your result and any share link expire after seven days; sign in with the same verified email to keep the recording. Signed-in browser runs continue through your dashboard.
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. Signed-in and CLI cloud recordings start private to your workspace; 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 an agent.
For this local recording path, you’ll need macOS, Linux, or Windows, 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-cliThe browser runs in your agent’s environment and can reach localhost. Remote encoding is the CLI default: captured frames upload to Rill to build the video. With local encoding, FFmpeg builds the video before upload. Video and captured diagnostics are stored in Rill. Remote encoding does not use cloud-run credits.
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. The recording and captured diagnostics still upload to Rill. See the encoding guide for setup and recording limits.
Connect
Save anonymous recordings to your account.
rill connect --email you@example.comrill doctorYour 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. The connection also lets the agent create and read workspace recordings. Review the access request before approving. Connecting does not buy a subscription. 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
Tell your agent what to record.
Use an agent with browser tools that can connect to the Chromium browser Rill provides. Paste the prompt in your project to check setup and record a flow. Anonymous capture uploads to Rill with an unlisted link that anyone holding it can open. Use suitable test data.
Read and follow the Rill skill at https://userill.dev/skill.md for this project. Install the required Rill tools if needed, following this environment's setup and approval rules. Record one useful browser flow for this project. Follow our current task when clear; otherwise choose a short, non-destructive smoke test. Use any specific app URL, steps, test data and expected behavior I supplied. Check prerequisites and confirm that you can control the browser Rill provides. Use the existing app setup. Ask if the target is unclear, application changes are needed, or an action needs approval. Do not submit payments or make destructive changes without approval. Start anonymously if I am not connected, following the existing skill and approval rules. Before anonymous capture, explain that the recording uploads to Rill with an unlisted link that anyone holding it can open. Use suitable test data and avoid sensitive content. Stop the recording, wait for processing, and verify that it plays. Return the link, expiry, tested version if available, what you checked, what you observed, and anything you could not verify. Report failed checks or processing problems explicitly.
Read the Rill skillFor a bug you’re fixing:
Record the bug in the current version before changing code. After an approved fix, record the same steps and test data again. Verify both recordings play. Return their links, expiry, tested versions, what changed, and anything not checked. Ask if either version is unavailable.Your agent drives the browser and Rill captures the run. 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.