October 2026 Summaries

PagerDuty’s AI-Powered Incident Communications, now in rolling general availability, is designed to reduce the manual work of creating timely incident updates for internal stakeholders, partners, and customers. Its SRE Agent coordinates Scribe Agent, which captures conference-call audio and incident-channel chat across Zoom, Microsoft Teams, and Google Meet, generates live transcripts, and supports scheduled progress updates in Slack. Using captured incident context and standardized templates, the system can draft or refine internal and external status communications, including structured details such as incident status, affected services, impact level, and next-update timing. Responders review, edit, and publish drafts within the Slack incident channel or PagerDuty incident details page, while updates are organized into a single threaded status-page post. PagerDuty positions the capability as part of its broader autonomous operations strategy, keeping human responders responsible for approval while agents gather context, automate communication tasks, and preserve records for post-incident reviews and future incident response.

PagerDuty has launched a unified documentation site at docs.pagerduty.com to consolidate 1,200 pages previously distributed across 21 subdomains and four publishing platforms. Designed for both human users and AI assistants, the site organizes material around operational tasks and PagerDuty’s product pillars, combines support and developer content in a shared navigation structure, and provides consistent layouts, persistent light and dark modes, and instant full-corpus search. Each page includes options to copy content as Markdown, view raw source, or open it in an AI assistant, while machine-readable features such as page-level Markdown versions, llms.txt, llms-full.txt, open crawling, and structured data aim to give AI systems accurate, canonical documentation rather than relying on fragmented or outdated sources. PagerDuty presents the effort as part of its broader autonomous operations strategy, intended to help teams find reliable answers more quickly, reduce support needs, and prevent documentation gaps from contributing to incidents.

PagerDuty has made its Runbook Automation/Rundeck MCP Server generally available for Rundeck and self-hosted Runbook Automation customers running version 6.1.0 or later, enabling AI assistants such as Claude, Cursor, VS Code, and Codex to interact directly with customers’ automation instances. Through a permissioned MCP connection, assistants can inspect real instance details such as installed plugins, existing jobs, schemas, and access controls, allowing them to create validated jobs, execute and summarize runs, search projects and job histories, and draft ACL policies from natural-language requests. The server uses the customer’s API token, validates job and policy definitions before application, and requires human confirmation for destructive actions. PagerDuty presents the capability as a way to reduce onboarding and operational friction while supporting its broader autonomous-operations strategy of using intelligent agents to accelerate incident resolution and automate routine work under controlled security safeguards.