Linear Issue Triage Agent

Linear teams file fast, which is the point, and it also means the triage view fills with one line issues carrying no labels and the same crash reported by three people who each thought they were first. This agent reaches every issue as it is created: it searches the workspace for that symptom, applies labels you already use, assigns from your area map, and asks once for the build number or workspace id that is missing. Opening Linear becomes a review of triage rather than the doing of it.

What people use it for

• Triage view at zero - Issues are labelled and owned within a minute of being filed, so the view your team is supposed to clear each morning is already clear. Nobody draws the short straw at standup.
• Catch the lookalike first - A workspace search runs before a single word is written, so a re-report arrives with the original identifier quoted in the comment instead of turning into a parallel investigation two engineers pursue separately.
• Ask for the build number once - Issues filed from Slack shortcuts and support handoffs almost never carry version, platform, or workspace id. The comment names exactly the ones missing, so the reporter answers in a line.
• Break the room only for outages - Slack fires for issues that clear the urgent bar you wrote and nothing softer, quoting the issue identifier, its title, and whatever cleared that bar.

Before you fork

Will it start inventing labels in our workspace?

No. It reads your existing label list on every run and can only apply what is already there. If your guide names a label nobody has created yet, the agent says so in the comment instead of creating one, which keeps label sprawl a decision your team makes deliberately.

What happens when the search finds something similar that is not actually a duplicate?

It writes the identifier into the comment as a possible duplicate and stops. It never merges, never closes, and never marks a relation, because deciding two reports are the same bug takes context the agent does not have. Two seconds of a human reading one line beats an auto merge you have to unpick.

What does it need connected, and what does a run cost?

A Linear credential that can read and update issues in the team you want triaged, plus a Slack channel for the urgent ones. It runs once per issue created, and a run is a search, a couple of reads, and one comment, so cost follows how many issues you file and not how big your workspace is. A team opening 25 issues a day is 25 small runs a day.