WorkerKit

AI workers for Sentry

AI workers for Sentry read your errors so a person does not have to watch the inbox: they find the issues that are new, spiking or back after a fix, read the stack trace and the events behind it, and hand the team a short brief with the issue links. Each worker acts as the Sentry user who connected it and uses only the tools you grant.

What is an AI worker for Sentry?

An AI worker for Sentry is an AI worker given one recurring job in the Sentry organizations the connected user can see: search errors, performance problems, traces and logs, open an issue to read its events and stack trace, and, where you grant it, comment on or update an issue. The connection uses Sentry sign-in, so there is no key to paste, and the worker sees exactly what that user sees. Tools are granted one by one per worker, so a reporting worker can read every issue without being able to change one.

What these workers do

Morning error triage brief

Read the issues that are new, spiking or regressed since yesterday in one project, rank them by users affected and recency, read the top ones' stack traces, and send the team a short brief with links.

Release health check

The morning after a deploy, compare the issues seen on the new release with the previous one, and name what the release introduced and what it fixed.

Stack trace to ticket

For each new high-impact issue, read the events and the trace, write a plain-language summary of where it fails and what the user was doing, and hand it to the engineer on call or file it in the team's tracker.

Weekly noise review

Once a week, list the issues that fire most and fix nothing, and suggest which ones to resolve, ignore or merge, for a person to approve.

How an AI worker runs in Sentry

Connect the right Sentry user

Start with reads

Name the organization and project

Writes reach your team

Sentry questions, answered.

Can a worker change anything in Sentry?

Only with the tools you grant it. Reading issues, events, traces and logs changes nothing. Commenting on an issue, assigning it, resolving it or creating a project are separate tools, granted per worker, and each one is visible to your team in Sentry like any other change by that user.

Which organizations does a worker see?

The ones the connected Sentry user can see. The connection does not add access and does not pick one organization, so a worker's instructions should name the organization and project it works on.

Does it work with self-hosted Sentry?

No. The connection uses Sentry's hosted service for sentry.io accounts. A self-hosted Sentry has no hosted connection to offer.

Will it keep running without me?

Workers run on their schedule with the connected user's access. Sentry can ask that user to sign in again from time to time; when that happens the worker reports that it could not connect, and reconnecting from the Apps page fixes it.

Browse Sentry kits

All apps