RillDocs
Sign in
Skip to guide

Review and share

Make the recording useful to someone else.

Watch the steps, find the moment that matters and send enough context for the next person to act.

Watch the recording

Open a recording from your library or the link returned by Rill. If it is still preparing, wait for Ready. Play the video and check that it shows the intended page and steps.

Pause at the important moment. Use a timestamped comment to explain what happened or ask a question. Record the flow again if you need to check a new version; reviewing an existing video does not run your app again.

Understand the browser details

Some recording methods include diagnostics: captured information from the browser. Use them to investigate what happened around a moment in the video.

ViewWhat to look for
ConsoleMessages and errors reported by the recorded page.
NetworkCaptured requests, status codes and failures. A failed request may explain a missing result.
TimelineCaptured browser events and interactions, when available.

Chrome recording saves bounded console messages and request details, without request headers or bodies. Screen recordings and uploaded videos do not gain diagnostics after upload. Local-agent and cloud captures have their own capture settings. See what each method records.

An error may be unrelated to the task. Missing diagnostics do not establish that no error occurred. Use the video, the task and the captured details together.

Share with someone

  1. Review the video, diagnostics and comments for anything you should not share. Video is not automatically masked.
  2. For a private workspace recording, choose Create share link.
  3. Copy the active link and send it with a short explanation of what to watch.

Anyone with an active share link can view the recording and included diagnostics and comments. A private recording page URL does not grant access to someone outside your workspace.

Local CLI recordings, including anonymous ones, already receive an unlisted share link when ready. Connecting them to an account preserves those URLs; it does not make them private. Link expiry and recording retention are different. See access and expiry.

Add the useful context

Recording handoff template
Recording: <Rill link>
Watch: <timestamp or short range>
Task: <what you tried>
Expected: <what should happen>
Observed: <what actually happened>
Version: <commit or build, if known>
Not checked: <what this recording does not cover>

For a fix, record the same steps and test data before and after the change. Keep the two recordings clearly labelled. For an agent handoff, include the link and ask for observations grounded in the captured evidence.