A bug report is usually a sentence and a screenshot, and the first reply is always the same three questions. GuideGen answers them before they are asked — every click, and every API call those clicks fired.
For: QA engineers, support engineers, and anyone who files the ticket somebody else has to reproduce.
Turn on the API capture before you record. Each step carries the calls it fired — method, path, status — and you can copy any one of them as a cURL with the headers and the body. POST /api/orders → 500 is a starting point; “the save button is broken” is not.
Catch-up capture means the recording can start after the bug did. Arm the dashboard once, work normally, and when something breaks take the last two minutes — screenshots, steps and network log intact.
Authorization headers, session cookies, API keys and query-string values are replaced with a mask in the page and again in the extension. The cURL documents the call. It cannot replay it.
Response bodies can hold real customer records, which is exactly why this tier is off by default and why the whole capture stays on your machine. Attach the file to the ticket yourself, or hand the text to a model.
Free, unlimited guides, no watermark and no card. Everything runs in your browser until you choose to publish.