Use casesTriage

Error triage that starts the moment a new error spikes

Mitra triages new errors for you. When a Sentry issue starts affecting real users, the agent opens a Linear issue with the stack trace. It names the person who last touched that code, posts a link to your engineering channel, and records every run.

Runs: Whenever a new error spikes
Used by: Engineering

The prompt

When a new Sentry issue hits real users, open a Linear issue with the stack trace. Post it to #eng with whoever last changed that file.

Sentry

GitHub

Linear

Slack

Build this agent

200 credits to start · no credit card

What the agent actually does.

Catch the new Sentry issue
The agent picks up issues Sentry has not seen before, with the trace, the release and how many people it hit.
Check that real users are hit
Errors from bots, retired releases or a single internal session drop out before anything goes further.
Find who touched the code
The files in the stack trace are matched against GitHub history to name the last person who changed them.
Open the Linear issue
One issue per error, carrying the trace, the release, the user count and that name, on the owning team.
Post the link to #eng
A short Slack message names the error, how many people it reached and where the issue now lives.

Make it yours.

For small teams with no triage rotation, where a new error is spotted by whoever happens to open Sentry that day. Change any of this by saying so — there is nothing to rewire.

Open an issue only once an error has hit a set number of users.
Assign the issue to the person who last changed the code.
Skip Slack, and let the Linear board be the only place errors show up.

Questions, answered.

How do I get Sentry errors into Linear automatically?

Mitra opens a Linear issue for each new Sentry error, with the stack trace, the release it appeared in and a link back to Sentry. You describe which errors deserve an issue, such as only the ones affecting real users, and the agent applies that rule on every run.

How does an agent know who should fix a new error?

Mitra reads the GitHub history for the files in the stack trace and names whoever changed them last, in both the Linear issue and the Slack post. That is a suggestion rather than an assignment, and your team still decides who picks the error up.