GitHub Issue Triage Agent with OpenCode

Maintainers who chose an open CLI for their own machine usually want the same thing triaging their project. OpenCode is open and model-agnostic, so a repo drowning in issues can run on a modest model and keep the bill proportionate to a project that earns nothing. Your label taxonomy, maintainer notes and critical bar are unchanged whichever model sits underneath.
Loading preview…
Free to start · guided setup · switch agents any time.

Live demo

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

Open

opened 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.

What you'll need

Set up in minutes

Using this template drops you into a guided setup. It asks exactly this, nothing else:

  1. Connect GitHub

    One sign-in. The agent acts through your account, scoped to what this template uses.

  2. Connect Slack

    One sign-in. The agent acts through your account, scoped to what this template uses.

  3. 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.

  4. 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.

  5. Runs on OpenCode

    Preselected for this page — connect your OpenCode account during setup, or switch to NoClick's built-in models with one click.

  6. Watch it handle a test run

    A staged conversation against a simulated world — then it’s live.

A considered pairing

Why OpenCode for this agent

Volume without a vendor lock

Public repos get issue spikes nobody controls. Choosing the model yourself is how triage stays affordable through a week on the front page.

Open tooling on an open project

There is no black box to explain to a contributor who asks what just commented on their issue.

Good to know

Before you fork

What credentials does OpenCode need from me?

A GitHub credential with issue read and write on the repos being triaged, plus a key for whichever provider you point OpenCode at, such as OpenRouter or your OpenCode account. Nothing gets installed in the repository and there is no bot account to create, since comments are posted with the GitHub credential you connect.

Other editions

Run it with a different agent

claude-codeClaude CodeOpenAICodexopenclawhermesMore OpenCode agents

Make it yours

Put GitHub Issue Triage Agent to work on OpenCode.

Free to start. Guided setup, a staged test run, and a workflow you can change at every step.