File a bug on WhatsApp

Your team can file a bug without opening a laptop: message the Glitchgrab WhatsApp number, chat about the problem, and it becomes a GitHub issue.

Who can use it

• Owners and members whose WhatsApp number is verified in Glitchgrab (see Get WhatsApp alerts for your issues).
• QA testers whose phone number the owner saved on their tester row (see Add a QA tester).

The number you message from must be exactly the number saved in Glitchgrab, country code included. A number saved without a country code is read as an Indian (+91) number.

Clients, reporters and demo prospects cannot file this way. If they message the number, they get the usual replies.

File a bug

1. Open WhatsApp and message the Glitchgrab number with bug (or issue, report, report a bug). You can add the problem straight after it: bug: Save does nothing on the invoice page. Sending a screenshot, a voice note or a video also starts a report.
2. Pick the project from the list. You only see projects you can file into. If you have just one, this step is skipped. Sent several screenshots at once? They all join the report and the list comes once.
3. Tell it what went wrong, in any mix: type it, send several screenshots at once, record a voice note, send a screen recording.
4. The assistant may ask a question or two. Two or three short answers (like Yes, that's it / Not quite) come as buttons; longer ones come as a list. Tap one, type your own, or say it.
5. When it shows the draft, tap File it. Tap Keep chatting to change something, or Cancel to stop.
6. You get the issue number and link back in the chat.

Type cancel at any time to stop. Nothing is filed.

hi still sends a tester their sign-in link. It does not start a report.

Voice notes and videos

• Voice note: Hindi, English or a mix both work. You get back 🎙 I heard: … with what it understood, once per voice note. If that is wrong, type it instead. The voice note itself is linked on the GitHub issue, so the developer can listen to it.
• Video: you get 🎬 Got your video, watching it…, then 🎬 I saw: … with the steps it saw on screen. The video is linked on the issue too.
• Up to 6 screenshots and 3 videos per report, each video up to 16MB (WhatsApp's own limit).
• Sending screenshots without words? You get 📎 Got it and the assistant reads them with your next message or voice note.

Share a meeting recording

Recorded a client call and want to talk it through with Claude? Send the recording to the same number.

1. Send the recording. A voice note or audio file longer than 10 minutes, or any audio or video sent as a document (📎 → Document — the way to send a Meet or Zoom recording), counts as a meeting. Add a caption to name it.
2. Tap Save as meeting. (Tap It's a bug note if it was a bug after all.)
3. Pick the project.
4. You get Got it — transcribing the whole recording. It takes a few minutes, longer for an hour-long call.
5. You get the link to a new GitHub issue, Meeting: <name>. It has a short summary, what the client asked for, a link to the recording on the project's Calls page, and the full speaker-labelled transcript in the comments.

Point a Claude session at that issue to discuss the meeting. The call also shows on the Calls page with a WhatsApp tag, where you can play it back and retry the transcript.

Recordings up to 100MB (WhatsApp's document limit). Shorter than 10 minutes, it is treated as part of a bug report instead.

When the AI is off for a project

If the project has the AI report assistant off or no GLITCH.md, the chat is plain: describe the bug, send screenshots, voice notes or videos, then reply done. Your words are filed as you wrote them.

Good to know

• A chat stays open for 24 hours. After that, type bug to start again.
• PDFs, stickers and other files are not taken.
• If the assistant answers your question from the project's guides, nothing is filed.
• The issue says it was filed from WhatsApp, under your name.