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 asks what they want to do, with starters like Something on this page is broken, It did the wrong thing, I wish it could… — or they just type.
2. 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.
3. If it is already a known open issue, it asks whether theirs is the same problem. If they agree, their words are added to that issue instead of opening a new one.
4. Otherwise it says back what it understood and asks them to confirm, then writes a report under Your report · edit anything. They can keep correcting it by typing (Anything to change? Tell me here…).
5. They press Send Report (or Add to #N for an existing issue).

Write it myself switches to the plain form at any time. If the assistant is unavailable or the project's monthly limit is reached, it closes and says so — the plain form underneath still sends.

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.
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. The person can press Add to #N, or No, mine is different — send as new.

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

What arrives in your issue

• 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 AI assistant has hit this project's monthly limit. Write your report below and send it as normal.

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.