Use cases · Session replay
Session replay for debugging
Stop debugging from a screenshot and a shrug. BugMojo records the DOM with rrweb session replay and bundles it with the console logs, network requests, and a screenshot in one click — so engineers and QA reproduce bugs from exactly what happened, not from a second-hand description.
Free plan — $0 forever. Quick Capture and session replay included.
Why bugs bounce back as “cannot reproduce”
A screenshot and a few remembered steps are not enough to reproduce a modern web bug. The sequence, the timing, and the state that caused the failure are exactly what a static report leaves out.
"Works on my machine"
A screenshot freezes one instant. It can’t show the three clicks, the stale form state, or the race that produced the failure — so the bug lands back in your queue marked "cannot reproduce."
Reproduction is a scavenger hunt
Engineers spend the first hour of every ticket reconstructing steps: which build, which viewport, which account, what was in the console. That time is pure overhead, paid on every bug.
The evidence is already gone
By the time someone files the report, the console has scrolled, the failed request is out of the Network tab, and the exact DOM state is unrecoverable. You’re debugging a memory, not a fact.
Context lives in three places
A screenshot in one tool, a HAR export in another, console text pasted into a ticket. Nobody stitches them back together, so the report is never quite reproducible.
How BugMojo turns a replay into a reproducible bug
Every pain above maps to a capability that ships in the extension. The replay is never alone — it arrives with the signals engineers actually need to fix the bug.
Screenshots freeze one instant
One-click rrweb DOM replay
rrweb records the DOM and every mutation — clicks, inputs, scrolls, route changes — as a lightweight event stream, not a video. Scrub the replay to watch the exact sequence that led to the bug, then step frame by frame through the moment it broke. No heavy video files by default: just the DOM, faithfully replayed, plus an optional real-pixel tab video from the Chrome extension when a canvas or chart needs it.
The evidence is already gone
Console + network + screenshot, captured together
The same click that records the replay also grabs the console logs, the network requests, and a screenshot — bundled into one bug. The failed request, the thrown error, and the visual state are all preserved at the instant of capture and time-aligned with the replay, so nothing scrolls away before you look.
Replays can leak sensitive data
Client-side PII redaction
Redaction runs in the browser, before anything leaves the page. Input values and password fields are masked during recording, so sensitive content is never transmitted to or stored by BugMojo. You get a reproducible replay without shipping user data off the device.
Agents can’t see what a human saw
MCP for AI coding agents
BugMojo ships an MCP server, so AI coding agents like Claude and Cursor can read a bug and its full context — the replay events, console output, and network activity — directly. An agent triages or drafts a fix from the same evidence an engineer would open, not a one-line summary.
Setup friction kills capture
Quick Capture, zero setup
Quick Capture needs no project, no company, no configuration. Anyone — a teammate, a beta user, support — installs the extension and files a complete, reproducible bug in one click. The context comes along automatically instead of being reconstructed later.
Bugs stall waiting on a human
Assign to a human or an agent
Every bug uses a polymorphic assignee: route it to a human MEMBER or to an AGENT. AI agents never consume human seats, so you can hand triage or a first-pass fix to an agent and keep engineers on the work that needs them.
From bug to fix in four steps
- 01
Reproduce or catch it live
When the bug happens — in your own testing or on a teammate’s screen — click the BugMojo extension. rrweb has already been recording the DOM, so the steps that led here are captured, not remembered.
- 02
Capture the full context in one click
That single click bundles the replay with the console logs, the network requests, and a screenshot. PII is redacted in the browser first, so the report is complete and safe before it ever uploads.
- 03
Hand it to a human or an agent
Assign the bug to an engineer or to an AI agent. Whoever opens it lands on the exact replay, the failing request, and the error — no follow-up questions, no "which build was this?"
- 04
Fix from evidence, not description
Scrub to the moment it broke, read the aligned console error, inspect the request that failed. An MCP-connected agent can read the same context to triage or draft a fix. Reproduction is done before debugging starts.
What's in every capture
DOM first, video optional
rrweb replays the actual DOM as an event stream — small to store, precise to scrub, and inspectable frame by frame. The Chrome extension can add a synced real-pixel tab video when a canvas or chart needs it.
Time-aligned signals
Console and network are captured alongside the replay, so an error and the request behind it line up with the moment on screen.
Screenshot on capture
A screenshot is grabbed at the instant of capture, giving triagers the visual state at a glance before they open the replay.
Redacted before upload
Input and password masking runs client-side, so replays stay reproducible without carrying user data off the browser.
Agent-readable via MCP
The MCP server exposes a bug’s replay, console, and network context to AI coding agents in a form they can act on.
Zero-setup capture
Quick Capture files a full report with no project or account configuration — friction that would otherwise lose the bug.
Session replay is on the free plan
The Free plan is $0 forever and includes Quick Capture and session replay. Pro is $12 per user / month and adds MCP-powered AI agents so coding agents can read a bug's full context. Team is $24 per user / month and adds SSO and audit logs. AI agents never consume human seats.
Frequently asked questions
- What is rrweb session replay, exactly?
- rrweb is an open-source library that records the DOM and its mutations — clicks, inputs, scrolls, route changes — as a compact event stream, then replays them faithfully. The replay itself is not a screen video — it is an event stream, so it stays small and inspectable. Because it replays the real DOM, you can scrub the timeline and step through the exact sequence that produced a bug. If you also need real pixels (canvas, WebGL, embedded video), the Chrome extension can record an optional tab video that plays back in sync with the DOM replay.
- Why is a replay better than a screenshot or a written description?
- A screenshot captures a single instant and a description captures someone’s recollection of the steps — both drop the sequence, the timing, and the state that actually caused the failure. A replay preserves the whole path to the bug, so engineers reproduce from what happened instead of guessing, and "cannot reproduce" stops bouncing tickets back and forth.
- Does the replay include console and network data?
- Yes. A single capture bundles the rrweb replay with the console logs, the network requests, and a screenshot, time-aligned so a thrown error and the request behind it line up with the moment on screen. You do not export a separate HAR file or paste console text by hand — it all arrives in one bug.
- Is sensitive data captured in the replay?
- PII redaction runs client-side, in the browser, before anything leaves the page. Input values and password fields are masked during recording, so masked content is never transmitted to or stored by BugMojo. You get a reproducible replay without shipping user data off the device.