FailTrace

Record one tab's network trace while you test. See what led to an error, copy cURL, export redacted bug reports. Local only.

FailTrace records the network traffic of one browser tab while you test, so when something breaks you can see exactly which requests led up to the error — without keeping DevTools open. WHAT IT DOES • Records every request in the tab after you click Start Testing: URL, method, status, headers, request and response bodies, timing. • Flags failures: 4xx, 5xx, network errors, CORS errors reported by Chrome, canceled requests. • Shows context: the 10 requests before and 5 after any failure. • Captures requests from cross-site iframes and web workers inside the tab. • Filters by errors, 4xx/5xx, method, host, text and time range; groups repeated requests. ONE-CLICK EXPORTS • Copy as cURL — correctly escaped, secrets replaced with placeholders. • Markdown bug report — the failed request, its result, preceding requests and correlation IDs, ready to paste into Jira or GitHub. • JSON bundle with a stable schema. • Postman collection (v2.1). PRIVATE BY DESIGN • Local only: no server, no account, no analytics. The extension is blocked from making any network connection. • Nothing records until you click Start. It never resumes on its own after a browser restart. • Secrets are redacted before anything is saved: Authorization, cookies, API keys, tokens, passwords, JWTs. • Common personal data is redacted too: emails, phone numbers, card numbers, Kazakhstan IIN/BIN. • A warning before every export shows what was redacted, so you review it before sharing. • "Metadata only" mode stores no bodies at all. Data is deleted automatically after 7 days (configurable) or with one click. WHO IT'S FOR QA engineers, testers and developers who need to report or reproduce failing requests quickly and safely. NOTE Chrome shows a "FailTrace started debugging this browser" bar while recording. This is Chrome's own notice for the debugger permission; clicking Cancel on it stops the recording.