HaoDev - Network Request to Bug Report

Pin requests, annotate screenshots, redact tokens and cookies, export Markdown / HTML / JSON. No server, no host permissions.

HaoDev turns a failing network request — and the screenshots that show it — into a file you can hand to someone. There is no toolbar UI to speak of: the work happens in a DevTools panel. The toolbar icon opens a three-step guide (and a walkthrough page opens on first install), so you are never left wondering whether the install worked. Open DevTools, reproduce the problem, click "Pin", then export. You get a document that contains the request, the response, the headers, a runnable cURL command and a place for reproduction steps — ready to attach to a bug report or send to a backend developer. It is a DevTools extension, so it only sees traffic while DevTools is open: open DevTools first, then reproduce the problem. That is a deliberate trade-off — watching your traffic without DevTools would require host permissions, and this extension has none. WHY ANOTHER NETWORK TOOL? Because "can you send me the request?" usually means screenshots, or copy-pasting a half-relevant slice of the Network panel. Both lose the part that matters: the exact headers, the response body, and the moment in time. This extension captures all of it as one artifact — and it takes the screenshots too: paste one in, mask or annotate it, and it ends up in the same document as the requests. FEATURES • Pin requests from the DevTools Network panel; pinned items survive closing DevTools. • Record a session: press Record, reproduce the bug, press Stop. You then pick what to keep — failures are ticked for you, static assets are folded into one row, and the footer says how many will be pinned and how much of the monthly allowance is left. Confirming turns the selection into an evidence pack in one step. If DevTools was closed while recording, it says so and reports the exact gap instead of pretending nothing happened. • Screenshots: paste, drag or pick an image file and it becomes evidence — listed next to your requests in the same library, with a title and repro steps. • A built-in annotation editor: box, arrow, line, text (colour and weight), mosaic, eraser and crop, all with undo / redo. Type straight onto the image, then move, resize, rotate or edit that text again later. • Masking is real: on save the mosaic is flattened into a new PNG at the original resolution, and neither the original image nor the list of edits is ever stored. If a single mosaic stroke fails to apply, the save is refused rather than quietly shipping an unmasked image. • Evidence library: browse, search, sort and delete what you pinned. • Three export formats: - Markdown — for pasting into an issue or a chat. - Single-file HTML — one file, opens offline, no scripts, dark-mode aware. Self-contained: hand it to anyone. - JSON — structured data for tooling, migration, or AI pipelines. • Images travel with the export: the HTML inlines them (it stays a single file), while Markdown and JSON hand the PNG files over alongside the document. • Before anything is written, the export lists every file it is about to create (the document plus each PNG) and says plainly that screenshots are not auto-redacted. • Redaction built in: Authorization, Cookie, tokens, session ids, passwords, emails, phone numbers, ID and bank card numbers, and URL credential parameters — plus your own field names. File names are always redacted, no matter what the switch says. • Customisable export file names, with saved templates. • Reproduction steps and a title written straight into the exported document. • Compare two responses from the same endpoint: pick two pinned records and get an added / removed / unchanged breakdown, exportable as Markdown. • Evidence packs: bundle several requests and screenshots into one document — ideal for a whole flow ("checkout returns 500"), with reordering, per-entry removal and its own repro steps. • Available in English, 简体中文, 繁體中文, 日本語 and 한국어. It follows your browser language, and the panel has its own language setting. LIMITS, STATED UP FRONT • Pinning is capped at 240 requests per month. Exports are never capped, and evidence you have already pinned is never taken away — the counter refills on the 1st of the month. Screenshots have no monthly cap — they only take local disk space. • Screenshots are imported by you (paste, drag, or the file picker). The extension has no host permissions, so it cannot capture a page for you — the same trade-off as above. • Redaction covers text fields only. A token that happens to be visible inside a screenshot is not detected — cover it with the mosaic tool (the UI says so, and the export repeats it next to the file list). • It sees only what DevTools sees, and only while DevTools is open (see above). PRIVACY, BY CONSTRUCTION This extension has no servers and no network code. It cannot upload your data because it never makes a network request — there is a static check for that in the project's own test suite, and it runs on every change. There is no analytics, no telemetry, no account, and nothing to sign up for. It asks for exactly two permissions (the DevTools panel itself needs none — it comes from the `devtools_page` manifest key): • storage — to remember your preferences locally. • unlimitedStorage — so pinned evidence is not evicted by Chrome under storage pressure. No host permissions. No content scripts. Nothing is loaded into a page, and nothing runs on a site until you open DevTools there. One honest caveat about Chrome's own permission list for this extension. It says the extension can "read and change all your data on websites you visit". That line is triggered by the DevTools integration itself (the devtools_page manifest key), which has to work on whatever tab you are inspecting. It is not a host permission, and it cannot be removed without removing the panel. Its only use here: reading the network requests you are already looking at in the Network panel, so you can pin them into a local evidence file. WHO IT IS FOR Frontend and full-stack developers, QA engineers, and support engineers who need to hand a reproducible network failure to someone else.