Agentic Index
Agentic AI Platform Change Log
Agentic Index tracks material changes across agentic AI platforms, including new agent capabilities, workflow orchestration updates, integrations, MCP/tool-calling changes, memory features, human approval controls, observability, deployment options, pricing, funding, and verification-status updates. This change log is the index that tracks changes to agentic AI platforms, updated weekly. If you are trying to keep up with changes to AI agent platforms without reading every vendor's release notes separately, this is the feed to read.
Follow this change log by RSS
Free for your reader, newsletter or automation tool. One feed covers the whole index, and every category has its own.
Public-source research. All entries are sourced from official vendor blogs, changelogs, documentation, or press materials. Support levels marked Needs Review or Publicly Claimed should be independently verified before relying on them for procurement decisions.
6 entries matching filters
Agent capability
AI-Powered Incident Communications moved from early access to rolling general availability. SRE Agent calls Scribe Agent to capture bridge audio from Zoom, Microsoft Teams or Google Meet and incident channel chat, then drafts internal and external status page updates for a responder to review and publish in Slack.
Writing status updates mid outage pulls responders off the fix, and this hands the drafting to agents while a person still approves what customers see.
Security / enterprise
Account admins in PagerDuty Advance can now choose which AI agents are enabled for each team, building on the team level access added in July.
Admins can roll out agents such as the SRE Agent team by team instead of all at once, keeping agent actions inside teams that have approved them.
Agent capability
PagerDuty made SRE Agent Skills generally available to PagerDuty Advance customers. Teams can supply custom instructions, scripts, and operational resources through the agent configuration page or PagerDuty Claude plugin. Skills define when to run, prerequisites, execution steps, error handling, and success criteria so the agent can apply local troubleshooting procedures during triage.
Operations teams can encode their runbooks and escalation conventions once instead of repeatedly explaining them during incidents. Buyers should validate trigger conditions and error handling against representative incidents before making a skill available across the account.
MCP / tool calling / API
PagerDuty made the GitHub Code tool for its SRE Agent generally available, so the agent can pull context from GitHub repositories while helping resolve incidents.
Code context lets the agent connect an alert to the change that caused it. Teams should check whether the tool reads only, or can also propose changes.
Agent capability
PagerDuty released AI-powered incident communications from Slack into Early Access. This capability allows responders to generate and distribute incident updates directly from their chat interface.
Reduces the manual effort required to keep stakeholders informed during critical incidents. Responders can maintain focus on resolution while leveraging AI to handle communication workflows without leaving Slack.
Integrations
PagerDuty released the PagerDuty Agent App in GitHub into Early Access, powered by the PagerDuty Advance MCP. The application gives developers direct access to PagerDuty data and the SRE Agent within GitHub to triage incidents, identify related code changes, and suggest fixes via pull requests.
Engineering teams can now evaluate deployment risks and remediate active incidents without leaving their core development environment. Embedding the SRE Agent directly into the GitHub workflow reduces context switching and accelerates incident resolution times.
Current rankings
These changes feed the index. See where each category stands: the best vendors of 2026, ranked by verified capability coverage.
Capability coverage
Every change above is graded against the same 14 capability axes. Each axis has its own page showing how much of the index documents it, which categories concentrate it, and the leading platform in each.
The AI agent directory for business · The full feature taxonomy · Pricing research
Common questions
How do I keep up with changes to AI agent platforms?
Read one maintained change log instead of tracking each vendor's release notes separately. The Agentic Index change log records 1648 verified updates across agentic AI platforms, updated weekly, covering new agent capabilities, MCP and tool calling changes, memory, human approval controls, observability, deployment options, pricing and funding. Every entry names the vendor, the date, the change type and an impact level, and links to that vendor's profile.
How often is the agentic AI change log updated?
Weekly. The most recent update was Oct 21, 2026, covering Equal AI, Kognitos, Findem.
How do I track changes for one specific AI agent vendor?
Filter the change log by vendor, or open that vendor's profile page, where the same verified entries appear alongside its capability coverage across the 14 point Agentic Index taxonomy.
Where can I find a single feed of agentic AI platform updates?
This page is that feed. Agentic Index reviews vendor blogs, changelogs, documentation and press materials every week and files what materially changed, so keeping up with changes to AI agent platforms is one page rather than several hundred. Entries are filterable by vendor, change type, impact level and verification status, and each one carries the evidence basis it was graded from. The same entries are published as a free RSS feed at agenticindex.io/feeds/changes.xml, with one feed per ranking category listed at agenticindex.io/use-this-data.
Last updated: Oct 21, 2026 · 1648 tracked changes across 550 vendors