Version 1.5.0 of AI, the canonical WordPress plugin for AI features, adds a screen that lets site owners choose which of their site's Abilities external AI agents can use. It also fixes two reported security advisories, and its developers say sites using the plugin should update promptly.

The release is dated 29 October 2026. Jeffrey Paul's release post followed on the Make WordPress AI blog on 2 November. The plugin's directory listing showed 1.5.0 as the current version when I checked it on 3 November.

Background

AI is the WordPress AI team's canonical plugin, which the release post calls "the canonical plugin powering AI-powered features in WordPress". It works with Abilities, which the Make WordPress glossary describes as registered, self-documenting units of functionality that agents and other tools can discover and run. Version 1.4.0, released on 5 October, renamed three of these Abilities and kept the old names working as deprecated aliases for the time being.

Six new experiments

The release post lists six new experiments:

Breaking changes for developers

Version 1.5.0 updates three general-purpose Abilities, core/content-query, core/users-query and core/settings-get, to match the versions the post says are "coming in WordPress core with 7.2 this December".

“These updates include breaking changes for existing integrations. The deprecated aliases introduced in earlier releases have now been removed.”

Jeffrey Paul, WordPress AI team, 2 November 2026

Code that still calls core/read-content, core/read-users or core/read-settings needs to move to the new names and schemas. The Markdown Feeds experiment has also changed. Individual post URLs using /<post>/feed/markdown/ are no longer supported, and consumers should request ?output_format=markdown instead.

Security fixes and settings changes

The release fixes two security advisories, listed as GHSA-7mwf-4ppp-cxmp and GHSA-g94j-h78j-rr2j. The release post gives their identifiers but does not describe them. It also says the release improves how private and password-protected post information is handled in AI-powered comment workflows, and adds protections around stored connector credentials.

“Sites using the AI plugin are encouraged to update promptly.”

Jeffrey Paul, WordPress AI team, 2 November 2026

The settings screen now separates stable Features from experiments. It marks which experiments run automatically, and shows what information each one sends to the configured AI provider and how many requests it makes. Mistral and Vercel AI Gateway have joined Anthropic, Google and OpenAI as featured connectors under Settings → Connectors.

Work planned for 1.6.0 and later includes an AI Workspace and Site Agent, Agent Users, and Internal Link Suggestions. The post says: "These concepts are still exploratory."

What this means for site owners

Analysis by Depakar B

If the AI plugin is installed on a live site, update it. Two security advisories are fixed, and the release post does not publish their details.

MCP Access is a useful step because it puts agent permissions on a screen an owner can review. WebMCP needs more care, because an agent that can save and publish posts is acting inside the editor of a logged-in user. Try both on a staging copy before you use them on a production site. My guide to setting up a WordPress staging site shows how.

If you or your developer built anything on the old Ability names, test it before you update. A silent failure in an automation is easy to miss.

About this report

This report is based on the WordPress AI team's release posts on make.wordpress.org and the plugin's WordPress.org directory listing. Facts and quotes are taken from the sources credited below, which I re-read on 3 November 2026. Sections marked "Analysis" are my own view. I am an independent WordPress developer and am not affiliated with the organisations named here.

Credits and sources

Corrections

Updated 5 November 2026, 11:40 IST:52 IST: removed an unsupported line saying each experiment is off until an administrator turns it on, made the "breaking changes" quote exact, corrected the Markdown feed path to /<post>/feed/markdown/, reworded the lead-image alt text, and added a background section, quotes and full source credits.

Spotted an error? Please contact me. Corrections are noted on this page with the date.