Windsurf: Devin Oncall Is Now Generally Available for All Organizations
WindsurfWindsurf's Devin made Devin Oncall generally available to all organizations. Oncall responders watch Slack or Microsoft Teams channels and PagerDuty incidents, triage new alerts, bug reports and support requests, and investigate them using telemetry tools, code, deployments and runbooks. Devin posts a likely root cause and recommended next actions, can join incident channels to keep a self-updating incident report, and sends recurring Oncall reports.
Key Takeaways
- Devin Oncall is now generally available to all organizations, ending its limited availability.
- Responders watch Slack, Microsoft Teams and PagerDuty, so alerts, bug reports and support requests are triaged where teams already work.
- Devin goes beyond triage by investigating with telemetry, code, deployments and runbooks and posting a likely root cause and recommended next actions.
- During live incidents, Devin can join incident channels and maintain a self-updating incident report, reducing manual write-up work.
- Recurring Oncall reports summarize incidents investigated, issues identified and fixes shipped, giving teams a view of trends over time.
- Organization admins control setup, connecting tools and managing responders, while Oncall lives in the Devin sidebar for everyone else.
Sources & Mentions
1 external resource covering this update
Devin Oncall Reaches General Availability
Windsurf's Devin Oncall is now available to every organization, moving the incident response feature out of limited access. Oncall is found under Oncall in the Devin sidebar, and organization admins connect the tools it needs and manage the responders that run on them.
What Oncall Does
An Oncall responder watches the places where problems first surface. It monitors Slack or Microsoft Teams channels and PagerDuty incidents, then triages new alerts, bug reports and support requests as they arrive. Instead of only flagging an issue, Devin investigates it, drawing on the organization's telemetry tools, source code, deployments and runbooks.
The result of that investigation is posted back where the team is already working: a likely root cause together with recommended next actions. This turns the first, often slowest, stage of an incident (working out what is actually wrong) into something that can start before a human has opened a dashboard.
Staying With the Incident
Devin can also join incident channels and keep investigating as the situation develops. While it is there, it maintains a self-updating incident report, so the summary of what happened, what has been tried and what is still unknown stays current without someone manually writing it up.
Recurring Oncall Reports
Oncall also produces recurring reports. These summarize the incidents Devin investigated, the issues it identified and the fixes that shipped, giving teams a periodic view of how their on-call load looks and where problems keep recurring.
Setup and Who Manages It
Organization admins are responsible for connecting the tools Oncall relies on, such as chat channels, PagerDuty and telemetry sources, and for managing responders. Regular team members then see Devin's findings in the channels and incidents they already use. The general availability follows the earlier PagerDuty integration for Oncall response that Windsurf added in September 2026.