Notwork

Notwork records the network requests and console output produced while you reproduce a bug, then hands you everything as a single zip file. DevTools can export network activity as HAR, but the console has to be copied separately and the two are hard to line up in time. Notwork records only from the moment you press start until you press stop, so a report contains exactly the window you care about. ■ How to use 1. Click the toolbar icon and press Start recording. 2. Reproduce the problem. Press Add marker to annotate a moment. 3. Press Stop recording. The zip downloads right away. · Use Alt+Shift+R to start or stop and Alt+Shift+M to add a marker without opening the popup. ■ What is in the zip · network.har — requests and response bodies. Drag it into the DevTools Network panel to reopen it. · console.ndjson — console calls, uncaught exceptions, browser-issued log entries · timeline.ndjson — navigations and the markers you added · raw-events.ndjson — the raw CDP events · meta.json — recording environment and counts · redactions.json — the field names and locations that were redacted · screenshots — the page at start and at stop · screen.webm — a screen video of the tab, when you turn screen video recording on Network and console entries share one time base, so the order between them is preserved. ■ Redaction By default Notwork replaces Authorization and X-Api-Key style headers, query parameters and URL fragments whose names denote tokens or passwords, JSON, form, XML and multipart body keys, and JWT strings with [REDACTED]. It follows the name even when the value is percent-encoded or when one URL is nested inside another. Once a value has been redacted, the same string is also removed anywhere else it appears in the same recording. Only the field names are listed in redactions.json. You can turn this off in the popup. The Cookie and Set-Cookie headers the browser adds on its own never reach the path Notwork records through, so they are absent from the zip. Both headers remain in the redaction rules, so if they ever do reach a recording they are redacted like any other authentication header. ■ Good to know · While recording, Chrome shows its own "extension is debugging this browser" banner. · Notwork cannot attach to a tab that already has DevTools open. Close DevTools first. · Console messages produced before you press start are not captured. · Values that carry no name are not redacted. HTML form attributes, CSV and TSV bodies, and bare values printed to the console fall into this group. · Binary bodies (images, video, protobuf and the like) are left out of the recording before redaction applies. · The screen video and the screenshots contain whatever is on screen, and redaction is not applied to them. · Recordings stay in your browser. Nothing is uploaded.