Bugpacker

Stop receiving bug reports
that say “it’s broken”.

Bugpacker records a bug while you reproduce it, then hands you one file to attach: screenshots, console output, failed requests, the state of every form field, and the steps you took, written for you.

Add to Chrome See what’s in the file Free. No account, no upload.

A Chrome extension. The package is built in your browser and saved to your downloads folder.
Recorded on demo.bugpacker.com, a deliberately broken checkout you can open yourself.

Repro steps, written for you

Writing steps is the friction that produces one-line bug reports. Bugpacker drafts them from what actually happened, and you correct the draft.

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 (reading 'total')
5. Request failed: POST /v2/discount → 500
6. Navigated to /checkout

Bugpacker records that a field was typed into. It never records the value.

What lands in the file

One ZIP, about a megabyte, attachable anywhere.

BUG-REPRO-STEPS.txt Steps, expected, actual, environment
BUG-REPORT.md The same, for pasting into a tracker
report.json Structured, versioned, with a fingerprint for de-duplicating
screenshot-*.png The page at the start, the area you marked, and the end
console.log Logs, uncaught errors, rejections, CSP violations
network-errors.log Real failures, kept apart from ad-blocked noise
network.har Opens in DevTools and any HAR viewer
form-state.json What each field held and why it was rejected
page-snapshot.html The DOM, made inert so opening it runs nothing
environment.json Browser, OS, GPU, viewport, preferences, frameworks

Built for the awkward bugs

Mark it when it appears

You rarely know where a bug will surface. Record first, then mark the problem area the moment it shows up, even a screen later.

Field state in detail

“Rejected an unknown string” is not actionable. Bugpacker reports the length, the shape, the validation flags and the site’s own error text.

The server’s own request id

Trace headers are lifted to the top of the report, so a backend engineer can jump straight to the matching server log.

Noise stays out

Requests an ad blocker killed are counted separately from real failures, so forty blocked pixels never look like a fire.

Hand it to your coding agent, not to a server

Jam, BugHerd and Usersnap can all hand an AI agent your bug report, because the capture is already on their servers. Bugpacker's is a file on your disk, so it needs a reader that runs on your machine and opens the file you already have. Works with Claude Code, Cursor, Codex and anything else that speaks MCP.

$ npm install -g bugpacker-cli
$ claude mcp add bugpacker -- bugpacker mcp ~/Downloads

> What went wrong in the bug I just captured?

Promo validation rejected a code the user did type. The page has two
elements with id="promo-code": the keystrokes landed in the second,
the length check read the first and saw zero. No request ever
reached the checkout backend.

Your agent gets the console error, the failed request, the form state and the steps you took. The extension makes no network requests and neither does the reader, which is open source. What your agent does next is your decision: a cloud-hosted agent sends what it reads to its provider, and a local model sends nothing anywhere.

Or read it yourself, without an agent

The same reader is a normal command-line tool. Useful when the fastest way to understand a bug is to look at it.

bugpacker show The whole report, summarized
bugpacker steps Repro steps, with expected and actual
bugpacker console Logs, uncaught errors, CSP violations
bugpacker network Real failures, kept apart from ad-blocked noise
bugpacker har The session as HAR, for DevTools or a HAR viewer
bugpacker files Everything the package holds, with sizes
bugpacker json report.json, for piping into something else
bugpacker extract Write any artifact out as a file

Nothing leaves your machine

All five products on our comparison page store captures on their own servers. Bugpacker builds the package in your browser and saves it to your downloads folder. There is no server of ours in the loop.

Redaction is always on

Emails, phone numbers, card numbers, tokens and authorization headers are replaced before you see the package. There is no setting that disables it.

Placeholders keep the shape

A rejected number reads [PHONE_1: (NNN) NNN-NNNN]. That is enough to fix a validator and too little to identify anyone.

Never the values

Typed text, passwords, cookie values and storage values are not captured at all. Bugpacker records only that a field was used and what its name was.

No network requests, ever

The extension declares no host permissions, which is the browser's own way of saying it has nowhere to send anything.

Redaction is best effort. Read the privacy policy for exactly what is captured and what is not, or the security and data handling page if you have to get this approved by somebody.

Free, with nothing held back

Bugpacker has no server, so there is no data to sell and nothing to sign up for. We do not know who you are or whether you ever use it. The extension contains no analytics and no crash reporting.

There is no paid tier, and little to pay for: no server to run and no accounts to support. If work on it stopped tomorrow the copy you installed would keep working.

Stop receiving bug reportsthat say “it’s broken”.