Read console logs in a bug report
Find the error that caused a bug by grouping console logs, opening a stack trace, and jumping the replay to the moment it fired.
When a bug involves broken JavaScript, the console usually holds the smoking gun. BugMojo captures the full console at capture time, so you can read every log, warning, and error without ever reproducing the bug yourself. This guide shows you how to find the error that matters and trace it back to the exact moment it happened.
Open and filter the console
Open the bug and select the Console tab beneath the Instant Replay. Every captured message appears in time order, tagged as
log,warn, orerror.Click the Errors filter to hide routine logs and show only failures. Add Warnings if an error alone does not explain the bug. This grouping turns a wall of output into the few lines that matter.
Type in the Filter box to narrow further (a component name, a function, or part of the error text) when a busy page produced dozens of messages.
Expand an entry for its stack trace
Click an error to expand it. BugMojo shows the full stack trace (the call path that led to the failure) plus any arguments logged with the message.
Read the trace top to bottom: the first frame is where the error was thrown, and the frames below show who called it. This is usually enough to point at the file and function to fix.
Jump the replay to the moment it fired
Click the timestamp on any console entry. The Instant Replay scrubs to that exact moment, so you can see what the user was doing on screen when the error fired.
Watch the seconds just before the timestamp to catch the click, keystroke, or page change that triggered the failure. Pairing the log with the replay turns "an error happened" into "here is what caused it."
Common questions
Do I have to reproduce the bug to see its console errors?
No. The extension captured the console at the moment of the report, so every log, warning, and error is already attached to the bug. Just open the Console tab.
Can an AI agent read these console logs?
Yes. A coding agent connected over MCP reads the exact same console output, including stack traces, plus the replay context and network requests, so it can diagnose the bug without you copying anything.
Why do some log messages show masked text?
PII redaction runs in the extension before data leaves the browser, so text and inputs are masked by default. That protection also applies to values printed in console logs.
Related articles
- The bug detail page: a guided tourLearn where every part of a bug lives: replay, console, network, environment, activity, and comments.
- Watch a session replayPlay back a bug's DOM session replay, control speed, skip idle time, and jump straight from a log to its moment.
- Inspect the network requests in a bugFind the failed or slow request behind a bug, read its status, timing, and headers, and jump the replay to the moment it fired.
- How AI agents work with BugMojoUnderstand the full loop, from a captured bug to an agent-proposed fix that a human verifies and closes.