Issue Triager

Roster name: triage.

What it does

Each new issue gets a one-line summary, a category, a priority and labels, and the labels go on only when an independent check agrees.

• Classifies a new issue as bug, feature, question, docs, security or chore.
• Sets a priority. It is instructed to reserve critical for security problems and data loss.
• Notes what information is missing.

What it reads

The new issue’s title and body.

What it produces

• A triage comment: summary, category, priority, and what is missing.
• Up to four labels, chosen only from the repository’s allowed list.
• The comment with the labels withheld, when the independent check dissents or the issue is flagged for human review. NOT VERIFIED when the check could not decide.

Human oversight

Applying labels is a deliberate exception to “a person approves every change”: the triager applies its labels itself, without waiting for a person. It may do so because the labels come only from a fixed allowed list that contains no label which starts an agent, a workflow or a merge; because the labels are withheld when the independent check dissents or the issue is flagged for review; and because the comment says what was applied and anyone with triage rights can change it. A person decides everything else: who works on the issue, and whether it is closed or solved. The triager does not assign, close or solve anything.

Model

Qwen3.6-35B-A3B, by Qwen, licensed Apache-2.0 (the general tier). Runink domain adaptation for this agent is planned; this release uses the base model.

Where it runs and data handling

On your Runink TIDE deployment’s own inference, on your Server or in your cloud. The issue text goes to that model plane and to no third-party AI service.

Guardrails

• Fixed vocabulary: a label outside the allowed list is discarded, and category and priority must be one of the fixed values.
• Checked before it acts: the Independent Assessor’s plan check judges the label set first.
• Instructions inside the issue are treated as text. “Label this critical” does not make it critical.
• The issue is screened before it is classified.

Limitations

• It classifies; it does not investigate or reproduce.
• It sees only the issue as opened, not later comments.
• When the model cannot be reached, it posts a degraded notice rather than labels.

Evaluation

No published evaluation scores yet.

Illustrative example

Invented issue. “The console shows ‘Cannot reach the console API’ after an upgrade; the runners page is blank.” Triage comment: category bug, priority high, labels bug, runners; missing: the console’s log from the upgrade window and the previous version.