How We Built an Automated Debugging Workflow at Sentry

Dhrumil Parekh on Sentry using its own Seer agent against its own repos. Seer root-causes incoming issues and opens fix PRs; an hourly Claude routine then scans a dedicated Slack channel for PRs opened in the last four hours, asks Seer to work out from commit history who knows the affected code best, checks the PR is still open, and pings that person to merge, close, or give feedback.

The reported effects are modest but consistent: roughly 21% more action on PRs, 13% better response within 48 hours, and 12.5% more PRs closed without merging. They read that last one as a good sign rather than a bad one, since the rejections tend to be duplicate fixes or cases where an engineer wanted a more thorough solution.

The framing I liked, and the reason this is more interesting than most agent-in-production writeups, is that the automation is aimed at the handoff rather than the fix. The agent finds a plausible patch, but the design work went into getting the right human to look at it at the right moment, down to details like never double-posting and never pinging at the weekend. As Parekh puts it, automation “is all about creating less manual work for your engineers, not reducing the number you have.”