Bug Report is a Chrome extension and team workspace for QA. You record a bug once; it writes the report (title, steps to reproduce, actual result, environment) and keeps the console logs, network requests, screenshots and an optional video. Developers press Replay and the same steps run live in their own browser.

How is a live replay different from a screen recording?

A screen recording is a video you have to watch and scrub through. A live replay performs every recorded click, typed value and page change again in the developer's own browser, step by step, with Back, Forward and Pause, so they can open DevTools and inspect the bug while it happens.

How is Bug Report different from Jam, Marker.io or BugHerd?

Those tools capture a bug well: a screenshot or video, and in some of them the console and network. Bug Report captures the same evidence, then goes one step further: the developer presses Replay and the recorded steps run again on the live site in their own browser, and checks QA added while recording say whether the bug is reproduced. The comparison page lists the differences row by row.

Which browsers does Bug Report work in?

Recording works in Google Chrome and in Chromium browsers such as Microsoft Edge and Brave. The report page, the shared links and the team dashboard work in any modern browser.

Does it capture console errors and network requests?

Yes. Every console message, JavaScript error and network request (method, status, headers, request and response bodies for fetch and XHR) is saved with the report, shown in a DevTools-style panel, with secrets such as auth headers, cookies and passwords removed before anything is saved.

Can my AI coding assistant fix the bug?

Yes. Copy for AI turns a report into a ready prompt, and the Bug Report MCP server lets Claude, Cursor or VS Code read your team's bugs with their steps, errors and failed requests, then update the status and comment when the fix is done.

Does Bug Report work with automated tests?

Yes, with Playwright. Add @bugreport/playwright to your config in one line and you get a full test report (retries, steps, errors, trace viewer, trends, flaky tests, failures by cause), and every failed test becomes a bug report with its steps, checks, console, network and video. Create bug report puts it on your dashboard, where the developer replays it in their own browser. The reporter is free and open source (MIT).

Yes. Screenshots, step recordings, live replay, console and network capture and a team workspace for three people are free. Pro adds 30-minute videos with voice and tab sound, instant replay with video, the video timeline and trimming to MP4 or GIF.

Reports stay on your computer until you send them to your team workspace. Passwords, card numbers and one-time codes are never recorded by default, secret headers and tokens are redacted, and private details can be blurred in videos and screenshots.

← All posts

Manual testing

Stop watching bug videos. Replay them.

October 17, 2026 · 5 min read

Most bug reports today come with a video. That's better than a sentence like “checkout is broken”, but anyone who fixes bugs knows the routine: open the ticket, scrub through four minutes of someone else's screen, pause on the one frame that matters, squint at the URL, then try to do it all again by hand. Half the time it doesn't happen on your machine and the ticket goes back with can't reproduce.

A video is evidence. A replay is the bug.

A video shows what happened once, on someone else's computer. What a developer actually needs is to make it happen again, on theirs, with DevTools open. That's what Bug Report does. While QA tests, the extension records every click, typed value, choice, drag, upload and page change, with the elements they happened on. When a developer opens the bug and presses Replay in my browser, those steps run again, live, in their own Chrome.

A bug on the dashboard with Replay in my browser and the video timeline — Replay in my browser, next to the video and its timeline of steps, errors and failed requests.

It's not a video of the replay. It's the real site, doing the real thing. Pause it before the step that breaks. Step back. Go forward one step at a time. Slow it to half speed. Open the network panel and watch the request fail.

“Is it still broken?” gets an answer

While recording, QA can add checks: this heading should say “Welcome back”, this total should be 74, this row should exist. And on the report they mark which failed request or console error is the bug. When the replay finishes it answers: Reproduced, Not reproduced or Inconclusive. After a fix, replay the bug again and you know it's gone, without asking QA to retest.

The report page with steps, the actual result, the Replay card and Reproduced? — The report writes itself: title, steps and actual result; you add what should happen, as checks.

Everything a developer would ask for, already there

Steps to reproduce and the actual result, written from what QA did (QA adds what should have happened)
Console messages and JavaScript errors with their source line
Network requests with headers and request / response bodies, like DevTools
Browser, OS, window size, language and time zone
Screenshots, and a video with voice on Pro, with a timeline of every step and error

Passwords, card numbers and tokens are never saved, and private details can be blurred before anything leaves the browser.

When a video is still the right tool

Visual glitches, animations and “it feels slow” are easier to show than to replay, so Bug Report keeps the video too, and its timeline jumps straight to each step. But for the bugs that end in a ping-pong of “can't reproduce”, give the developer the bug itself.

Try Bug Report free: screenshots, step recordings, live replay and a workspace for three people cost nothing.