Guides

Step-by-step: record network activity in Chrome DevTools and export it as a HAR file, what Chrome 130+ strips by default, and how to capture requests without DevTools.

What a HAR file can leak (cookies, tokens, request bodies, personal data), what Chrome's sanitized export removes and what it doesn't, and a checklist before you send one.

Save Chrome's console output to a file, keep it across reloads with Preserve log, add timestamps, and send it with the rest of the bug.

Three ways to get console errors and failed network requests into Cursor, Claude Code or Codex: a browser the agent drives, a DevTools MCP, or a recorded bug served over MCP.

Stop pasting console errors into Cursor. Use Cursor's built-in browser, Chrome DevTools MCP, or a Roll recording the agent reads with get_console and get_network.

Get browser console errors and network failures into Claude Code with Claude in Chrome, Chrome DevTools MCP, or a recorded bug served from disk by the Roll MCP server.

When to let your agent drive Chrome with DevTools MCP, and when to hand it a recording of a bug that already happened. Profiles, logged-in sessions, and what each one can see.

A copy-paste markdown bug report an AI agent can act on: steps with timestamps, failed requests with status and body, console errors with stacks, all in time order.

Record a Chrome tab and get the console, every fetch/XHR request with bodies, and every click on one timeline. Free, no account, recordings stay on your machine.

Missed the bug because you weren't recording? A rolling buffer keeps the last minutes of video, console and network in memory so you can save it after the fact.

Roll, BrowserStack Bug Capture, Marker.io, Loom and BetterBugs compared with Jam on free limits, pricing, console and network capture, where recordings live, and AI agent access.

Roll and Jam both record a tab with console and network. The differences: where recordings live, pricing ($29 once vs $14 per creator a month), team features, and agent access.