What your users see when they report a bug

This is the report dialog people see inside your app — the Glitchgrab SDK, the Chrome extension and the GlitchRecord desktop app all show the same one. Read it once so you can tell your users what to expect, and so you know what arrives in your issues.

Opening it

• The Report Bug button your app shows, or
• ⌘⇧G on a Mac / Ctrl+Shift+G on Windows, anywhere in the app.

A screenshot is taken the moment it opens, so it shows exactly what was on screen:

• In Chrome, Edge and other Chromium browsers, the browser asks permission to share the tab. The person picks this tab and allows it. Glitchgrab reads one frame and stops sharing at once — the "sharing this tab" bar should disappear within a second.
• If they pick something else, or decline, the report goes without that screenshot.
• In other browsers the page is redrawn into an image instead, with no prompt.

If the AI assistant is on for your project

The dialog opens straight into Describe it with AI, a chat that already has the screenshot and what the person clicked.

1. It opens on an empty chat with the cursor in the text box (What went wrong, or what would you like?) — no question, nothing to pick. They type the problem and press Enter. The report type (Bug Report, Feature Request, UI Improvement or Performance) is filled in from what they wrote and shows once the draft appears; a bug then asks how bad it is. To pick a type by hand, or give a star rating, they press Write it myself.
2. Files they attach in the chat are read too: screenshots, text files (HTML, JSON, logs) and PDFs. A PDF shows a small spinner while it is read, then is outlined like the rest. A scanned PDF or one over 3 MB stays greyed out — it is still attached to the report, just not read. To point at the problem, they press the pencil on a screenshot thumbnail (or tap the thumbnail) and draw on it — pen, highlighter, rectangle, circle or arrow, with undo and clear. It opens on the rectangle, so the first drag draws a box; the other tools are one click away. A rectangle can be moved or resized by dragging it or its corners right after drawing, and each tool remembers its own colour and thickness. The highlighter leaves the text underneath readable. Save annotation swaps in the marked picture, so the assistant and your issue both see the marks.
3. If you already have an answer — a published guide or your GLITCH.md covers it — it tells them what to do, links the guide, and offers That worked / Still broken — report it. If it worked, nothing is filed.
4. If it is already a known open issue, it names the issue and says in one line what the two have in common (— both are about …), then asks whether theirs is the same problem — they tap Yes, or type what is different about theirs. It matches on what they wrote, not on the sidebar or dashboard an attached design shares with every page. An issue is only named when it is the same thing going wrong, not just the same screen, and never when it covers only one of several problems they described. If they agree, their words are added to that issue instead of opening a new one. If they say no — or that the issue is already closed — the issue disappears from the chat and is not offered again. It asks once what is different (no buttons), and whatever they reply is written up as a new report. Their words go on that issue only if they say themselves it's the same after all. If theirs is a different request for the same feature (another way into the same flow), it asks whether to add it to that issue — Yes, add it there / No, file it separately. Added, it goes on as a comment marked as a related request, so closing that issue does not cover it.
5. Otherwise it says back what it understood and asks them to confirm, then writes a report under Your report · edit anything, with a short title on top saying what it is. They can edit both; the title becomes the issue title. They can keep correcting it by typing (Anything to change? Tell me here…).
6. They press Send Report (or Add to #N for an existing issue). Send first checks for a matching open issue — the same Our team may already have this card as the plain form (below), shown in the chat in place of the Send button. An issue they already said was not theirs in the chat is left out of that card.

While a reply is on its way the bubble says Sending your screenshot… 40% until the picture has arrived, then Thinking… 5s. The screenshot is sent once per chat, so later replies skip straight to Thinking.

If no answer comes within about a minute, the bubble says No answer — this is taking too long with Try again (asks the same question again) and Write it myself (opens the plain form with what they typed already in the description).

Write it myself switches to the plain form at any time. ✕ in the top-right corner closes reporting altogether; a chat they typed in stays under Chats. If the assistant is unavailable or busy, it closes and says so — the plain form underneath still sends.

Coming back to a chat

The chat is kept in the person's browser as they go, so closing the dialog or the page loses nothing.

• Opening Describe it with AI again shows Pick up where you left off. Continue this chat brings the whole conversation back. For a bug it shows above How bad is it? too, so they do not have to answer that first.
• If they left before the assistant answered, Continue this chat makes it answer that last message again by itself. They do not retype it.
• Chats in the header lists every chat. Unsent ones continue; sent ones open read-only.
• × deletes a chat.
• Chats stay in that browser only, separate per project and per signed-in person, for 30 days (up to 20). Screenshots are not kept with them.
• Not in the GlitchRecord desktop app yet.

The plain form

1. What's on your mind? — pick a type: Bug Report, Feature Request, UI Improvement, Performance, Security, Question or Other. If your app collects ratings, a How are we doing? star row appears above. When the AI assistant is on, a Describe it with AI button above the types takes them back to the chat.
2. Tell us more — describe it. Extras on this screen:
   • Describe it with AI — open the assistant (when it is on).
   • The microphone — speak instead of typing.
   • AI enhance — tidies the grammar without changing the meaning (when AI is on).
3. Attachments — add screenshots or files: drag and drop, paste with ⌘V / Ctrl+V, or click to browse. Images, PDF, Word, Excel and text files (logs, JSON, HTML) are accepted.
4. How bad is it? — shown for bugs when your app asks for a severity.
5. Send Report.

Before sending, Glitchgrab checks for an existing report: Our team may already have this lists matching issues — ones that ask for the same thing, even in different words. An attached HTML or PDF design counts too, so a mockup of the Invoices page is not mistaken for one of Leads. The person can press Add to #N, or No, mine is different — send as new. Sent as new, the issue still names the closest match at the top (Possibly related: #N), so whoever triages sees the overlap.

If the same person sends nearly the same text again within a day while their earlier issue is still open, it is added to that issue as a comment instead of opening a second one.

When it is sent they see Bug Report sent. Thank you! (or Added to #N. Thank you!).

What arrives in your issue

• A title saying what the report is — the assistant's (as edited) when they used it, otherwise the first sentence of their description.
• Their description, and the report type as a label.
• The screenshot and any attachments (text files are previewed and stored in full).
• The page, the pages they came through, the browser and screen size.
• The activity log — what they clicked and which requests failed just before.
• Who they are, if your app passes a session.
• The full AI conversation, folded, when they used the assistant.

Messages people may see

• Please describe the actual issue you're experiencing — the description was empty or too vague.
• Pick how bad it is before sending. — severity is required for bugs in your app.
• Could not send — please try again. — the network or Glitchgrab was unreachable.
• The assistant is busy right now — try it again in a few minutes, or write your report below and send it as normal. — an unusual number of reports in the last hour. There is no monthly limit.
• The assistant took too long to answer — try again, or write it yourself. — the AI took over a minute to reply (seen on older versions of the SDK; newer ones show the Try again bubble above). What they typed stays in the form, and the assistant button stays.
• AI enhance isn't available right now — send your report as written. — AI enhance couldn't run (the AI service is down or out of budget). Their text is unchanged and still sends.
• Too many AI enhance tries — wait a while, or send your report as written. — the hourly AI enhance limit was reached.

The footer

• Problem with Glitchgrab? — reports a problem with the dialog itself to the Glitchgrab team (see Let reporters flag a problem with Glitchgrab). Otherwise the footer reads Powered by Glitchgrab.