GitHub Issue Triage Agent with OpenClaw
Some repos need triage more than they need a triage project. OpenClaw is the quickest of the five to get onto a repository: hosted, nothing to install, and the setup is your label taxonomy plus the repro details you are tired of asking for. It stays inside the rails the prompt draws, using labels that already exist and leaving one comment per issue.
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 OpenClaw
Preselected for this page — connect your OpenClaw 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 OpenClaw for this agent
From repo to triaged
No local environment, no bot to register, no infrastructure to babysit. Connect GitHub, write the guide, rehearse on the staged issues.
Narrow by construction
One comment, existing labels only, no closing or editing anything. A straightforward agent on a tight tool set is hard to embarrass yourself with.
Before you fork
Can I move this to a different harness once it is running?
Yes, the harness is a single field on the agent. Your triage guide, maintainer notes, GitHub connection, Slack channel and staged issues all stay put, so trying Claude Code or Codex later means one setting and a re-run of the test issues. Most people start simple and only switch if duplicate detection starts missing things.
Run it with a different agent
Put GitHub Issue Triage Agent to work on OpenClaw
Free to start. Guided setup, a test run against staged conversations, and it's live.