What the Fetch

Record browser evidence. Investigate with your model. Test with confidence.

What the Fetch (WTF) helps developers investigate browser failures using captured evidence. Choose a page, press Record, and reproduce an issue. Inspect network requests, response bodies, console messages and performance observations in a Chrome side panel or a wider workbench. Ask AI to explain a failure, follow evidence citations, and inspect the relevant requests. - Record and inspect browser evidence without an AI key. - Connect Groq, OpenAI, Anthropic, Google Gemini, or a compatible hosted/local API using your own settings. - Use Included AI when available, with a limited allowance and no personal provider key. Shared capacity and provider limits apply; one investigation may use multiple model turns. - Review approvals before state-changing browser actions under the default autonomy setting. - Export HAR, cURL, Postman collections, investigation reports and portable recordings. - Keep recordings in your Chrome profile, and optionally save them to a folder you choose. You control what page is recorded and when recording stops. Captures can contain private content and credentials. Before sending evidence to AI, What the Fetch identifies the destination and asks for consent. Recognized credentials are masked by default, but masking is not comprehensive. Included AI sends text evidence through our Cloudflare-hosted gateway to the provider named in the prompt; your own-provider mode connects directly to the endpoint you choose. What the Fetch uses Chrome’s debugging permission to capture and inspect the selected tab. Browser actions can affect the live application. Only debug applications and data you are authorized to inspect, and review any actions that change state. AI explanations can be wrong; use the linked evidence to verify them. Published by josharsh. Support: harsh.joshi.pth@gmail.com.