Linear Issue Triage Agent with OpenCode
Triage goes wrong quietly: a label nobody uses gets created, an owner is picked because the name looked close, or the comment repeats back what the reporter already typed. This template closes those off with data rather than restraint, since labels come from the live workspace list, owners resolve against real members, and the comment is capped at three sentences. OpenCode suits that arrangement, being light to point at one narrow loop while the constraint lives outside the model.
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.
iOS app signs the user out when the phone hands off from wifi to LTE
created by Aditi Raghunathan
Started with build 5.9.1, which shipped Tuesday. On iOS 18.4, walk out of wifi range with the app open and the session token gets dropped, so the next tap lands on the login screen. Nine people in the beta channel hit it today, two of them on the Kerslake account. Android is unaffected.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Linear
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 triage rules in plain English - which labels you genuinely use and what each one means, what clears the urgent bar, and the repro details your engineers always end up chasing. Nothing gets classified from anywhere else.
Team map
Each area of the product and the Linear member who owns it, and where to send an issue whose area is not obvious.
Runs on OpenCode
Preselected for this page — connect your OpenCode 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 OpenCode for this agent
Rules carry the weight
The label list and the member list are fetched on every run, so the agent picks from what exists rather than inventing. A lighter harness is fine when the guardrail is the data it was handed.
Swap the engine, keep the guide
OpenCode is model agnostic, so the model behind triage can change without touching your triage guide or your area map. The behaviour you tuned survives the swap.
Before you fork
What happens if Linear returns an error halfway through a run?
The run is marked failed with the error attached, and any write that already landed stays landed. In practice that is an issue labelled but not yet commented on, which the next person sees in triage. Nothing is queued for a silent retry, so a revoked credential shows up as failed runs rather than as issues that quietly stop being triaged.
Run it with a different agent
Put Linear Issue Triage Agent to work on OpenCode
Free to start. Guided setup, a test run against staged conversations, and it's live.