Browser recording

Needs

Chrome or a Chromium browser. No account.

Produces

A local session with a timeline, screenshots and captured request data

Settings

Capture detail, redaction rules, telemetry filtering, API spec

When to use it

Use it whenever someone has to understand a bug they did not see: a QA finding headed for a developer, a product review note, or a failure you want an AI coding agent to trace. The recording replaces the usual pile of screenshots, copied console lines and “I clicked around a bit” in the ticket.

What gets captured

• Interactions. Clicks, typing, scrolls, text selections and page navigations, each with a short description of the element involved. Password fields are never recorded as text.
• Console. Log output, warnings, errors and uncaught exceptions from the recorded tabs.
• Network. Requests and responses, including headers, status, timing and bodies up to a size cap. Capture uses Chrome’s debugging protocol, which is why Chrome shows a “started debugging this browser” banner while you record.
• Tabs the app opens. When the recorded page opens a new tab or window, that tab joins the session. Switching back and forth stays on the same timeline.
• Uploaded files. Files you pick in the page’s file inputs are kept with the session. Files up to 25 MB are stored whole by default; larger ones keep only their name, type and size.
• Screenshots and optional video. Covered on Screenshots and video.

Choosing capture detail

The Record button has a detail control with four presets. Each one changes how often screenshots are taken, whether hovering is recorded, and how much of each request body is kept.

Analytics and telemetry requests are still captured, but by default they are left out of Standard and smaller exports, so the network section stays about your app. Turn on API spec in capture settings and the export also includes an openapi.json inferred from the JSON traffic you exercised.

Limits

• Chrome blocks extensions on its own pages (such as chrome:// and the Chrome Web Store), so those cannot be recorded.
• Only tabs in the session are recorded. A tab you open yourself from the address bar is not adopted.
• Redaction runs on headers, bodies and URLs as they are captured, but it is pattern-based. Read Local storage and redaction before recording production data.