Clear browser bug reports, with the evidence included.

Record the affected tab, collect console and network context, add reproduction steps, and review everything before exporting a local report.

Version 0.3.0 is the latest version.

Start on the page where the wording or behavior feels wrong.
Local-first No account required No automatic uploads Review before sharing

Everything needed to reproduce the problem.

BugReceipt keeps the human steps and browser evidence together, so developers receive context instead of another vague report.

01

Screen recording

Record the selected browser tab without microphone or tab audio.

02

Console evidence

Keep errors, warnings, exceptions, and rejected promises with the report.

03

Network activity

Review failed requests, status codes, timing, and supported filtered responses.

04

Reproduction steps

Add the exact human actions needed to reproduce the problem.

05

Review before export

Remove evidence, select frames, annotate screenshots, and highlight diagnostics.

06

Local export

Download a reviewed Markdown report and selected evidence as a ZIP.

See the full workflow in 45 seconds.

From a failed browser action to a reviewed local export—without leaving the evidence scattered across screenshots and DevTools.

Your report stays under your control.

Filtering happens before diagnostic data is stored. You inspect the capture and explicitly choose which local files to export.

Captured intentionally

Nothing is recorded before you choose a tab and start the capture.

Reviewed locally

Remove unwanted entries and visual evidence before creating the report bundle.

Exported explicitly

BugReceipt does not automatically upload, email, or submit your capture.

Changelog

A concise view of what is available and what is coming next.

0.3.0Latest version

Updated review experience, evidence curation, local export flow, and the new light/dark product identity.

0.1.6Previous release

Tab recording, console and network evidence, manual steps, annotations, and reviewed local ZIP export.

Frequently asked questions

What BugReceipt collects, where it stays, and what happens when you export.

What does BugReceipt capture?

Only evidence collected after you start: the selected tab, console messages, network activity, page context, and steps you add.

Does BugReceipt upload my report?

No. Captures stay in extension-owned browser storage. A report leaves only when you explicitly export and share it.

Can I remove sensitive information?

Yes. Review and remove individual evidence before export. Diagnostic filtering reduces risk, but you should still inspect screen recordings and every report field.

Which browsers are supported?

BugReceipt currently supports Chrome desktop version 125 and newer.

Does it create GitHub issues automatically?

No. BugReceipt exports local files and can open the public issue form, but it does not populate or submit an issue.

Report bugs with proof.

Capture the context developers need.

Add to Chrome