Devin Oncall Explained: AI Incident Response Buyers Guide
Cognition launched Devin Oncall on October 15, 2026, extending its coding agent into production incident response. This buyer guide explains what the AI on-call agent does and the questions every custom software buyer should ask about monitoring, SLAs, review gates and rollback readiness.
The Short Answer
On October 15, 2026, Cognition extended its Devin coding agent into production operations with a launch called Devin Oncall. The product investigates alerts and bug reports, traces causes through infrastructure, logs, traces and code, joins incident channels and can open a tested pull request with video evidence for engineer review. When a person is needed,…
On October 15, 2026, Cognition extended its Devin coding agent into production operations with a launch called Devin Oncall. The product investigates alerts and bug reports, traces causes through infrastructure, logs, traces and code, joins incident channels and can open a tested pull request with video evidence for engineer review. When a person is needed, it escalates with severity, suspected root cause and a recommended next step. Cognition says the system already handles thousands of production alerts a day for some of the world's largest companies, a claim the company has not backed with named customers or further figures.
For buyers of custom software, this launch matters for a different reason than the headlines suggest. The real question is not whether an AI agent can answer a page at 3 a.m. It is what your software partner does when alerts fire, who reviews the fix, how fast service is restored, and what safeguards stop an automated change from making a bad night worse. This guide explains what Devin Oncall does, what the launch reveals about modern incident response, and the exact questions to ask any development partner before your system goes live.
What Devin Oncall Actually Does
Cognition describes three core uses for the product. In alert triage, Devin follows alerts through infrastructure, logs, traces and code to find the underlying cause, and when a person is needed it escalates with the severity, suspected root cause and recommended next step. As an incident teammate, it joins incident channels automatically and investigates alongside the team, keeping the timeline, findings and decisions current. For bug reports and questions, it reproduces reported bugs and, when a fix is needed, opens a tested pull request with video evidence.
At launch, Devin Oncall connected to the collaboration and observability tools teams already use. The announced integrations cover Slack and Teams for incident channels, Datadog, New Relic, Sentry, Grafana and Dynatrace for monitoring and telemetry, and Jira, Linear and ServiceNow for ticketing and service management. That list matters more than it looks, because an AI agent is only as useful as the systems it can read. An incident responder that cannot see your traces, your recent deploys or your runbooks is just another alert forwarder.
It is also worth noting how Cognition frames the product. The launch message says Devin "answers pages first, escalates to a human when needed, and learns from every alert." The agent investigates and prepares; an engineer still reviews and approves. Any vendor telling you a different story about fully autonomous incident resolution should be asked for evidence.
Why On-Call Response Is the Bottleneck Custom Software Buyers Should Care About
When you buy custom software, most of the negotiation focuses on features, timelines and design. Incident response gets a paragraph, which is a mistake, because the numbers show it is where systems quietly fail their owners.
Industry data puts the average mean time to resolution (MTTR) for production incidents at roughly 3.5 hours, with about 75% of that time spent on diagnosis rather than on the fix itself. During major incidents, teams can face 200 to 500 or more alerts, and an estimated 85 to 90% of those alerts are duplicates or symptoms rather than root causes. The problem is not detection. Modern monitoring notices deviations well. The problem is understanding which deviation matters and what actually broke.
That is also why AI-assisted incident response is gaining real traction beyond marketing claims. A 2025 Forrester Consulting study commissioned by IBM found that companies deploying AI-driven performance monitoring achieved a 40% reduction in mean time to resolution for critical incidents. Separately, the DORA research program continues to find that elite performers restore service for most incidents in under an hour. The gap between average teams and elite teams is not better luck. It is faster, more structured diagnosis.
Devin Oncall is the clearest sign yet that this capability is moving from specialist AIOps platforms into the general coding-agent stack. Whether or not you ever use Devin's product, the launch tells you what to expect from the market: alert triage agents will become a standard part of production software, and your software partner should already have a clear position on them.
Devin Oncall and the Trust Test: Every AI Fix Must Stay Reviewable and Rollback-Ready
Here is the original insight most coverage of this launch skips. Cognition's headline number is "thousands of alerts a day." That is a volume claim, not a quality claim. It tells you nothing about how many were resolved correctly, how many needed rework, or how many fixes introduced new problems. A buyer evaluating any AI incident response tool, including this one, should treat volume as a footnote and ask about resolution quality instead.
An AI agent that opens pull requests only earns trust if every fix stays reviewable and rollback-ready. "Reviewable" means a human can see exactly what the agent changed, what evidence it used, and why it believes the change addresses the root cause. Devin Oncall's habit of attaching video evidence to its tested pull requests is a step in the right direction, because evidence beats assertion when someone is deciding whether to merge at 3 a.m. "Rollback-ready" means the fix can be undone in minutes if it makes things worse, through feature flags, staged rollouts or one-click reverts, not a manual scramble.
This is also where governance matters. An agent that touches production code, ticketing and communication channels is a powerful privileged actor, and the rules for governing it should be written before it is switched on. Our guide on how to govern hundreds of AI agents covers the access controls, audit trails and approval workflows that separate a useful agent from a liability. And because AI-generated fixes still need human-grade verification, the discipline in our QA playbook for testing AI-generated code applies directly: every machine-proposed change gets the same test bar as a human one, or higher.
Questions to Ask Your Software Partner Before Launch
The Devin Oncall launch is a useful trigger for a conversation every buyer should have with their development partner. Use these questions before you sign, not after your first outage.
- What does your on-call rotation look like? Ask who gets paged, how escalation works, and what happens if the primary responder is unavailable. A partner with no documented rotation is a partner planning to improvise during your outage.
- What monitoring and alerting is wired into my system? Ask which tools cover logs, metrics, traces and uptime, and how alerts are deduplicated so engineers are not buried in noise. If your partner cannot name the observability stack, that is your answer.
- What are the SLA response and resolution targets? Get severity definitions in writing, with response and resolution time targets per severity, and ask how performance against them is reported to you.
- Who reviews a fix before it reaches production? Ask about the review gates for emergency changes: required approvals, automated test suites, and whether hotfixes can bypass the normal pipeline. The answer should include a named human approver.
- How fast can a bad deploy be rolled back? Ask for the rollback mechanism and its expected time, and ask when it was last exercised. A rollback plan nobody has tested is a hope, not a plan.
- Do you run blameless postmortems? Ask what happens after an incident: a written timeline, root cause, and prevention items with owners and deadlines. Partners who learn from incidents are partners whose systems get more reliable over time.
For custom enterprise software, these questions matter more than for off-the-shelf products, because there is no vendor support line to fall back on. You own the system, which means the incident response process is part of what you are buying. If you are still weighing build versus buy, our comparison of custom vs off-the-shelf software in 2026 walks through how support and operational responsibility differ between the two paths.
Review Gates: What to Demand Before Any Automated Fix Ships
If your partner uses an AI incident response agent, or plans to, insist on these gates. They apply equally to Devin Oncall and to any competing tool.
| Gate | What it should look like | Why it matters |
|---|---|---|
| Human approval | A named engineer approves every production change, with no silent auto-merge. | Stops confident-looking but wrong fixes from shipping unattended. |
| Evidence bundle | The agent links the traces, logs and reproduction steps behind its diagnosis. | Lets the reviewer verify the root cause instead of trusting the summary. |
| Tested change | The fix passes the project's automated suite before review is requested. | Catches regressions the agent cannot reason about. |
| Staged rollout | Fixes deploy to a subset of traffic or behind a feature flag first. | Limits blast radius if the fix is wrong. |
| One-click rollback | Reverting takes minutes through a tested, documented path. | Turns a bad fix into a short incident instead of a long one. |
| Full audit log | Every agent action, from alert read to PR opened, is recorded and attributable. | Enables real postmortems and satisfies compliance requirements. |
How Buyers Should Evaluate an AI Incident Response Agent
When a vendor pitches AI on-call capability, separate the demonstration from the deployment reality. Ask which systems the agent can read and which it can change, and demand those be different lists. Read access to telemetry is low risk. Write access to production code or infrastructure is high risk and should require explicit approval per action or per change window.
Ask where the agent's context lives. Incident history, runbooks and learned patterns are the valuable part of an AI on-call setup, and if they live only inside one vendor's platform, switching vendors later means starting over. Keep runbooks and incident records somewhere you control regardless of which agent reads them.
Ask about failure modes, including the agent's own downtime. An AI on-call agent runs on someone else's hosted platform, which makes it a new dependency in your incident chain. What happens when the agent is unreachable during your outage? Your runbooks should still work with humans alone.
Finally, ask for references tied to resolution quality, not alert volume. "Thousands of alerts a day" is interesting. Median time to resolution with the agent versus without it, the share of agent-proposed fixes accepted without rework, and the rate of agent-caused regressions are the numbers that matter. If a vendor cannot share them, treat the capability as unproven and price your risk accordingly.
There is a related lesson from infrastructure work. Many incidents trace back not to code bugs but to environment changes made under pressure, which is why our breakdown of cloud migration mistakes that cost businesses millions in 2026 is worth reading alongside this guide. The monitoring, rollback and staging discipline that prevents migration disasters is the same discipline that makes AI-assisted incident response safe.
Frequently Asked Questions
What is Devin Oncall?
Devin Oncall is Cognition's AI incident response product, launched on October 15, 2026. It extends the Devin coding agent into production operations: it investigates alerts and bug reports, traces causes through infrastructure, logs, traces and code, joins incident channels, and can open a tested pull request with video evidence. When a human is needed, it escalates with severity, suspected root cause and a recommended next step.
Does Devin Oncall replace on-call engineers?
No. The product is designed as an incident teammate that investigates and prepares fixes for human review, not as a replacement for engineers. The fix still requires a person to approve and merge it. Buyers should be skeptical of any vendor claiming fully autonomous incident resolution without a human in the loop.
Which tools does Devin Oncall connect to?
At launch, the announced integrations include Slack and Teams for communication, Datadog, New Relic, Sentry, Grafana and Dynatrace for monitoring and observability, and Jira, Linear and ServiceNow for ticketing and service management.
Is handling "thousands of alerts a day" proof the tool works?
No. Alert volume is a throughput claim, not a resolution-quality claim. It does not say how many incidents were resolved correctly, how many fixes needed rework, or how many changes caused new problems. Ask vendors for median time to resolution, fix acceptance rates and regression rates instead.
What should I ask my software partner about AI incident response?
Ask who approves AI-proposed changes, what evidence the agent must attach, how fixes are tested and rolled out, how rollbacks work, where the audit log lives, and what happens when the agent itself is down. Every automated fix should be reviewable and rollback-ready.
Should AI incident response change my SLA expectations?
It can shorten diagnosis time, which is where most MTTR is spent, but it does not remove the need for written SLAs. Keep severity definitions, response and resolution targets, and reporting requirements in your contract regardless of which tools your partner uses.
If you are commissioning custom software, make incident response part of the brief from day one. Monitoring, escalation paths, review gates and rollback discipline are not extras to add after launch. They are the difference between a system you own confidently and one that owns your weekends. Contact our team to discuss how we build production-ready systems with clear SLAs, tested rollback paths and review gates that keep every change, human or AI-made, accountable.
Related Articles
Keep reading — more guides you may find useful.
Related Services
Services connected to this guide.
