GitHub Issue Triage Agent with Hermes
Hermes runs on Nous Research's open models, which appeals to maintainers who would rather not have a closed model writing in their issue tracker. The reasoning it needs here is ordinary and important: is this the same bug as the old one, what is missing from this report, does it clear the critical bar you set. Everything it produces is one comment in the tone you described.
Watch it work before it's live
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
Webhook retries fire twice when the first attempt times out
Openopened by Priya Raghunathan
On v4.2.1 self-hosted, a webhook whose first delivery hits the 10 second timeout is retried, but the receiver gets both the retry and the original once it finally completes. Steps: create a webhook pointing at an endpoint that sleeps 12 seconds, trigger it once, watch the receiver log two deliveries with the same event id about 40 seconds apart. Expected one delivery per event, or at least the same event id deduped. This started for us after upgrading from 4.1.6, where the same endpoint only ever received one call.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect GitHub
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Triage guide
Your label taxonomy and who owns what - the labels you actually use, what each one means, which team or person owns each area, and what counts as critical. The agent only ever labels and routes from this.
Maintainer notes
The repro details you always end up asking for, the parts of the codebase that break most often, and the tone you want used with contributors.
Runs on Hermes
Preselected for this page — connect your Hermes account during setup, or switch to NoClick's built-in models with one click.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
Why Hermes for this agent
Open project, open model
Contributors can see the whole stack that answered them, which is an easier thing to explain in a community than an unnamed vendor model.
Judging thin reports
Working out what a vague report is actually missing takes general reasoning rather than code generation. That is what this harness is built around.
Before you fork
Is an open model safe to let comment in public?
The blast radius comes from the tools rather than the model: existing labels, one comment of two to four sentences, no closing, editing or code access. Rehearse on the three staged issues first, especially the vague one, since that is where an off tone shows up. Anything outside your triage guide is handed to a maintainer instead of answered.
Run it with a different agent
Put GitHub Issue Triage Agent to work on Hermes
Free to start. Guided setup, a test run against staged conversations, and it's live.