Local-first Chrome extension for capturing privacy-filtered console, network, reproduction-step, and visual evidence in a reviewable bug report.
BugReceipt is a browser extension created to make a real workflow clearer, faster, and easier to trust. It turns a focused product idea into something people can use, evaluate, and understand without needing to inspect the source code.
Why BugReceipt exists
Screenshots and vague descriptions rarely preserve the sequence, browser evidence, environment, and visual result developers need to reproduce a web application failure.
The goal is not simply to add another tool. BugReceipt is designed to reduce the friction around that problem and give people a more dependable way to complete the work.
What it delivers
- Reporters can preserve reproduction steps, bounded console and network evidence, environment details, and a recording or screenshot in one workflow.
- Every captured item remains reviewable and removable before it leaves extension-owned storage.
- Users can export a local Markdown-and-visual bundle or deliberately send a size-bounded report through the configured endpoint.
- Maintainers can exercise known failures and ship verifiable unpacked Chrome archives with published checksums.
The experience
Local-first Chrome extension that combines privacy-filtered console, network, reproduction-step, environment, and visual evidence in a reviewable browser bug report.
The project brings the important parts of the workflow into one coherent experience. Its interface and behavior are shaped around the people using it, while the implementation stays focused on predictable results and honest feedback.
What to know
Every product has boundaries. These are the most important considerations for BugReceipt:
- Browser diagnostics and screen recordings can expose sensitive information, while local filtering cannot guarantee that every secret will be recognized.
- Chrome permission, selected-tab, service-worker, navigation, and storage boundaries must remain understandable during a capture.
- Email delivery crosses a separate network boundary and must not bundle server credentials or silently transmit evidence.
These limitations are presented openly so visitors can understand where the project works well, what it depends on, and what may change in future versions.
Current status
Public pre-release. The current release demonstrates the core value of the project and the main end-to-end experience.
My role was product design and browser-extension engineering, covering capture lifecycle, privacy boundaries, review workflows, and release delivery. The related case study explains the decisions and delivery process in greater depth for visitors who want the engineering story behind the product.