CI alert email is noisy, and most of it is ignorable. If you've ever owned a pipeline at any scale, you know the shape of it: a flaky integration test trips, GitHub Actions emails you, a retry passes, and now there are three messages in your inbox about a problem that fixed itself. Multiply that by every branch, every nightly, every deploy, and the signal you actually care about — the one real failure — is buried under forty notifications that all look identical until you open them.
The usual fix is to wire alerts into Slack and add a bot that reacts to emoji. That works right up until the channel becomes the new noisy inbox. The other usual fix is to point an LLM at a human's mailbox and let it "summarize your morning." That's a demo, not a system — the moment you want the summarizer to reply, to be a participant in the alert thread that on-call is reading, you need it to own an address, not borrow yours.
That's the angle here. Give the triage agent its own inbox. Your CI system already knows how to email failures somewhere — point it at an address the agent controls, let the agent cluster and summarize the incoming alerts, and have it reply in the same thread with a probable root cause so whoever's on-call reads one message instead of forty.
