Show what happened in your app.
Show what happened in your app.
Explain a bug, demonstrate a change, or review a browser check. Record it yourself, capture any agent that can drive a browser, or give Rill a URL and a task to run.
1. 1Website 2. 2Task 3. 3Sign in
Public website URLSee an example recording
Describe the task →
Try a public demo:Sauce DemoTodoMVCThe Internet
OrRecord my screenRecord my agentCompare the three ways
A browser run, from start to finishMade with Rill
media loading
Play Pause
Play Pause 10 Seek backward 10 Seek forward Mute Unmute
0:00 / 0:00 1x Playback rate Enter fullscreen mode Exit fullscreen mode
Use the browser agent you already work with
- Codex
- Claude Code
- Cursor
- Windsurf
- Antigravity
- Gemini CLI
- GitHub Copilot Browser connection requirements
- Record it yourselfBug reports that show the problemRecord the bug as it happens instead of writing steps from memory.
- Record it yourselfRecordings from customers and clientsAsk someone outside your team to show you what they see.
- Record an agentReviewing your coding agent’s workCome back to recordings of what your agent checked in the browser.
- Let Rill run itChecking a public siteHand Rill a URL and a task, and watch the run afterwards.
- Record an agentHanding context to an agentGive an agent the recording and the details behind it.
- Record it yourselfWalkthroughs of a changeShow reviewers and stakeholders what changed.
How it works
Make a recording. Make it useful to the next person.
Choose how to record, review what happened, and share the result with someone who needs the context.
1. 01
Choose how to record
Record it yourself, record an agent, or let Rill run a browser task.Record it yourselfCapture a bug or walk through a change in your app.Sign in, choose a screen capture surface, and preview before upload. Screen recordings do not capture browser diagnostics. Record my screen→
Record an agentKeep a recording of the browser work your agent is already doing.Set up the Rill CLI and connect your agent’s browser tools. The browser runs in the agent’s environment; recordings upload to Rill. Record my agent→
Let Rill run itGive Rill a public URL and a task to run in a cloud browser.Sign in to start a task. Cloud-run credits apply separately from recording and storage allowances. Run a browser task→ 2. 02
Show the steps that matter.
Replay a bug, walk through a change, or review a browser check. Keep the recording with the issue, update, or conversation it explains. Watch the example
Browser recording Playback + timeline
3. 03
See the browser activity behind the recording.
When diagnostics are captured, inspect console messages, network requests, and browser events alongside the video. They add context to the behavior you can see. See what each recording mode captures Console / Network / Timeline Illustrative 00:04Navigate`/pricing` 00:05GET`/api/plans 200` 00:08Console`Request failed` 00:08GET`/api/usage 500` Use the captured details to decide what to check next. 4. 04Give the next person the context.
Send a recording someone can watch. When browser diagnostics are included, a teammate or agent can inspect those details too. Read recordings with your agent ↗A recording with its captured context
VideoConsoleNetworkTimeline Review the recording before sharing. Anyone with an active share link can view it.Use cases
What people record with Rill.
Record an agent
Keep a recording of the work your agent does.
Use your existing browser-capable agent to record a bug, a change, or a browser check. The browser runs in the agent’s environment, so it can reach the apps that environment can access.
Paste into your agent in the project you want to record
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.
Copy recording promptCopy recording promptRead the Rill skill
Before you record
A few practical details.
Find setup steps and capture limits in the docs.
01
What happens when I give Rill a URL and a task?
+
Rill opens the public site in a cloud browser, follows your instructions, and records the run. You can watch the recording and inspect captured diagnostics. A recording shows that run; it does not establish that every part of the app works.
02
What do I need to get started?
+
To record your screen, sign in and choose a capture surface in your browser. For a task run by Rill, enter a public URL and task, then sign in. You do not need a local browser tool or your own AI API key for a cloud task. Recording an existing agent requires the Rill CLI and a supported browser connection.
03
Can I record the agent I already use?
+
Yes, if it can connect to a supported browser through Rill’s recording workflow. Your agent drives the browser; Rill captures the run. You can also ask an agent to submit a task for Rill’s cloud browser.
04
Can I record localhost or a private app?
+
Record your screen, or use the existing-agent route in an environment that can reach the app. Agent recordings upload to Rill. The URL-and-task form on this site is for publicly reachable websites.
05
Can I record an app that requires login?
+
Rill’s cloud runs can use a separately configured website account through the CLI. Signing in to Rill does not sign in to your app. Saved-account login does not support CAPTCHA, multi-factor authentication, or SSO. Do not put passwords in the task prompt. Saved-account setup →
06
Who can see a recording?
+
Cloud and signed-in screen recordings start private to your workspace. Anonymous agent recordings upload with an unlisted link. Anyone with an active share link can view the recording and its included diagnostics. Review what was captured before sending a link.
07
What’s included in the Free plan?
+
Free includes recording and storage allowances, plus monthly cloud-run credits for tasks run by Rill. Monthly credits reset on the first of each month (UTC). See Pricing for current allowances. View pricing →
08
Can I record it myself?
+
Yes. Choose Record my screen to capture a tab, window, or screen for up to 10 minutes, subject to your browser’s capture support. You’ll see a preview before the video uploads.
Your next recording