BugReceipt

Capture a clear, privacy-filtered bug reproduction bundle.

BugReceipt turns difficult-to-explain browser problems into clear, reproducible reports. Record a browser tab while BugReceipt collects context developers need to investigate: reproduction steps, console messages, network activity, page details, and browser environment information. Before exporting, review and edit the report, remove unwanted evidence, select useful video frames, annotate screenshots, and highlight relevant console or network details. Key features: • Record a browser tab without microphone or tab audio • Add and edit step-by-step reproduction instructions • Capture supported console messages, errors, warnings, exceptions, and rejected promises • Search console messages and filter by console type • Search network requests and filter by request method • Inspect request payloads and responses in formatted JSON or raw text • Review available request headers with recognized sensitive values redacted • Review recordings and capture important frames • Annotate visual evidence and diagnostic text • Remove individual pieces of evidence before sharing • Download a ZIP containing the Markdown report and included visual evidence • Download console JSON, network HAR, and individual visual evidence separately BugReceipt is local-first. Capture data is stored locally in extension-owned browser storage. Reports are not automatically uploaded or emailed. Exporting creates local files and does not automatically delete the capture. Recognized sensitive diagnostic values—including email addresses, bearer tokens, authorization headers, cookies, API keys, and secret-shaped fields—are filtered locally where supported. Filtering cannot detect every sensitive value, and screen recordings may display private information visible on the page. Review your evidence before sharing it. Diagnostic capture begins when recording starts. Coverage depends on browser support, capture limits, and an active debugger connection. BugReceipt is designed for QA testers, developers, support teams, product teams, and anyone who needs to report a browser issue with more useful context than a screenshot and “it doesn’t work.” Requires Chrome 125 or newer.