HaoDev - Network Request to Bug Report

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

This update upgrades a single request record into a complete, deliverable on-site record. New · Screenshots and Annotations Screenshots can be pasted directly (via paste, drag-and-drop, or file selection) and saved as screenshot evidence alongside request records. They are mixed into the evidence library, allowing you to view, download as PNG, add titles, and write reproduction steps. Built-in annotation editor: rectangles, arrows, lines, text (with adjustable color and thickness), mosaic, eraser, and crop, all supporting undo and redo. Text can be typed directly onto the image, then dragged, resized, rotated, and re-edited. Mosaic is truly baked into the image: upon saving, the mosaic is flattened into a new PNG at the original image resolution, and neither the original image nor the mosaic steps are retained in the library. Better not to save than to be sloppy: if any mosaic operation fails to apply, saving the image is not allowed. New · Deliver a Complete On-Site Record at Once Combine multiple requests and screenshots into an "evidence set," and export it with one click to Markdown / HTML / JSON, with screenshots included. HTML embeds images inline into a single file (viewable offline by double-clicking); Markdown and JSON deliver PNGs alongside. Before exporting, it lists every file that will be written to disk and notes that screenshot content is not automatically desensitized — allowing you to review everything before delivery. New · No Lost Context Even after closing and reopening DevTools, unconsolidated requests from the previous session can still be retrieved (marked with ↺ and still eligible for consolidation). Improvements The evidence library clearly indicates which records have been included in an evidence set: row-level color bars + reference count badges + an "Not in Set" filter. When the panel is docked to the left or right of DevTools, or when the window is narrowed, the filter box and toolbar buttons are no longer squeezed out. Before deleting evidence, it clearly states which evidence sets will be affected (including cases where "an evidence set will become empty"), and allows you to delete empty evidence sets at the same time. Note: This extension does not request any website access permissions (zero permissions upon installation), so you need to take screenshots yourself and paste them in. HaoDev turns a failing network request 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. FEATURES • Pin requests from the DevTools Network panel; pinned items survive closing DevTools. • 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. • 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 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. • 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. It cannot read or modify any website you visit. 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.