Question 1

What is Bug Report?

Accepted Answer

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.

Question 2

How is a live replay different from a screen recording?

Accepted Answer

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.

Question 3

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

Accepted Answer

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.

Question 4

Which browsers does Bug Report work in?

Accepted Answer

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.

Question 5

Does it capture console errors and network requests?

Accepted Answer

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.

Question 6

Can my AI coding assistant fix the bug?

Accepted Answer

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.

Question 7

Does Bug Report work with automated tests?

Accepted Answer

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).

Question 8

Is Bug Report free?

Accepted Answer

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.

Question 9

Is my data safe?

Accepted Answer

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.

Feature	Bug Report	Jam	Marker.io	BugHerd	Loom
Screenshot with markup	Yes	Yes	Yes	Yes	No
Video of the bug	Voice + tab sound (Pro)	Yes	Session replay	Video feedback	Yes
Steps to reproduce written for you	Yes	AI-suggested	No	No	No
Console logs and network requests	With request / response bodies	Yes	Opt-in	No	No
Checks on the page while recording	Yes	No	No	No	No
Replay the steps live in the developer's own browserSession replay and video show what happened; a live replay performs the steps again on the real site.	Pause, Back, Forward, 0.5x–2x	No	No	No	No
Answer after a replay: Reproduced / Not reproduced	Yes	No	No	No	No
Failed automated tests become bug reports	Playwright	No	No	No	No
AI coding assistants (Copy for AI, MCP)	Yes	AI tooling	No	MCP	No
Jira, Linear, GitHub	Coming soon	Jira, Linear	Yes	Yes	Yes
Free plan	Yes	Yes	Trial, from $39 / month	Trial, from $42 / month	Yes

Feature	Bug Report reporter	Playwright HTML report	Allure Report	ReportPortal	Currents
Steps, errors, screenshots and video per test	Yes	Yes	Yes	Yes	Yes
Playwright trace viewer in the report	Yes	Yes	Attachment	Download	Yes
History, trends and flaky tests	Folder kept between runs	No	Needs history folder	Yes	Yes
Failures grouped by cause	Yes	No	Categories	ML auto-analysis	No
Needs a server or account	No (dashboard optional)	No	No	Self-host or SaaS	Cloud service
Price	Free, MIT	Free	Free, open source	Free self-hosted	Paid
A failure turned into a filled-in bug report (steps, checks, console, network, video)	Yes	No	No	No	No
The developer replays the failure live in their own browserPlaywright's trace viewer (which our report includes) replays a recording of the test; Bug Report also runs the steps again on the live site.	Yes	No	No	No	No

Everyone captures the bug.
We replay it.

Live replay, not another video

Automation that files its own bugs

Manual testing: bug capture tools

Automation testing: Playwright reports

How we compared

Stop watching bugs.
Start replaying them.

Everyone captures the bug. We replay it.