RequestFox - Network QA Monitor by Abhishek Johri

RequestFox watches your browser's network traffic while you manually test a
web app, and automatically flags the things a tester would otherwise have
to notice by eye.

WHAT IT CATCHES
• Duplicate calls — rapid double-fires and retry-like repeats
• Failed requests — every 4xx/5xx, tied back to the click or form submit that caused it
• Slow responses — against a threshold you set
• API contract drift — the same endpoint's response shape changing mid-session

COMPOSE, IMPORT, AND SEND
• Build a request from scratch and fire it through the page you're testing
• GraphQL mode — query + variables, sent and captured with the real query text visible in the log
• Import a Postman Collection (v2.0/v2.1) or an OpenAPI 3.x spec
• Environments with {{variable}} substitution, saved collections
• OAuth 2.0 (Authorization Code + PKCE) against your own app registration, tokens AES-GCM encrypted in a local vault you unlock with your own passphrase — never stored in plaintext, never sent anywhere

SEE WHAT PLAIN DEVTOOLS CAN'T
• A dedicated WebSocket/SSE panel — every frame sent or received on a socket, and every server-sent event, while regular network tools only show the initial handshake
• Inject a fake incoming (server → page) or outgoing (page → server) message on a live connection, to test how the page reacts

TURN A TEST SESSION INTO A REGRESSION SUITE
• Chain saved requests into a named, repeatable test suite with pass/fail per step
• Data-driven runs — paste a table of values and run the whole suite once per row
• Export captured traffic straight to a Playwright test, a Cypress test, or a k6 load-test script
• Request chaining — extract a value from one response into a variable the next request uses
• Optional pre-request / post-response JavaScript for one-off logic a UI can't cover

FIND WHAT YOU'RE LOOKING FOR
• GitHub-style filters: status:>=500, method:POST, has:drift, latency:>1000
• Session-vs-session diff, and live-vs-baseline comparison
• Global search across every archived session
• A dedicated DevTools panel alongside the sidebar — same view, wherever you already work

SHAPE THE TRAFFIC
• Header override / URL rewrite rules while recording
• Fault injection & mocking — force a failure, a delay, a size-proportional network throttle, or a mocked response for an endpoint that doesn't exist yet, organized into named groups
• Per-endpoint assertions (status, latency, field, or full JSON Schema)
• An opt-in, off-by-default heuristic scan for leaked secrets and a short list of API misconfigurations

TAKE THE EVIDENCE WITH YOU
• Export an HTML report, HAR, CSV, session JSON, Postman Collection, or a best-effort OpenAPI spec reverse-engineered from what was captured
• Copy any request as cURL or fetch()
• One-click GitHub/Linear issue creation, pre-filled with the request and a repro
• Export environments + saved collections as one workspace file to share with a team, or commit to git

No account, no cloud sync, no telemetry. Everything lives in your browser's
own local storage — nothing is sent anywhere. Load it, click Start
Recording, and go test.