AI features
Label issues with AI triage
Turn on AI triage so each new issue gets a gg: label for the kind of problem, and correct a wrong label
Steps checked September 12, 2026
AI triage reads each new report and adds one gg: label to its GitHub issue saying what kind of problem it is — a wording mistake, a layout glitch, wrong data, a crash. You can then filter issues on GitHub, route them to the right person, or point an agent only at the kinds it handles well.
It never decides whether a report is safe to auto-fix. That depends on your code and your risk appetite, which Glitchgrab cannot see.
Before you start
- You own the repo.
- It is off by default — it sends reporters' screenshots and text to a model, so only the owner can turn it on.
Turn it on
- Open Repos in the left sidebar and find the repo's card.
- Press TRIAGE OFF. It changes to TRIAGE ON and you see Triage on — new issues get a gg: label for what kind of problem they are.
Only issues filed from now on get a label. Existing issues are not relabelled.
The label arrives shortly after the issue is created, not instantly — triage runs after the issue exists, so a slow or unavailable model never delays or blocks a bug report.
What each label means
| Label | The report is about |
|---|---|
gg:copy | Wording, labels, or a value shown as text |
gg:visual | Layout, spacing, size, colour, overflow, truncation |
gg:content-missing | The screen loads but something expected is blank or absent |
gg:logic | Wrong behaviour — a wrong state change, a bad filter result, an action that does nothing |
gg:data | A wrong or inconsistent value, count or record |
gg:crash | An error, exception, or a blank or broken page |
gg:access | Permissions, roles or signing in |
gg:performance | Slow, hanging or timing out |
gg:feature | Asks for something that does not exist yet |
gg:unclear | Not enough to tell — also used when the model is not confident |
A second label, gg:surface, is added when the report is only about what is shown on screen and makes no claim about what the system calculated or stored. It is the most useful signal for "this is probably a front-end-only change".
Correct a wrong label
Every correction is saved and used to improve the triage instructions, so it is worth the ten seconds.
- Open Reports in the left sidebar.
- On the report's card, press its type chip. The tooltip says Triaged as "…". Click if that is wrong.
- In wrong type?, pick the right type — or leave not sure what it should be.
- In the note, say why it was wrong: Why was it wrong? This is the part that improves the prompt. The reason matters more than the new type.
- Press save. You will see Noted — this goes into the next triage prompt rewrite.
The label on GitHub is not changed by this — edit it there too if you rely on it.
Coding agents can do the same with the correct_triage tool of the Glitchgrab MCP server.
Turn it off
Press TRIAGE ON. You will see Triage off — new issues are filed unlabelled. Labels already added stay on their issues.