Bugpacker: QA bug reports with screenshot, console, network & repro steps

Bugpacker turns "it's broken" into a bug report a developer can act on. Press record, reproduce the problem, mark it when it appears, and Bugpacker hands you a single ZIP to attach to Jira, GitHub, Linear or an email. WHAT IT CAPTURES • Screenshots of the page, with the area you marked highlighted • Console output, uncaught errors and Content Security Policy violations • Failed network requests, with the server's own request id when it sends one • The steps you took, drafted for you and ready to edit • The state of every form field and why the browser or the site rejected it • Browser, OS, GPU, viewport, zoom, colour scheme and framework versions REPRO STEPS, WRITTEN FOR YOU Writing steps is the friction that produces one-line bug reports. Bugpacker drafts them from what you actually did: 1. Clicked "Add to cart" (#add-to-cart) 2. Typed into "Promo code" (#promo) 3. Clicked "Apply" ([data-testid="apply-promo"]) 4. Console error: TypeError: Cannot read properties of undefined Correct the draft instead of facing an empty box. NOTHING LEAVES YOUR MACHINE No account. No upload. No telemetry. The package is built in your browser and saved to your Downloads folder. Every other tool in this category uploads your bug data to its own cloud first; Bugpacker never does. GIVE IT TO YOUR CODING AGENT, NOT TO A SERVER Because the package is a file, it can go straight to Claude Code, Cursor or anything else that speaks MCP, without passing through anyone's server on the way. Every other tool in this category can hand your bug report to an agent because it is already on their cloud. This one reads it off your disk. bugpacker-cli is a separate free tool, open source, that does this. It also reads a package in the terminal if you would rather look yourself. It makes no network requests either. Optional, and the extension is complete without it. Details at bugpacker.com. PRIVACY SCRUBBING IS ALWAYS ON Email addresses, phone numbers, card numbers, tokens and authorization headers are replaced before you ever see the package, and there is no setting that turns it off. Placeholders keep the shape and drop the content, so a rejected phone number reads [PHONE_1: (NNN) NNN-NNNN]: enough to fix a validator, not enough to identify anyone. Screenshot scrubbing masks password and payment fields automatically. That part is best effort, so you review everything before it is saved. ANNOTATE BEFORE YOU SEND Boxes, arrows, numbered pins, text labels, and a mask brush for anything the automatic pass missed. TRY IT IN THE FIRST MINUTE Installing a bug reporter when nothing is broken is an awkward moment, so there is a bug waiting for you. demo.bugpacker.com is a checkout that rejects a valid promo code, because the same element id is used twice and the page reads the copy the customer never typed into. Record it, and see what the package says about why. PRICE Free. No account, no upload, no telemetry, and no network requests of any kind. There is nothing to sign up for and no data to sell. Bugpacker has no server, and the extension declares no host permissions at all, which is the browser's own record of the fact that it has nowhere to send anything.