G-garry

G-garry is a DevTools panel for inspecting and modifying the API calls your web app makes. It adds a "G-garry" tab to Chrome DevTools (F12). There is no toolbar icon and no popup — open DevTools on the page you are developing, and the panel is there. WHAT IT DOES G-garry patches window.fetch and XMLHttpRequest on the page you have open, so every API call that page makes is listed, and any of them can be changed while you work: • Inspect — every fetch/XHR request in a familiar request grid: name, status, method, type, initiator, size, time and a waterfall. Response bodies are pretty-printed, syntax-coloured and searchable, either as a JSON tree or as raw text. • Mock — serve your own response for a matching request. A rule can replace the whole body, or patch only the fields you edited and let everything else come from the real server, so a mock authored while logged in as one account keeps working for another. • Redirect — send a matching request to a different address and let a real server answer it: point one endpoint at staging or at a local fixture server while the rest of the app keeps talking to production. • Block — stop a request being sent, so you can see how the application behaves when an endpoint fails or times out. • Replay — re-send a captured request with an edited URL, headers or body. The URL is edited as structure — origin, path and a table of query parameters — and anything you do not touch is sent back byte for byte. • Trace — pick an element on the page and find which API response produced the value shown in it. • Library — keep a response body permanently, with its URL, status and headers, so you can return to it after the log has been cleared. • Import / export — HAR 1.2, plus a native session format and mock-rule files. Sensitive header values are redacted by default.