Engineering video
1:10 · 16 October 2026
An automated workflow uses hooks from Slack and Sentry to send bug context to an agent that checks if it is a real error or already in the backlog, followed by a refinement agent that estimates scope, blast radius, impacted services, and priority.
Hear it at 0:00 →And what happens right now is we have a triage agent ingesting issues that come either through Slack, Sentry, or they're usually reported. So all those are hooks and whenever a user reports a bug or we see an error popping up on Sentry, it will call. It'll send all the context to an agent and then the agent will try and see is this a real error? Is there something already in the backlog? Was it already fixed?
So that's the first step. We automated this kind of bug collection, then we have a refinement agent that will try to estimate. Scope, blast radius, how many services are impacted? If we make the change, what's the priority? Is it a life production bug that we need to fix ASAP and the size. So all this is the product work that we used to do. And the beautiful thing is this used to take days in a team.
Like you'd wake up, you'd be like, okay, what's let me reproduce the issue? And is this a real issue? And it was fairly mechanical. Like there's very few bugs that really need you to be present. So I really love this because it took away part of the work that me as an engineer, I didn't even liked. Again, all those are agents, so they try to estimate, they try to guess. Don't trust this as, oh, it's going to give the estimate as good as mine, but it will be good enough.
And for most changes, most small bugs, it's good enough. You don't need to spend more time on it. It's not worth it.
