Your Next On-Call Engineer Doesn't Sleep · AI Automation Agency Hub

Your Next On-Call Engineer Doesn't Sleep

It's 3 a.m. and production is down.

What if the first responder wasn't you?

Cognition just made Devin Oncall generally available. It picks up production alerts and bug reports before an engineer does, then:

→ Digs through logs and code

→ Escalates with the severity, the likely root cause and a suggested next step

→ Or opens a tested PR to fix it

It also remembers past incidents. By recognising known issues and grouping related alerts, it skips about 60% of repeat investigations.

The customer numbers Cognition shared:

→ AngelList: 50% of incidents handled end to end, and 3.5x more correct root causes than its in-house tool

→ Reducto: Devin flagged a problem from early warning signs and opened an incident before the production alerts fired

The design choice which is most interesting: a second "review" agent runs alongside the investigator. Its job is to catch weak reasoning, like treating a recent deploy as the cause just because the timing lines up.

That's the same pattern showing up everywhere this month. One agent does the work. A separate one checks it.

On-call is a great place for agents, because the first hour of an incident is mostly gathering context. But it's better to start with "investigate and escalate" and earn trust before letting it ship fixes on its own.

A good trial: replay last month's incidents and compare its root cause with what your team actually found.

2 comments

Your Next On-Call Engineer Doesn't Sleep