How we handle GDPR data-subject requests on a deadline
Legal
The error-triage agent we run on Kortix — connected to Sentry and GitHub. Hourly, it groups new and spiking errors, dedupes against our existing GitHub issues, and drafts an issue with the stack trace and impact for the top offenders, then alerts Slack. It never resolves, ignores, or assigns an error itself.
Sentry catches every error. Turning that stream into work someone actually picks up is a different problem. New error types pile up next to ones that have been spiking for days, half of them already have a GitHub issue somewhere and half don't, and by the time an engineer has the hour to sit down and sort it, the backlog is long enough that sorting it feels like its own project. Most weeks, no one has that hour, so the backlog just grows.
We run an error-triage agent on Kortix that grooms that backlog every hour. It reads the current state of Sentry, groups new and spiking errors, checks which ones already have a tracked GitHub issue, and drafts an issue with the stack trace and impact for the ones that don't — then posts a summary to Slack. This is grooming, not paging: it doesn't wake anyone up and it doesn't decide anything is fixed.
A Sentry project accumulates issues faster than anyone triages them. Some are brand new. Some have been sitting unresolved for weeks at a low, steady rate. Some just started spiking after today's deploy. Working out which of those deserve an engineer's attention — and whether that attention already exists as an open GitHub issue — means reading the whole backlog by hand, which is exactly the task that gets deferred every time something more urgent comes up.
The common fixes don't groom the backlog, they just move it. Auto-creating a GitHub issue for every Sentry error floods the tracker with duplicates and one-offs no one will ever action. Leaving Sentry as the system of record means the backlog is only as current as the last time someone opened the dashboard. And on-call triage tools are built for the opposite end of the problem — one loud alert right now — not the quiet pile of errors that never paged anyone but still need a decision.
On Kortix, an hourly cron triggers an agent. It spawns a fresh session with read-only access to Sentry, pulls the errors that are new or whose event frequency has spiked over their trailing baseline, and groups them by fingerprint. For each one, it checks our GitHub repo for an existing issue before doing anything else. For the top offenders that aren't already tracked, it drafts a GitHub issue with the stack trace and the impact — event count, affected users, first seen — and posts a summary of what's new, what's spiking, and what got drafted to Slack. It never touches Sentry's issue state and never assigns anything.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the triage skill and the hourly trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up an hourly error triage agent in this workspace.
Create the agent agents/error-triage.md. Its job is to groom the Sentry backlog into a short list of GitHub issues. It may use the Sentry and Slack connectors and a GH_TOKEN secret for GitHub.
Create the skill skills/error-backlog-triage/SKILL.md with these rules:
Add a cron trigger hourly-error-backlog-sweep to kortix.yaml. It runs the error-triage agent every hour, on the hour, with the prompt "Load the error-backlog-triage skill and run one complete sweep of the web project."
Tell me which of these connectors are not connected yet.
Open a change request with all of it. Do not merge it.
Open Connectors in your workspace and connect your error tracker and Slack.
Credentials are brokered server-side and never enter the agent's machine. Add a GitHub token as the GH_TOKEN secret so the agent can draft
issues.
Reads new and spiking errors, read-only.
Skips tracked errors and drafts issues for the rest.
Posts the sweep summary.
Merge the change request, then start a session with the error-triage agent and send this prompt. Read the drafted issues before you let the schedule take over.
Run one error-backlog sweep of the web project in Sentry.
The change request added this trigger to kortix.yaml. From now on the agent
runs every hour, on the hour, each run in a new session on its own cloud
computer.
To change the time, edit the cron line, or open Triggers in the workspace.
triggers:- slug: hourly-error-backlog-sweep name: Hourly error-backlog sweep on: cron: "0 0 * * * *" run: agent: error-triage prompt: Load the error-backlog-triage skill and run one complete sweep of the web project.Sentry access is read-only. The agent never resolves, ignores or mutes an error, and a drafted GitHub issue has no assignee. It drafts at most 5 issues per sweep. The team decides priority and ownership.
A sweep that finds new or spiking errors posts one summary, and a quiet sweep posts nothing. This is what a run looks like in the session:
Found 4 new and 3 spiking errors. 4 were already tracked, so the agent drafted 3 issues. The top one, a TypeError in checkout, had 1,240 events from 312 users this hour.
Once it works, paste any of these into the same session.
For each drafted issue, find the latest commit that touched the top frame of the stack trace and link it in the issue body.
Every weekday at 09:00, post to #eng-errors the 5 errors with the most affected users in the last 24 hours and their issue links.
When a new release appears in Sentry, run a sweep right away and compare its error rate with the previous release.
The agent reads production error telemetry and writes issues others will act on, so its access is scoped and one-directional:
The error backlog that used to need a dedicated hour to sort now arrives pre-groomed every hour: new errors and real spikes ranked by impact, checked against what's already tracked, and the top offenders already drafted as issues with the trace attached. The team spends its time deciding what to fix, not rediscovering what's broken.