Guides · Bug reporting
Screen recorder that captures console and network logs
Updated Sep 23, 2026
Roll is a free Chrome extension that records your tab and keeps the console, every fetch and XHR request with its body, and every click on the same timeline. Stop, and you get one link for a teammate or one bundle your coding agent can read. No account needed to record.
What one recording holds
| Video | The tab (or screen, or window) plus tab audio |
| Console | log, warn, error, uncaught exceptions, unhandled promise rejections, with stacks |
| Network | Every fetch and XHR request with status, timing and bodies, saved as HAR 1.2 |
| User actions | Clicks, typing, submits, navigations, tab switches |
| Environment | URL, browser, OS, viewport, timezone |
| timeline.md | All of the above merged in time order, for people and coding agents |
Everything is on one clock. In the viewer, scrub the video and the console and network panes follow; click a failed request and the video jumps to the moment it fired. See it in the live demo recording, no install needed.
How it works
- Add Roll to Chrome and pin it. No account.
- On the page that breaks, click Record (or press ⌘⇧Space / Ctrl+Shift+Space).
- Reproduce the bug. Pause if you need to; paused time is cut from the timeline.
- Stop. The recording opens in the viewer.
- Share a link, download the bundle, or hand it to your coding agent through the local MCP server.
Missed it? Rewind
Turn on Rewind and Roll keeps the last 2 minutes in memory, video, console and network included. When something goes wrong, press Save and you have it, without reproducing anything. More in recording the last 2 minutes.
Built for handing to a coding agent
Every recording is a .jam bundle: plain JSON, JSONL, a HAR file and WebM video in a folder. A local MCP server serves it to Cursor, Claude Code and Codex, so the agent reads the failed request body and the stack instead of guessing from a video. Setup is one line; see giving your agent browser logs.
Private by default
- Recording never contacts our servers. Recordings stay on your machine.
- Authorization, cookie and API-key headers are dropped at capture. Password, card and one-time-code fields are never recorded.
- Publishing a link is opt-in, per recording. Free links delete after 7 days.
Pricing
Free covers most people: unlimited recordings up to 5 minutes, 2-minute Rewind, MCP, and 7-day links. Pro is $29 once, not a subscription: unlimited length, 5-minute Rewind, and links that stay until you delete them. Comparing tools? See Jam.dev alternatives.
Just need the raw files?
You can get the same data by hand from DevTools: save the console and export a HAR. It works; it's just three files and no shared timeline.
Questions
Is it free?
Yes. Unlimited local recordings up to 5 minutes, 2-minute Rewind, the MCP server, and share links that last 7 days, with no account. Pro is $29 once for unlimited length, 5-minute Rewind and links that stay until you delete them.
Does it record my whole screen?
Your choice. Tab mode records only the current tab and starts instantly. Screen mode uses Chrome's share sheet once and then follows you across tabs and windows.
Which network requests does it capture?
Every fetch and XHR request the page makes, with headers and text request and response bodies up to 64KB each. It does not log images, stylesheets or the initial page load, and it never reads streaming responses.
Where do recordings go?
Nowhere until you say so. They're saved in your browser and, if the MCP server is running, in ~/.trace/jams on disk. Publishing a link is opt-in, one recording at a time.
Does it work in Edge, Brave or Arc?
Roll is built and tested for Google Chrome. Other Chromium browsers can install Chrome Web Store extensions, but tab capture behavior varies and they aren't officially supported.