Loupewire: HTTP Request Inspector, Header Editor and Masked HAR Export

Capture traffic from every tab in one window, apply header rules, mask secrets and export HAR. All on-device, no accounts.

Loupewire opens one window that records the HTTP requests every tab and popup makes, so a flow that crosses several pages - a login that bounces through a redirect chain, a payment step that opens a verification window, a vendor checkout - reads as one list. Select any request to see its headers, cookies, form data and body, timing and redirect chain. Everything runs on your device. 🔍 CAPTURE ACROSS EVERY TAB - One tracker window records every tab and popup in the browser window it belongs to - Request and response headers, cookies, form data, raw bodies, timing, redirect chain, resource type and server IP - Requests that were blocked or failed appear in the list with the reason - Open the tracker in its own window or as an ordinary browser tab 🛡️ MASKING, ON SCREEN AND IN THE FILE - Add a pattern such as authorization or session, and every matching value shows only its first and last characters - A built-in preset covers the common secret-bearing header and field names and is on by default - Masking is applied as the row is drawn, and there is no reveal button - a screenshot of the panel is already safe to attach 📤 EXPORT AND COPY, ALREADY REDACTED - Export as HAR 1.2, what vendors, developers and every network tool read - Export as Loupewire JSON, which keeps what HAR has nowhere to put: each redirect leg, partial records, and how a multipart field was read - Choose what goes in: everything captured, only the rows you selected, or only what the filter shows. A file holding part of a session says so inside itself - Copy one request as redacted text, or as a redacted cURL command, for a ticket or a chat message ✏️ REQUEST HEADER RULES, WITHOUT A PROXY - Set a request header on every request whose URL matches a filter, for a staging API or a feature flag - Rules are applied by the browser's own declarative rule engine, and the captured request shows the header exactly as it was sent - Headers that belong to the connection itself, such as Host or Content-Length, are allowed and flagged with a warning - Rules last while the tracker window is open and stop when it closes 🎯 NARROW IT DOWN - Track and Skip patterns decide what is recorded, for the session or for every window - Filter the table by url, method, status, date and cache state, combined with & and | - Block requests by pattern to see how a page behaves when an endpoint is unavailable - Find text inside the request you have open - Pause and resume; clear everything, the selected rows, or the rows currently shown - Select several rows and export or clear only those 🌍 INTERFACE - Available in 8 languages, including right-to-left interfaces that mirror as a whole - Light, dark, or following the system 🔒 ON-DEVICE, AND NOTHING ELSE - Captured headers, cookies, bodies and URLs stay in the tracker window and are never written to disk unless you export them - Your patterns, rules and settings are stored in the browser's local extension storage - The extension makes no network requests of its own - No account, no telemetry, no analytics, no crash reporting ⚠️ WHAT IT DOES NOT DO Response bodies are not available. The browser API Loupewire observes traffic with does not expose them, and Loupewire does not attach a debugger to your tabs to get them. When you need a response body, use DevTools alongside Loupewire. 🚀 QUICK START 1. Install, then click the Loupewire icon in the toolbar 2. The tracker window opens and starts recording straight away 3. Browse in any tab of that window - rows appear as requests are made 4. Select a request to read its headers, then Export to attach a masked HAR to a ticket 📞 SUPPORT - Guides: https://loupewire.github.io/guides/ - Support: https://loupewire.github.io/support/ - GitHub: https://github.com/loupewire/loupewire-support 🔗 LINKS - Website: https://loupewire.github.io/ - Privacy Policy: https://loupewire.github.io/privacy-policy/ - Terms: https://loupewire.github.io/terms/ 🔐 PERMISSIONS - webRequest: observe request and response metadata so the tracker can list and display it - declarativeNetRequest: apply your header rules and block patterns while the tracker is open - Storage: save your patterns, rules and settings locally - Host access to all sites: traffic from any site you visit must be observable, and header rules must apply to whichever host you target No content script is injected into any page. Captured traffic never leaves your device.