Title: WordPress AI | AI Team Updates

---

 [  ](https://profiles.wordpress.org/eidolonnight/) [Nicholas Garofalo](https://profiles.wordpress.org/eidolonnight/)
2:19 pm _on_ 3 November 2026     
Tags: [make.wordpress.org/marketing ( 2 )](https://make.wordpress.org/ai/tag/make-wordpress-org-marketing/),
[p2-xpost ( 14 )](https://make.wordpress.org/ai/tag/p2-xpost/)   

# 󠀁[X-post: Updates to the WordPress Marketing Repository](https://make.wordpress.org/ai/2026/11/03/xpost-wp-marketing-repo/)󠁿

X-post from [+make.wordpress.org/marketing](https://make.wordpress.org/marketing/):
[Updates to the WordPress Marketing Repository](https://make.wordpress.org/marketing/2026/11/03/wp-marketing-repo/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fai%2F2026%2F11%2F03%2Fxpost-wp-marketing-repo%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/jeffpaul/) [Jeffrey Paul](https://profiles.wordpress.org/jeffpaul/)
10:59 pm _on_ 2 November 2026     
Tags: [AI Experiments ( 17 )](https://make.wordpress.org/ai/tag/ai-experiments/),
[AI Features ( 10 )](https://make.wordpress.org/ai/tag/ai-features/), [AI Plugin ( 10 )](https://make.wordpress.org/ai/tag/ai-plugin/),
[ai-release ( 15 )](https://make.wordpress.org/ai/tag/ai-release/), [canonical plugins ( 17 )](https://make.wordpress.org/ai/tag/canonical-plugins/),
[core-ai ( 88 )](https://make.wordpress.org/ai/tag/core-ai/)   

# 󠀁[What’s new in AI 1.5.0 (29 OCTOBER 2026)?](https://make.wordpress.org/ai/2026/11/02/whats-new-in-ai-1-5-0/)󠁿

**AI 1.5.0** has been released and is [available for download](https://wordpress.org/plugins/ai/)!“
What’s new in AI…” posts (labeled with the [#ai-release tag](https://make.wordpress.org/ai/tag/ai-release/))
are posted following every AI pluginPlugin A plugin is a piece of software containing
a group of functions that can be added to a WordPress website. They can extend functionality
or add new features to your WordPress websites. WordPress plugins are written in
the PHP programming language and integrate seamlessly with WordPress. These can 
be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
or can be cost-based plugin from a third-party. release, showcasing new features
included in each release.

![Text graphic titled 'What's New In AI 1.5.0?' on a light pink background.](https://
make.wordpress.org/ai/files/2026/11/ai-1-5-0-scaled.png)

We’re pleased to announce the release of [AI 1.5.0](https://github.com/WordPress/ai/releases/tag/1.5.0),
the latest update to the canonical plugin powering AI-powered features in WordPress.
This release introduces six new Experiments, including Text to Speech, Content Verification,
MCP Access, WebMCP, Revision Change Summary, and BlockBlock Block is the abstract
term used to describe units of markup that, composed together, form the content 
or layout of a webpage using the WordPress editor. The idea combines concepts of
what in the past may have achieved with shortcodes, custom HTML, and embed discovery
into a single consistent API and user experience. Container Label Generation. It
also expands the Embeddings infrastructure, improves Content Translation and Markdown
Feeds, introduces additional AI providerProvider An AI service offering models for
generation, embeddings, or other capabilities (e.g., Anthropic, Google, OpenAI).
connectors, and brings several Abilities into alignment with WordPress coreCore 
Core is the set of software required to run WordPress. The Core Development Team
builds WordPress..

## What’s new in 1.5.0?

### New Experiment: Text to Speech

The new [Text to Speech experiment](https://github.com/WordPress/ai/pull/888) lets
editors generate an audio version of a post, giving visitors the option to listen
to content instead of reading it.

When enabled, editors can generate audio from a post’s title and content using a
configured AI provider that supports speech generation. Audio processing runs in
the background, allowing editors to continue working or return later while longer
posts are processed.

Once generated, the audio file is saved to the Media Library and can be played directly
in the editor. Editors can choose whether to display an audio player on the published
post and regenerate the audio when needed. This provides another way for publishers
to make their content accessible and available in different formats without requiring
a separate audio production workflow.

### New Experiment: Content Verification

The new [Content Verification experiment](https://github.com/WordPress/ai/pull/459)
introduces support for detecting C2PA Content Credentials in images uploaded to 
WordPress.

Content Credentials are a standard for attaching provenance information to digital
media, helping publishers and audiences understand where content originated and 
how it may have been modified. When enabled, the experiment detects embedded C2PA
data in uploaded JPEG, PNG, and WebP images and preserves the manifest information
alongside the attachment. Credential status is displayed in the Media Library, including
a new indicator in the grid view.

This initial implementation is read-only. It detects and preserves existing Content
Credentials but does not yet perform cryptographic verification or generate new 
credentials for images. The experiment establishes a foundation for future content
provenance features, including deeper verification and support for preserving credentials
through WordPress image-processing workflows.

### New Experiment: MCP Access

![Dashboard view of the MCP Access interface in a web application, displaying various
tools and their settings related to AI functionalities, with options for abilities
like site information retrieval, image generation, and content analysis.](https://
make.wordpress.org/ai/files/2026/11/mcp-access-839x1024.png)

The new [MCP Access experiment](https://github.com/WordPress/ai/pull/992) makes 
it easier to connect WordPress to external AI agents through the Model Context Protocol(
MCP).

MCP provides a standardized way for AI applications and agents to discover and interact
with tools and capabilities exposed by other systems. When enabled, the experiment
installs and activates the [MCP Adapter plugin](https://wordpress.org/plugins/mcp-adapter/)
when site permissions allow. It also adds a new **Tools → MCP Access** administration
screen where site owners can review registered WordPress Abilities and control which
ones are exposed to AI agents.

The interface displays the site’s MCP endpoint and provides controls for exposing
or hiding individual Abilities, along with the option to restore their default settings.
This separates the underlying MCP infrastructure from the controls site owners need
to manage agent access, making it easier to explore how external AI systems can 
interact with WordPress functionality.

### New Experiment: WebMCP

AI 1.5.0 also introduces a [WebMCP experiment](https://github.com/WordPress/ai/pull/1081),
allowing compatible AI-powered browsers to interact directly with the WordPress 
Block Editor.

While MCP Access exposes server-side WordPress Abilities to external agents, WebMCP
focuses on interactions within the browser itself. Using the experimental `document.
modelContext` interface, an AI agentAI Agent An AI system that autonomously performs
tasks and interacts with systems through available tools and resources. can interact
with the editor through a collection of tools that support actions such as:

 * Reading the current post and updating its title.
 * Inserting, editing, moving, and duplicating blocks.
 * Modifying block attributes and content.
 * Saving and publishing posts.

These actions use the editor’s existing data stores, so changes appear directly 
in the editing interface as they happen. This provides an early look at how AI agents
could work alongside editors within familiar WordPress interfaces rather than operating
exclusively through external APIs.

### New Experiment: Revision Change Summary

The new [Revision Change Summary experiment](https://github.com/WordPress/ai/pull/1159)
helps editors understand what changed between two revisionsRevisions The WordPress
revisions system stores a record of each saved draft or published update. The revision
system allows you to see what changes were made in each revision by dragging a slider(
or using the Next/Previous buttons). The display indicates what has changed in each
revision. of a post.

WordPress already provides detailed revision comparisons, but interpreting those
changes can become time-consuming for longer or more complex content. With this 
experiment enabled, editors can generate a plain-language summary of the differences
between revisions directly from the visual or classic revision comparison screens.

The summary highlights meaningful changes to post content and titles, helping editors,
reviewers, and content teams understand how a post has evolved without reviewing
every individual change. The experiment is read-only and does not modify either 
revision or the underlying post. Additional improvements also preserve more detailed
comparisons for multiline content such as tables and quotes.

### New Experiment: Block Container Label Generation

The new [Block Container Label Generation experiment](https://github.com/WordPress/ai/pull/1175)
helps editors navigate complex block layouts by generating meaningful labels for
container blocks.

As posts and pages grow in complexity, List View can become difficult to navigate
when multiple Group, Columns, and other container blocks appear with generic names.
This experiment uses AI to suggest concise, descriptive labels based on the content
and purpose of a container. Generated labels are available in List View and the 
block Rename modal, helping editors identify sections without changing their visible
content.

A [follow-up enhancement](https://github.com/WordPress/ai/pull/1218) also incorporates
document-level context, including the post title, surrounding sections, and existing
labels, to produce more useful suggestions.

For editors working with complex page layouts, reusable patterns, or long-form content,
these labels can make document navigation and organization considerably easier.

### Expanded embeddings infrastructure

AI 1.5.0 continues building on the Embeddings infrastructure introduced in previous
releases.

The plugin now includes a [background synchronization system](https://github.com/WordPress/ai/pull/1135)
for generating and maintaining embeddings for posts and taxonomyTaxonomy A taxonomy
is a way to group things together. In WordPress, some common taxonomies are category,
link, tag, or post format. [https://codex.wordpress.org/Taxonomies#Default_Taxonomies](https://codex.wordpress.org/Taxonomies#Default_Taxonomies).
terms.

Using WordPress Cron, the system can process existing content in batches, detect
when content changes, and update or remove stored embeddings as needed. It also 
supports resuming interrupted operations and avoids unnecessary requests when content
has not changed.

Embedding generation is not automatically activated for every site. Features that
need embeddings must register their requirements, allowing the infrastructure to
run only when needed.

Like the earlier embedding storage and vector ranking additions, this is primarily
developer infrastructure rather than a new end-user experiment. It provides additional
building blocks for future semantic search, content recommendations, retrieval, 
and other AI-powered workflows.

### Content Translation improvements

[Content Translation](https://github.com/WordPress/ai/pull/1009) now supports a 
broader range of WordPress blocks.

Previously, translation focused primarily on paragraphs and headings. AI 1.5.0 expands
that behavior to blocks containing rich-text content, allowing more of a post’s 
content to be translated within the existing workflow. The release also improves
translation behavior when working with the editor’s “Show template” mode and prevents
translations from being applied to blocks that have been edited, removed, or replaced
while a request was processing.

These changes make Content Translation more useful for complex posts and help protect
editors’ work when content changes during a translation request.

### Markdown Feeds improvements

The [Markdown Feeds experiment](https://github.com/WordPress/ai/pull/1121), introduced
in AI 1.4.0, receives several enhancements.

Individual posts requested with `?output_format=markdown` now include their approved
comments, providing AI agents and other Markdown consumers with additional context
from the discussion surrounding published content. The release also improves site-
wide comment feeds, fixes content negotiation so requests respect the preferred 
response format, and applies existing WordPress feed filters for greater compatibility
with other plugins.

One behavior has changed: individual post URLs using `/<post>/feed/markdown/` are
no longer supported. Consumers should request the post’s Markdown document using`?
output_format=markdown` instead.

### Improved AI settings and provider discovery

AI 1.5.0 makes it easier to understand how different AI capabilities operate before
enabling them.

The [AI settings interface](https://github.com/WordPress/ai/pull/1190) now more 
clearly distinguishes between stable Features and experimental functionality. Experiments
that run automatically are identified, and an information control provides details
about when each experiment runs, what information is sent to the configured AI provider,
and how many requests it makes.

These improvements are intended to give site owners better visibility into AI usage,
especially for experiments that can trigger requests automatically.

The release also [expands the available connectors](https://github.com/WordPress/ai/pull/1212)
featured on **Settings → Connectors**, adding Mistral and Vercel AI Gateway alongside
the existing Anthropic, Google, and OpenAI options. Featured connectors can be discovered,
installed, activated, and configured from the same interface.

Additional links to the [AI-Powered WordPress course](https://learn.wordpress.org/course/ai-powered-wordpress/)
make it easier for new users to find educational resources.

### Updated Abilities Explorer

The [Abilities Explorer](https://github.com/WordPress/ai/pull/1181) has been rebuilt
using WordPress DataViews, bringing its interface more closely into alignment with
modern WordPress administration experiences. The updated Explorer makes it easier
for developers and administrators to discover, inspect, and execute registered WordPress
Abilities.

Three new REST APIREST API The REST API is an acronym for the RESTful Application
Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data.
It is how the front end of an application (think “phone app” or “website”) can communicate
with the data store (think “database” or “file system”) [https://developer.wordpress.org/rest-api/](https://developer.wordpress.org/rest-api/)
endpoints support retrieving and running Abilities, replacing parts of the previous
implementation that relied on older administration patterns. Developers can also
extend the Explorer with additional read-only columns using the new `ai.abilitiesExplorer.
fields` JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming
language commonly used to create interactive effects within web browsers. WordPress
makes extensive use of JS for a better user experience. While PHP is executed on
the server, JS executes within a user’s browser. [https://www.javascript.com](https://www.javascript.com/)
filterFilter Filters are one of the two types of Hooks [https://codex.wordpress.org/Plugin_API/Hooks](https://codex.wordpress.org/Plugin_API/Hooks).
They provide a way for functions to modify data of other functions. They are the
counterpart to Actions. Unlike Actions, filters are meant to work in an isolated
manner, and should never have side effects such as affecting global variables and
output..

### Updated core Abilities and breaking changes

AI 1.5.0 includes important updates to three general-purpose WordPress Abilities:

 * `[core/content-query](https://github.com/WordPress/ai/pull/1208)`
 * `[core/users-query](https://github.com/WordPress/ai/pull/1207)`
 * `[core/settings-get](https://github.com/WordPress/ai/pull/1206)`

These Abilities have been synchronized with their corresponding implementations 
coming in WordPress core with 7.2 this December, helping developers work with consistent
interfaces as the Abilities APIAbilities API A core WordPress API (introduced in
6.9) that creates a central registry of capabilities, making WordPress functions
discoverable and accessible to AI agents, automation tools, and developers. Transforms
WordPress from isolated functions into a unified system. evolves. The updates introduce
changes to request and response structures, including new `where`, `fields`, and`
pagination` inputs for content and user queries, consistent result structures, and
updated field names.

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

 * `core/read-content` → use `core/content-query`
 * `core/read-users` → use `core/users-query`
 * `core/read-settings` → use `core/settings-get`

Developers using these Abilities should review the updated schemas and adjust existing
calls accordingly. Additional changes to date fields and user lookup behavior may
also require updates.

### Additional fixes and improvements

The release includes several fixes and smaller enhancements across existing experiments
and administration interfaces:

 * **Title Generation:** A new Generate title button is available in the post Rename
   modal.
 * **AI Request Logging:** Successful requests from providers using custom transports
   are now recorded, and administrators can delete logs by age rather than only 
   purging everything.
 * **Suggest Reply:** Reply suggestions are applied to the correct comment, and 
   protected post titles and excerpts are no longer sent to AI providers.
 * **Comment Moderation:** Automatic analysis no longer processes pingbacks, trackbacks,
   or block editor Notes by default.
 * **Content Classification:** Improved handling of taxonomy terms containing special
   characters or non-ASCII text.
 * **Key Encryption:** Integration with the emerging WordPress Secrets APIAPI An
   API or Application Programming Interface is a software intermediary that allows
   programs to interact with each other and share data in limited, clearly defined
   ways. includes backward compatibility and migrationMigration Moving the code,
   database and media files for a website site from one server to another. Most 
   typically done when changing hosting companies. for existing encrypted keys.
 * **Performance:** Feature and experiment settings are loaded more efficiently,
   reducing repeated database queries on sites without persistent object caching.
 * **AI Status:** The dashboard widgetWidget A WordPress Widget is a small block
   that performs a specific function. You can add these widgets in sidebars also
   known as widget-ready areas on your web page. WordPress widgets were originally
   created to provide a simple and easy-to-use way of giving design and structure
   control of the WordPress theme to the user. now summarizes enabled and disabled
   experiments in a more compact format.

### Security improvements

AI 1.5.0 includes fixes for two reported security advisories, [GHSA-7mwf-4ppp-cxmp](https://github.com/WordPress/ai/security/advisories/GHSA-7mwf-4ppp-cxmp)
and [GHSA-g94j-h78j-rr2j](https://github.com/WordPress/ai/security/advisories/GHSA-g94j-h78j-rr2j).

The release also improves how private and password-protected post information is
handled in AI-powered comment workflows and includes additional protections around
stored connector credentials.

**Sites using the AI plugin are encouraged to update promptly.**

## What’s next?

Work is already underway on additional Features, Experiments, Developer Tools, and
Abilities planned for [1.6.0](https://github.com/WordPress/ai/milestone/25) and 
future releases, including:

 * New Experiment: [AI Workspace](https://github.com/WordPress/ai/pull/1004) and
   [Site Agent](https://github.com/WordPress/ai/pull/1214)
 * New Experiment: [Agent Users](https://github.com/WordPress/ai/pull/1068)
 * New Experiment: [Natural-language admin navigation via Command Palette](https://github.com/WordPress/ai/issues/1203)
 * New Experiment: [Embeddings Support](https://github.com/WordPress/ai/issues/962)
 * New Experiment: [Internal Link Suggestions](https://github.com/WordPress/ai/pull/887)
 * New Experiment: [Topic Pages](https://github.com/WordPress/ai/issues/1136)
 * New Experiment: [Integrate with Gutenberg’s experimental Media Editor](https://github.com/WordPress/ai/issues/325)
   including [focus-aware crop suggestions](https://github.com/WordPress/ai/issues/238)
 * Updated Experiment: [Integrate Refine from Notes with Real-time Collaboration](https://github.com/WordPress/ai/issues/324)
 * New Developer Tool: [Role and User access controls](https://github.com/WordPress/ai/pull/749)
 * New Abilities: [`core/term-create`, `core/term-update`, and `core/term-delete`](https://github.com/WordPress/ai/pull/1103)
 * New Abilities: [`core/media-upload`, `core/media-update`, and `core/media-delete`](https://github.com/WordPress/ai/pull/1104)
   plus [`core/media-query`](https://github.com/WordPress/ai/pull/1098)
 * New Abilities: [`core/user-create`, `core/user-update`, and `core/user-delete`](https://github.com/WordPress/ai/pull/1105)
 * New Abilities: [`core/content-create`, `core/content-update`, and `core/content-delete`](https://github.com/WordPress/ai/pull/1025)
 * New Abilities: [`core/post-types-query`](https://github.com/WordPress/ai/pull/1106),
   [`core/settings-update`](https://github.com/WordPress/ai/pull/764), and [`core/terms-query`](https://github.com/WordPress/ai/pull/1099)

These concepts are still exploratory, but they help test how AI could support real
workflows across WordPress.

## Thanks to contributors!

A big thank you to everyone who contributed to this release, including:

[@dkotter](https://profiles.wordpress.org/dkotter/), [@jeffpaul](https://profiles.wordpress.org/jeffpaul/),
[@dan2k3k4](https://profiles.wordpress.org/dan2k3k4/), [@jason_the_adams](https://profiles.wordpress.org/jason_the_adams/),
[@justlevine](https://profiles.wordpress.org/justlevine/), [@philsola](https://profiles.wordpress.org/philsola/),
[@milindmore22](https://profiles.wordpress.org/milindmore22/), [@laurisaarni](https://profiles.wordpress.org/laurisaarni/),
[@fernandot](https://profiles.wordpress.org/fernandot/), [@mdraabiul](https://profiles.wordpress.org/mdraabiul/),
[@whyisjake](https://profiles.wordpress.org/whyisjake/), [@raftaar1191](https://profiles.wordpress.org/raftaar1191/),
[@iamchitti](https://profiles.wordpress.org/iamchitti/), [@originvault](https://profiles.wordpress.org/originvault/),
[@shubhambhar007](https://profiles.wordpress.org/shubhambhar007/), [@mahbubwpwist](https://profiles.wordpress.org/mahbubwpwist/),
[@ankitkumarshah](https://profiles.wordpress.org/ankitkumarshah/), [@colinmcdonough](https://profiles.wordpress.org/colinmcdonough/),
[@ekamran](https://profiles.wordpress.org/ekamran/), [@yogeshbhutkar](https://profiles.wordpress.org/yogeshbhutkar/),
[@urbankidro](https://profiles.wordpress.org/urbankidro/), [@swissspidy](https://profiles.wordpress.org/swissspidy/),
[@fellyph](https://profiles.wordpress.org/fellyph/), [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/),
[@gziolo](https://profiles.wordpress.org/gziolo/), [@euthelup](https://profiles.wordpress.org/euthelup/),
[@ugyensupport](https://profiles.wordpress.org/ugyensupport/), [@ovidiu-galatan](https://profiles.wordpress.org/ovidiu-galatan/),
[@drzraf](https://profiles.wordpress.org/drzraf/), [@zodiac1978](https://profiles.wordpress.org/zodiac1978/),
[@dhrupo](https://profiles.wordpress.org/dhrupo/), [@pranjal4804](https://profiles.wordpress.org/pranjal4804/),
[@malaytiwari](https://profiles.wordpress.org/malaytiwari/), [@anubhav24](https://profiles.wordpress.org/anubhav24/),
[@gajendrasingh](https://profiles.wordpress.org/gajendrasingh/), [@maheshbohara](https://profiles.wordpress.org/maheshbohara/),
[@sohampate1](https://profiles.wordpress.org/sohampate1/), [@riccardodicurti](https://profiles.wordpress.org/riccardodicurti/),
[@htperkins](https://profiles.wordpress.org/htperkins/), [@abcd95](https://profiles.wordpress.org/abcd95/),
[@sainathpoojary](https://profiles.wordpress.org/sainathpoojary/), [@hbhalodia](https://profiles.wordpress.org/hbhalodia/),
[@noruzzaman](https://profiles.wordpress.org/noruzzaman/), and others involved in
review, testing, translating, and [81 commits across 395 files between 1.4.0 and 1.5.0](https://github.com/WordPress/ai/compare/1.4.0...1.5.0).
Your help and feedback are what make these Features and Experiments possible.

A similar thank you to translators assisting from the [Chinese (Taiwan), Czech, Danish, German, German (Formal), Hindi, Japanese, Persian, Polish, and Turkish locales](https://translate.wordpress.org/projects/wp-plugins/ai/)
ensuring language packs are available for users. [Translating the AI plugin](https://translate.wordpress.org/projects/wp-plugins/ai/)
is a **_great_** **_contribution_** and others contributing in this manner is very
much welcome and appreciated!

## Get involved

As always, we welcome feedback, testing, and contributions from the community. Whether
you are interested in editor UXUX UX is an acronym for User Experience - the way
the user uses the UI. Think ‘what they are doing’ and less about how they do it.,
APIs, accessibilityAccessibility Accessibility (commonly shortened to a11y) refers
to the design of products, devices, services, or environments for people with disabilities.
The concept of accessible design ensures both “direct access” (i.e. unassisted) 
and “indirect access” meaning compatibility with a person’s assistive technology(
for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility),
performance, or AI ethics and policy, there are many ways to participate.

You can [explore the 1.5.0 release today](https://wordpress.org/plugins/ai/?preview=1),
review [open issues](https://github.com/WordPress/ai/issues) and [pull requests](https://github.com/WordPress/ai/pulls),
and [help shape what comes next](https://github.com/WordPress/ai/discussions).

_Props to [@ekamran](https://profiles.wordpress.org/ekamran/) [@laurisaarni](https://profiles.wordpress.org/laurisaarni/)@
for reviewing this post._

[#ai-experiments](https://make.wordpress.org/ai/tag/ai-experiments/), [#ai-features](https://make.wordpress.org/ai/tag/ai-features/),
[#ai-plugin](https://make.wordpress.org/ai/tag/ai-plugin/), [#ai-release](https://make.wordpress.org/ai/tag/ai-release/),
[#canonical-plugins](https://make.wordpress.org/ai/tag/canonical-plugins/), [#core-ai](https://make.wordpress.org/ai/tag/core-ai/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fai%2F2026%2F11%2F02%2Fwhats-new-in-ai-1-5-0%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/jeffpaul/) [Jeffrey Paul](https://profiles.wordpress.org/jeffpaul/)
3:07 pm _on_ 2 November 2026     
Tags: [core-ai ( 88 )](https://make.wordpress.org/ai/tag/core-ai/),
[summary ( 47 )](https://make.wordpress.org/ai/tag/summary/)   

# 󠀁[AI Contributor Weekly Summary – 28 October 2026](https://make.wordpress.org/ai/2026/11/02/ai-contributor-weekly-summary-28-october-2026/)󠁿

_This week’s meeting focused on the newly published strategy for making WordPress
ready for the agentic web, including coordinated work on the MCP AdapterMCP Adapter
Translates WordPress abilities into Model Context Protocol format, allowing AI assistants
like Claude and ChatGPT to discover and invoke WordPress capabilities as tools, 
resources, and prompts., coreCore Core is the set of software required to run WordPress.
The Core Development Team builds WordPress. abilities, OAuth authentication, and
user experience. Contributors also discussed a proposed shared abilities package,
upcoming AI pluginPlugin A plugin is a piece of software containing a group of functions
that can be added to a WordPress website. They can extend functionality or add new
features to your WordPress websites. WordPress plugins are written in the PHP programming
language and integrate seamlessly with WordPress. These can be free in the WordPress.
org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
or can be cost-based plugin from a third-party. and PHPPHP PHP (recursive acronym
for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting
language that is especially suited for web development and can be embedded into 
HTML. [https://www.php.net/manual/en/index.php](https://www.php.net/manual/en/index.php)
AI Client releases, and the roadmap for delivering a stable MCP experience alongside
WordPress 7.2 and preparing for WordPress 7.3._

## WordPress for the Agentic Web: Strategy and User Experience

[@jeffpaul](https://profiles.wordpress.org/jeffpaul/) highlighted the newly published
[WordPress for the Agentic Web](https://make.wordpress.org/ai/2026/10/28/wordpress-for-the-agentic-web/)
proposal, outlining the team’s priorities across the remaining WordPress 7.2 cycle
and into 7.3. The strategy identifies three technical workstreams, MCP Adapter, 
Abilities, and OAuth authentication, supported by a coordinated user experience (
UXUX UX is an acronym for User Experience - the way the user uses the UI. Think ‘
what they are doing’ and less about how they do it.) effort to ensure they work 
together seamlessly.

[@karmatosed](https://profiles.wordpress.org/karmatosed/) volunteered to help lead
the UX effort, emphasizing asynchronous collaboration and the need to map the complete
user journey across these capabilities. [@jeffpaul](https://profiles.wordpress.org/jeffpaul/)
suggested beginning with the experience described in the proposal and identifying
how the individual workstreams contribute to each step.

[@apeatling](https://profiles.wordpress.org/apeatling/) also highlighted that user
experience will vary significantly depending on which AI client or agent someone
uses, requiring ongoing testing and refinement rather than a single implementation.

Contributors are encouraged to review the proposal and volunteer to help lead or
contribute to the workstreams.

## Shared WordPress Abilities Package

[@nikskyverge](https://profiles.wordpress.org/nikskyverge/) shared a prototype for
a [centralized WordPress Abilities package](https://github.com/nikmclaughlin/wordpress-abilities),
designed to simplify how abilities are developed, distributed, and eventually incorporated
into WordPress core.

Currently, abilities may need to be maintained separately across the AI plugin, 
MCP Adapter, and other integrations. The proposed package would provide a shared
implementation that these projects could consume without duplicating development
work. The approach could also benefit third-party developers who want to use specific
abilities without depending on an entire plugin. [@nikskyverge](https://profiles.wordpress.org/nikskyverge/)
is additionally exploring tooling to streamline the process of promoting abilities
into WordPress core.

The prototype remains experimental, with outstanding considerations around autoloading,
version management, and compatibility. The immediate priority remains getting useful
abilities into the AI plugin and MCP Adapter, with the shared package potentially
simplifying that work going forward.

## AI Plugin 1.5.0 and AbilityAbility A registered, self-documenting unit of WordPress functionality that can be discovered and invoked through multiple contexts (REST API, Command Palette, MCP). Includes authorization and input/output specifications. Compatibility

[@jeffpaul](https://profiles.wordpress.org/jeffpaul/) and [@dkotter](https://profiles.wordpress.org/dkotter/)
shared that AI plugin version 1.5.0 was targeted for release on October 29. The 
release includes continued work on custom abilities, incorporating changes aligned
with implementations being developed for WordPress core.

[@justlevine](https://profiles.wordpress.org/justlevine/) raised concerns about 
potential breaking changes to ability schemas between versions 1.4.0 and 1.5.0, 
including renamed abilities and changes to existing interfaces. The team clarified
that most content abilities are new to 1.5.0, limiting compatibility concerns for
existing installations. However, settings abilities and other previously available
functionality may require additional review.

Because these abilities remain part of an experimental feature, compatibility guarantees
differ from those of stable functionality. Nevertheless, contributors agreed that
any identified breaking changes should be clearly documented in the release changelog.

[@justlevine](https://profiles.wordpress.org/justlevine/) will review the changes,
while [@dkotter](https://profiles.wordpress.org/dkotter/) will ensure relevant compatibility
information is included in the release notes.

Contributors with outstanding pull requests targeted for 1.5.0 were encouraged to
address remaining review and testing feedback promptly.

## PHP AI Client 1.5.1

The team also discussed an upcoming maintenance release of the PHP AI Client, version
1.5.1, targeted for October 28 or 29. This release includes fixes following the 
PHP AI Client 1.5.0 integration into WordPress 7.2 BetaBeta A pre-release of software
that is given out to a large group of users to trial under real conditions. Beta
versions have gone through alpha testing in-house and are generally fairly close
in look, feel and function to the final product; however, design changes often occur
as part of the process. 1.

The goal is to incorporate the updates into WordPress 7.2 Beta 3, or Beta 4 at the
latest, ensuring the fixes receive additional testing before the final WordPress
release.

## MCP Adapter Roadmap and WordPress 7.3

[@justlevine](https://profiles.wordpress.org/justlevine/) provided an MCP Adapter
update, noting that work continues on open pull requests and potential improvements
to the adapter’s internal implementation.

Contributors were encouraged to review [MCP Adapter issue #402](https://github.com/WordPress/mcp-adapter/issues/402),
which collects user stories, technical improvements, testing requirements, and related
work needed to deliver a more complete MCP experience.

[@jeffpaul](https://profiles.wordpress.org/jeffpaul/) proposed targeting a stable
MCP Adapter 1.0 release around December 8, alongside WordPress 7.2. This would provide
an opportunity to gather real-world feedback and iterate ahead of the WordPress 
7.3 development cycle. The proposed timeline would require any planned core integration
for WordPress 7.3 to be ready for review ahead of Beta 1, tentatively expected in
the first quarter of 2027. The scope and timing of MCP Adapter 1.0 remain open for
further discussion.

[@apeatling](https://profiles.wordpress.org/apeatling/) emphasized that delivering
useful abilities should be the highest priority, since connecting an agent to WordPress
provides limited value unless it can perform meaningful site operations.

The team also discussed whether additional abilities should be considered for WordPress
7.2 after Beta 1. While there may be opportunities to include sufficiently mature
functionality, contributors cautioned against introducing unnecessary release pressure
when experimental plugins can already make those abilities available for testing.

[@nikskyverge](https://profiles.wordpress.org/nikskyverge/) will coordinate with
[@ovidiu-galatan](https://profiles.wordpress.org/ovidiu-galatan/) to determine whether
the MCP Adapter should consume abilities through the proposed shared package or 
integrate them directly in the short term.

---

## Next Steps

 * **Agentic Web UX:** [@karmatosed](https://profiles.wordpress.org/karmatosed/)
   will begin mapping the end-to-end user journey and coordinating UX considerations
   across the MCP Adapter, Abilities, and OAuth workstreams.
 * **Shared abilities package:** [@nikskyverge](https://profiles.wordpress.org/nikskyverge/)
   will continue refining the prototype and coordinate with [@ovidiu-galatan](https://profiles.wordpress.org/ovidiu-galatan/)
   on MCP Adapter integration.
 * **AI plugin 1.5.0:** Contributors will address outstanding pull request feedback
   ahead of the targeted release.
 * **Ability compatibility:** [@justlevine](https://profiles.wordpress.org/justlevine/)
   will investigate potential breaking schema changes, with [@dkotter](https://profiles.wordpress.org/dkotter/)
   ensuring they are documented in the changelog.
 * **PHP AI Client 1.5.1:** Finalize the maintenance release and prepare its fixes
   for inclusion in WordPress 7.2 Beta 3 or Beta 4.
 * **MCP Adapter roadmap:** Continue reviewing [issue #402](https://github.com/WordPress/mcp-adapter/issues/402),
   prioritize foundational abilities, and refine the proposed scope for a stable
   1.0 release.
 * **Meeting documentation:** [@justlevine](https://profiles.wordpress.org/justlevine/)
   will share the draft meeting handbook, and [@nikskyverge](https://profiles.wordpress.org/nikskyverge/)
   will review it and provide feedback.

## Upcoming Meetings

 * Contributors are welcome to join the weekly AI contributor call. All team meeting
   schedules are published on the [WordPress Meeting Calendar](https://make.wordpress.org/meetings/#ai).
 * **AI Team Office Hours:** Thursday, October 29, 2026 at 17:00 UTC.

_Props to [@gziolo](https://profiles.wordpress.org/gziolo/) for pre-publish review._

[#core-ai](https://make.wordpress.org/ai/tag/core-ai/), [#summary](https://make.wordpress.org/ai/tag/summary/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fai%2F2026%2F11%2F02%2Fai-contributor-weekly-summary-28-october-2026%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/jason_the_adams/) [Jason Adams](https://profiles.wordpress.org/jason_the_adams/)
3:46 pm _on_ 28 October 2026     
Tags: Abilities, [core-ai ( 88 )](https://make.wordpress.org/ai/tag/core-ai/),
MCP Adapter, OAuth   

# 󠀁[WordPress for the Agentic Web](https://make.wordpress.org/ai/2026/10/28/wordpress-for-the-agentic-web/)󠁿

Recently, Google announced that its total users of AI exceeded 1 billion while OpenAI
reports around 1.2 billion. Anthropic hasn’t shared a number, but others also share
numbers in hundreds of millions. Even accounting for people using accounts across
multiple platforms, AI adoption is staggering and shows no signs of slowing down.

This shift toward the Agentic Web is fundamentally changing how people experience
the internet. People are increasingly using agents to search the web, find products,
build apps, and run their businesses. There are interesting benefits, such as [Adobe sharing](https://www.digitalcommerce360.com/2026/08/19/adobe-ai-referral-traffic-data-july-2026/)
that AI traffic converts 60% better than non-AI traffic, and brings in 53% more 
revenue. This means that once a user arrives they’re more confident in why they’re
there and what they want to do. As these capabilities expand, users will expect 
their agents to work with the sites and platforms they already use.

## Making WordPress Agent-Ready

Within the WordPress ecosystem, products such as Jetpack, Elementor, and WPVibe 
have demonstrated demand for users to manage their WordPress sites agentically. 
Commercialism aside, it’s amazing to think of users being able to build the most
incredible versions of their WordPress worlds because their agents raise the bar
in what they can achieve. It’s not just another surface by which to control WordPress,
it opens another level of possibilities for those users. That’s exciting!

The goal remains: Democratize Publishing. To fulfill that mission in the Agentic
Web, WordPress needs to make it possible for everyone to manage their sites with
the agents they choose. This isn’t about putting an agent inside WordPress; it’s
about making WordPress ready to work with the agents users bring. WordPress is [the best solution](https://x.com/photomatt/status/2112511282523861149?s=20)
for the open web, we need to make it the same in the agentic web.

**The vision is simple:** A user opens their personal agent and says, “I want you
to help me with my example.com site.” The agent recognizes WordPress, provides a
link to authorize access, and the user signs in. The agent responds, “I’m in! How
can I help you with your site?”

Making that experience possible for every WordPress user requires native capabilities
that are simple to discover, connect to, and use.

## Making Agent Connectivity Native

Agents can already accomplish a lot with WordPress through WP-CLIWP-CLI WP-CLI is
the Command Line Interface for WordPress, used to do administrative and development
tasks in a programmatic way. The project page is [http://wp-cli.org/](http://wp-cli.org/)
[https://make.wordpress.org/cli/](https://make.wordpress.org/cli/), the REST APIREST
API The REST API is an acronym for the RESTful Application Program Interface (API)
that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end
of an application (think “phone app” or “website”) can communicate with the data
store (think “database” or “file system”) [https://developer.wordpress.org/rest-api/](https://developer.wordpress.org/rest-api/),
and file management. However, these approaches often require local access or more
advanced configurations.  For users bringing their own agents, connecting to WordPress
needs to be much simpler.

MCP has emerged as the open standard for connecting agents to external systems. 
The existing [MCP Adapter plugin](https://wordpress.org/plugins/mcp-adapter/) provides
an important foundation, but users still need to install and configure it, ensure
useful Abilities are available (perhaps via the [AI plugin](https://wordpress.org/plugins/ai/)),
and manually manage authentication through Application Passwords (hopefully not 
pasting them in plaintext to their agent). This is not a scalable approach for the
broad WordPress user base.

To deliver the experience described above, this proposal includes four coordinated
areas of work, targeting WordPress 7.3 while using the 7.2 release cycle to establish
the necessary foundations.

## MCP AdapterMCP Adapter Translates WordPress abilities into Model Context Protocol format, allowing AI assistants like Claude and ChatGPT to discover and invoke WordPress capabilities as tools, resources, and prompts.

We’ll rapidly iterate on the MCP Adapter pluginPlugin A plugin is a piece of software
containing a group of functions that can be added to a WordPress website. They can
extend functionality or add new features to your WordPress websites. WordPress plugins
are written in the PHP programming language and integrate seamlessly with WordPress.
These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
or can be cost-based plugin from a third-party., focusing on reliability, security,
and usability to have a solid foundation alongside WordPress 7.2.  From there the
goal is to propose bringing MCP functionality into coreCore Core is the set of software
required to run WordPress. The Core Development Team builds WordPress. for WordPress
7.3 either through a direct merge or a bundled approach that allows the adapter 
to evolve independently.

## Abilities

Connecting an agent is only useful if it can accomplish meaningful tasks.  We’ll
identify a baseline of Abilities needed for common site management workflows, continuing
rapid development through the AI and/or MCP Adapter plugins.

We’ll also explore whether a few additional foundational Abilities can land in WordPress
7.2 before the end of the betaBeta A pre-release of software that is given out to
a large group of users to trial under real conditions. Beta versions have gone through
alpha testing in-house and are generally fairly close in look, feel and function
to the final product; however, design changes often occur as part of the process.
cycles, with the broader goal of bringing a useful set of native Abilities into 
core for 7.3.

## OAuth Authentication

Users should be able to securely authorize their agents without having to manually
generate and share Application Passwords.  During the 7.2 cycle, we’ll map out the
necessary OAuth flows, architecture, and security considerations, targeting implementation
in core for WordPress 7.3.

This functionality would benefit more than just MCP (e.g. the REST API) and should
be developed in coordination with the broader Core team.  The upcoming Secrets APIAPI
An API or Application Programming Interface is a software intermediary that allows
programs to interact with each other and share data in limited, clearly defined 
ways. in WordPress 7.2 also provides an opportunity to support secure token handling.

## End-to-End User Experience

The three technical capabilities above need to come together as one simple, intuitive
experience.  We’ll need to map the complete user journey, from an agent discovering
a WordPress site and requesting access to performing tasks and managing or revoking
permissions.

During the 7.2 cycle, we’ll need to develop and test prototypes to identify friction
and inform all three technical workstreams.  For 7.3., the goal is a cohesive experience
that allows users to connect their preferred agents to WordPress without complex
setup or technical knowledge.

## Working Toward WordPress 7.3

These are ambitious goals and delivering them will require clear ownership and close
collaboration across the project.  We’re looking for a dedicated focus lead for 
each of these four areas, supported by contributors who want to help.  Each lead
will establish milestones for WordPress 7.2 and 7.3, coordinate development and 
testing, and share progress, blockers, and calls for help during our weekly AI contributor
meetings.

We also want to pair each focus lead with interested Core Committers, involving 
them throughout development rather than waiting until features are ready for merge.
This will help address architectural, compatibility, and security considerations
early.

Security will be especially important as we introduce new ways for external agents
to interact with WordPress.  Appropriate review and audits, including specialized
security-focused AI models, will help ensure these capabilities are safe to use.

While WordPress 7.3 is our shared target, inclusion in core will depend on technical
readiness, security, and the normal core review processes.

## Get involved

We’re looking for contributors willing to lead or help with MCP, Abilities, OAuth,
and UXUX UX is an acronym for User Experience - the way the user uses the UI. Think‘
what they are doing’ and less about how they do it., as well as Core Committers 
interested in partnering with these efforts.

Join us in the [#core-ai](https://make.wordpress.org/ai/tag/core-ai/) channel in
SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/).
The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)
or at our weekly AI contributor meeting to help shape the work, volunteer for a 
focus area, or contribute to the discussion.

Together we can make WordPress ready for the Agentic Web, empowering everyone to
build and manage their sites through the agents they choose.

_Props [@apeatling](https://profiles.wordpress.org/apeatling/), [@bacoords](https://profiles.wordpress.org/bacoords/),
[@mynameistaken](https://profiles.wordpress.org/mynameistaken/), [@jeffpaul](https://profiles.wordpress.org/jeffpaul/),_
[@nikskyverge](https://profiles.wordpress.org/nikskyverge/)_ for pre-publish review._

[#abilities](https://make.wordpress.org/ai/tag/abilities/), [#mcp-adapter](https://make.wordpress.org/ai/tag/mcp-adapter/),
[#oauth](https://make.wordpress.org/ai/tag/oauth/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fai%2F2026%2F10%2F28%2Fwordpress-for-the-agentic-web%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/jeffpaul/) [Jeffrey Paul](https://profiles.wordpress.org/jeffpaul/)
6:46 pm _on_ 22 October 2026     
Tags: [core-ai ( 88 )](https://make.wordpress.org/ai/tag/core-ai/),
[summary ( 47 )](https://make.wordpress.org/ai/tag/summary/)   

# 󠀁[AI Contributor Weekly Summary – 21 October 2026](https://make.wordpress.org/ai/2026/10/22/ai-contributor-weekly-summary-21-october-2026/)󠁿

_This week’s meeting focused on a significant step toward making Model Context Protocol(
MCP) a native part of the WordPress experience, following approval to move forward
with the initiative. Contributors discussed how MCP should be delivered, early agent
benchmarking results, authentication and security requirements, and the balance 
between seamless user experiences and modular development. The team also identified
maintenance bottlenecks affecting the PHPPHP PHP (recursive acronym for PHP: Hypertext
Preprocessor) is a widely-used open source general-purpose scripting language that
is especially suited for web development and can be embedded into HTML. [https://www.php.net/manual/en/index.php](https://www.php.net/manual/en/index.php)
AI Client and related components._

## MCP as Part of the WordPress Experience

[@jason_the_adams](https://profiles.wordpress.org/jason_the_adams/) shared that 
Matt has approved moving forward with making MCP a de facto part of the WordPress
experience, recognizing the growing adoption of AI agents and the importance of 
making WordPress accessible through agent-driven workflows.

The discussion clarified that this does not necessarily mean moving the entire MCP
AdapterMCP Adapter Translates WordPress abilities into Model Context Protocol format,
allowing AI assistants like Claude and ChatGPT to discover and invoke WordPress 
capabilities as tools, resources, and prompts. into WordPress coreCore Core is the
set of software required to run WordPress. The Core Development Team builds WordPress..
Options include bundling the pluginPlugin A plugin is a piece of software containing
a group of functions that can be added to a WordPress website. They can extend functionality
or add new features to your WordPress websites. WordPress plugins are written in
the PHP programming language and integrate seamlessly with WordPress. These can 
be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
or can be cost-based plugin from a third-party. with WordPress, enabling it through
existing core interfaces, or incorporating specific capabilities directly into core.

[@bacoords](https://profiles.wordpress.org/bacoords/) highlighted existing WordPress
patterns, such as importers and connectors, where plugins can be installed behind
the scenes without introducing complexity for users. [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/)
emphasized defining the desired user experience first, then selecting the appropriate
implementation.

[@ovidiu-galatan](https://profiles.wordpress.org/ovidiu-galatan/) advocated for 
preserving the MCP Adapter as a modular plugin, allowing it to evolve independently
of WordPress core release cycles as the protocol continues to change.

The team found common ground around making MCP part of the default WordPress experience,
while leaving the technical implementation open for further discussion.

## Agent Benchmarks and MCP Capabilities

[@apeatling](https://profiles.wordpress.org/apeatling/) shared findings from ongoing
[WordPress Agent Benchmarks](https://wpab.view.fast/build/), examining how successfully
AI agents can work with WordPress.

Early testing found that agents completed 0% of the benchmarked tasks using the 
MCP Adapter alone, primarily because the adapter does not currently bundle the abilities
needed to perform common WordPress operations. Agents using alternative methods,
including REST APIREST API The REST API is an acronym for the RESTful Application
Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data.
It is how the front end of an application (think “phone app” or “website”) can communicate
with the data store (think “database” or “file system”) [https://developer.wordpress.org/rest-api/](https://developer.wordpress.org/rest-api/)
access, achieved higher success rates, although some approaches introduced security
concerns.

The discussion distinguished between two related challenges:

 * **Agent capability:** Whether an agent can successfully complete tasks using 
   WordPress tools. Adding standardized core abilities to the MCP experience can
   directly improve these results.
 * **Agent selection:** Whether an agent recommends or chooses WordPress in the 
   first place. This depends on broader discoverability, product positioning, and
   model behavior, making it a longer-term challenge.

Contributors emphasized that the benchmarks demonstrate the importance of delivering
a complete MCP experience rather than simply providing a connection mechanism.

## Default Enablement and Agent-First User Experience

[@apeatling](https://profiles.wordpress.org/apeatling/) raised concerns about requiring
users to visit WP Admin and manually install or enable the MCP Adapter before connecting
an AI agentAI Agent An AI system that autonomously performs tasks and interacts 
with systems through available tools and resources..

For users interacting with existing WordPress websites through tools such as Claude
or other personal agents, this additional setup could become a significant barrier.

The team explored whether MCP should be bundled and available by default, allowing
agents to initiate authentication without requiring users to first configure the
integration manually.

[@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/) noted that
bundling could also avoid filesystem restrictions that prevent plugin installation
on some hosting environments. WordPress 7.3 was discussed as a possible target for
deeper integration, though no release commitment was made.

The discussion also touched on creating a complete agent-driven experience for users
starting without an existing WordPress website. [@jason_the_adams](https://profiles.wordpress.org/jason_the_adams/)
noted that a broader proposal addressing hosting environments and agent-first site
creation is being developed with [@apeatling](https://profiles.wordpress.org/apeatling/).

## OAuth Authentication and Security

The team discussed the need for OAuth authentication to make MCP connections more
accessible and secure for everyday WordPress users.

[@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/) suggested 
that OAuth should be part of the default MCP experience, reducing reliance on application
passwords and providing a familiar authorization flow.

[@ovidiu-galatan](https://profiles.wordpress.org/ovidiu-galatan/) raised concerns
about introducing additional security-sensitive functionality into WordPress websites
without sufficient review and auditing.

[@justlevine](https://profiles.wordpress.org/justlevine/) emphasized that authentication
is a broader WordPress architectural concern rather than something exclusive to 
MCP. Contributors discussed whether OAuth infrastructure should be implemented centrally
in WordPress core, potentially leveraging the new Secrets APIAPI An API or Application
Programming Interface is a software intermediary that allows programs to interact
with each other and share data in limited, clearly defined ways. to secure tokens.

The team also highlighted the importance of separate credentials for individual 
clients and integrations to limit the impact of compromised access.

No final implementation decision was reached, with additional exploration needed
around the appropriate architecture and security requirements.

## PHP AI Client Maintenance and Streaming Support

[@laurisaarni](https://profiles.wordpress.org/laurisaarni/) raised concerns about
the pace of development for the PHP AI Client and whether core development processes
can keep up with rapidly evolving AI providerProvider An AI service offering models
for generation, embeddings, or other capabilities (e.g., Anthropic, Google, OpenAI).
APIs.

[@jason_the_adams](https://profiles.wordpress.org/jason_the_adams/) acknowledged
that limited maintainer availability has become a bottleneck and proposed formally
recruiting additional contributors willing to take ongoing responsibility for maintaining
the library.

The discussion also identified a dependency affecting streaming support. Work in
the PHP AI Client is currently blocked by an outstanding pull request in the WordPress
Requests library, which itself has limited maintainer availability.

[@whyisjake](https://profiles.wordpress.org/whyisjake/) volunteered to help move
the request forward, with coordination needed from an appropriate core committer
to review and merge the changes.

The discussion reinforced the importance of sustainable maintenance across the AI
building blocks and their underlying dependencies.

---

## Next Steps

 * **MCP integration proposal:** [@jason_the_adams](https://profiles.wordpress.org/jason_the_adams/)
   will draft a post outlining the proposed direction for MCP in WordPress, including
   potential implementations and outstanding questions.
 * **Agent benchmarking:** Continue evaluating agent task completion, MCP capabilities,
   and WordPress discoverability to help guide implementation priorities.
 * **OAuth architecture:** Explore authentication requirements and whether shared
   OAuth infrastructure should be considered for WordPress 7.3.
 * **PHP AI Client maintenance:** [@jason_the_adams](https://profiles.wordpress.org/jason_the_adams/)
   will solicit additional maintainers to help reduce development bottlenecks.
 * **Streaming support:** [@whyisjake](https://profiles.wordpress.org/whyisjake/)
   will coordinate with a core committer to advance the outstanding Requests library
   pull request.

## Upcoming Meetings

 * Contributors are welcome to join the weekly AI contributor call. All team meeting
   schedules are published on the [WordPress Meeting Calendar](https://make.wordpress.org/meetings/#ai).
 * **AI Team Office Hours:** Thursday, October 29, 2026 at 17:00 UTC.

_Props to [@nikskyverge](https://profiles.wordpress.org/nikskyverge/), [@bacoords](https://profiles.wordpress.org/bacoords/)
for pre-publish review._

[#core-ai](https://make.wordpress.org/ai/tag/core-ai/), [#summary](https://make.wordpress.org/ai/tag/summary/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fai%2F2026%2F10%2F22%2Fai-contributor-weekly-summary-21-october-2026%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/jeffpaul/) [Jeffrey Paul](https://profiles.wordpress.org/jeffpaul/)
6:44 pm _on_ 22 October 2026     
Tags: [core-ai ( 88 )](https://make.wordpress.org/ai/tag/core-ai/),
[summary ( 47 )](https://make.wordpress.org/ai/tag/summary/)   

# 󠀁[AI Contributor Weekly Summary – 14 October 2026](https://make.wordpress.org/ai/2026/10/22/ai-contributor-weekly-summary-14-october-2026/)󠁿

_This week’s meeting focused on finalizing coreCore Core is the set of software 
required to run WordPress. The Core Development Team builds WordPress. abilities
ahead of WordPress 7.2 BetaBeta A pre-release of software that is given out to a
large group of users to trial under real conditions. Beta versions have gone through
alpha testing in-house and are generally fairly close in look, feel and function
to the final product; however, design changes often occur as part of the process.
1, improving schema compatibility across AI providers, and integrating the new Secrets
APIAPI An API or Application Programming Interface is a software intermediary that
allows programs to interact with each other and share data in limited, clearly defined
ways. with WordPress connectors. Contributors also discussed early benchmarking 
results for AI agents interacting with WordPress, the balance between core functionality
and ecosystem innovation, and emerging protocols for agent-based interactions._

## Core Abilities: Schema Refinements and WordPress 7.2

[@jason_the_adams](https://profiles.wordpress.org/jason_the_adams/) shared progress
from ongoing work with [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/)
and [@gziolo](https://profiles.wordpress.org/gziolo/) to finalize the core abilities
targeted for WordPress 7.2.

The team refined the input and output schemas, separating abilities that query collections
from those retrieving individual items. This simplifies the schemas, strengthens
type definitions through nested objects, and improves compatibility with AI providers
that have limitations around certain schema structures.

The settings abilityAbility A registered, self-documenting unit of WordPress functionality
that can be discovered and invoked through multiple contexts (REST API, Command 
Palette, MCP). Includes authorization and input/output specifications. remains ready,
while the users and content abilities are undergoing final reviews ahead of Beta
1. Additional single-item and write abilities remain under development and may follow
after the initial release.

[@jeffpaul](https://profiles.wordpress.org/jeffpaul/) suggested prioritizing the
core implementations until Beta 1, then returning to the remaining abilities in 
the AI pluginPlugin A plugin is a piece of software containing a group of functions
that can be added to a WordPress website. They can extend functionality or add new
features to your WordPress websites. WordPress plugins are written in the PHP programming
language and integrate seamlessly with WordPress. These can be free in the WordPress.
org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
or can be cost-based plugin from a third-party.. The team agreed this would avoid
duplicating work while the schemas are still changing, with the goal of making a
broader set of abilities available through the plugin ahead of WordPress 7.3.

The discussion also highlighted workflows as an important non-AI use case for abilities.
[@nikskyverge](https://profiles.wordpress.org/nikskyverge/) noted that workflows
provide a useful way to test whether abilities are sufficiently predictable, composable,
and reusable beyond AI agents.

## AI ProviderProvider An AI service offering models for generation, embeddings, or other capabilities (e.g., Anthropic, Google, OpenAI). Schema Compatibility

[@gziolo](https://profiles.wordpress.org/gziolo/) reported discovering compatibility
issues with Gemini’s tool-calling implementation during testing. Certain schema 
constraints, including validation keywords such as `minimum` and `maximum`, are 
not consistently supported across providers.

[@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/) recommended
maintaining broadly useful validation rules in core while allowing individual provider
integrations to remove or adapt unsupported keywords. This would avoid weakening
core schemas to accommodate limitations in individual AI providers.

The team discussed potential improvements to the PHPPHP PHP (recursive acronym for
PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting
language that is especially suited for web development and can be embedded into 
HTML. [https://www.php.net/manual/en/index.php](https://www.php.net/manual/en/index.php)
AI Client that would allow providers to transform schemas automatically, improving
compatibility for third-party plugins that may not test against every available 
provider.

[@gziolo](https://profiles.wordpress.org/gziolo/) will file issues documenting the
Gemini incompatibilities, with additional testing planned during the WordPress 7.2
beta period.

## Secrets API and Connector Integration

[@whyisjake](https://profiles.wordpress.org/whyisjake/) shared details about the
newly merged Secrets API, which introduces support for securely storing encrypted
values in WordPress core.

The API includes a migrationMigration Moving the code, database and media files 
for a website site from one server to another. Most typically done when changing
hosting companies. mechanism that allows developers to convert existing plaintext
options into encrypted secrets, providing a path for existing integrations to adopt
the new functionality without requiring users to re-enter credentials.

[@gziolo](https://profiles.wordpress.org/gziolo/) and [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/)
discussed integrating the Secrets API directly with WordPress connectors so provider
API keys can benefit from encrypted storage. [@whyisjake](https://profiles.wordpress.org/whyisjake/)
agreed to open a tracking ticket and begin work, with timing dependent on the upcoming
GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress.
The editor improves the process and experience of creating new content, making writing
rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes,
custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)
code freeze.

The team also discussed compatibility with encryption functionality already implemented
in the AI plugin, including the existing [migration issue](https://github.com/WordPress/ai/issues/1012).

The Secrets API is part of a broader WordPress security initiative, although secure
storage of AI provider credentials remains a key use case.

## AI AgentAI Agent An AI system that autonomously performs tasks and interacts with systems through available tools and resources. Benchmarking and MCP Effectiveness

[@apeatling](https://profiles.wordpress.org/apeatling/) shared preliminary results
from benchmarking AI agents against typical WordPress editing tasks. The benchmark
includes approximately 50–60 prompts tested across different models and environments,
comparing the MCP AdapterMCP Adapter Translates WordPress abilities into Model Context
Protocol format, allowing AI assistants like Claude and ChatGPT to discover and 
invoke WordPress capabilities as tools, resources, and prompts., third-party integrations,
and setups without dedicated connectors.

Early results suggest that agents can sometimes complete tasks more successfully
without an MCP connector than with the current implementations. [@apeatling](https://profiles.wordpress.org/apeatling/)
emphasized that these findings are preliminary, with additional runs needed before
drawing conclusions.

The benchmarking intentionally uses default environments without assuming tools 
such as WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to
do administrative and development tasks in a programmatic way. The project page 
is [http://wp-cli.org/](http://wp-cli.org/) [https://make.wordpress.org/cli/](https://make.wordpress.org/cli/)
are already installed, providing a closer representation of the experience for everyday
WordPress users rather than developers with customized setups.

[@apeatling](https://profiles.wordpress.org/apeatling/) plans to share more comprehensive
results and expand testing to include personal agents and environments such as Muse
and Grok Bot.

## WordPress Core, MCP, and Ecosystem Strategy

The team discussed whether WordPress should take a more opinionated approach to 
providing a consistent foundation for AI agents.

[@apeatling](https://profiles.wordpress.org/apeatling/) raised concerns that multiple
independently developed MCP servers could create fragmented experiences, inconsistent
security practices, and confusion for both users and AI agents. A standardized entry
point could provide a more reliable foundation while allowing hosts and plugins 
to extend functionality.

[@nikskyverge](https://profiles.wordpress.org/nikskyverge/) drew parallels to WooCommerce,
where extensions initially drive innovation before common capabilities are incorporated
into the platform. Contributors generally recognized the value of allowing ecosystem
experimentation while identifying opportunities to standardize successful approaches.

The discussion also explored how AI agents may increasingly become an entry point
for discovering and interacting with websites, raising questions about how WordPress
sites, hosts, and services remain discoverable through emerging agent platforms.

[@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/) highlighted
WebMCP as a promising direction for exposing WordPress functionality directly to
browser-based agents, potentially allowing them to interact with forms, content,
and editing interfaces without requiring separate connection setup.

No specific architectural changes were agreed upon, but the discussion reinforced
the importance of a consistent, extensibleExtensible This is the ability to add 
additional functionality to the code. Plugins extend the WordPress core software.
foundation for future agent interactions.

---

## Next Steps

 * **Core abilities:** [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/)
   and [@gziolo](https://profiles.wordpress.org/gziolo/) will continue finalizing
   the users and content abilities ahead of WordPress 7.2 Beta 1.
 * **AI plugin abilities:** Resume work on the remaining ability implementations
   after Beta 1, incorporating the updated core schemas.
 * **Provider compatibility:** [@gziolo](https://profiles.wordpress.org/gziolo/)
   will document Gemini schema compatibility issues and investigate provider-level
   transformations.
 * **Secrets API:** [@whyisjake](https://profiles.wordpress.org/whyisjake/) will
   create a tracking ticket for connector integration and share demonstration videos
   with [@jason_the_adams](https://profiles.wordpress.org/jason_the_adams/).
 * **Beta 1 communication:** [@jason_the_adams](https://profiles.wordpress.org/jason_the_adams/)
   will prepare a post summarizing the AI-related work included in WordPress 7.2
   Beta 1.
 * **Agent benchmarking:** [@apeatling](https://profiles.wordpress.org/apeatling/)
   will continue testing across models and environments, expand coverage to additional
   agent platforms, and share results with the team.

## Upcoming Meetings

 * Contributors are welcome to join the weekly AI contributor call. All team meeting
   schedules are published on the [WordPress Meeting Calendar](https://make.wordpress.org/meetings/#ai).
 * **AI Team Office Hours:** Thursday, October 15, 2026 at 17:00 UTC.

_Props to [@nikskyverge](https://profiles.wordpress.org/nikskyverge/) for pre-publish
review._

[#core-ai](https://make.wordpress.org/ai/tag/core-ai/), [#summary](https://make.wordpress.org/ai/tag/summary/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fai%2F2026%2F10%2F22%2Fai-contributor-weekly-summary-14-october-2026%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/jeffpaul/) [Jeffrey Paul](https://profiles.wordpress.org/jeffpaul/)
6:30 pm _on_ 22 October 2026     
Tags: [core-ai ( 88 )](https://make.wordpress.org/ai/tag/core-ai/),
[summary ( 47 )](https://make.wordpress.org/ai/tag/summary/)   

# 󠀁[AI Contributor Weekly Summary – 7 October 2026](https://make.wordpress.org/ai/2026/10/22/ai-contributor-weekly-summary-7-october-2026/)󠁿

_This week’s meeting focused on preparing coreCore Core is the set of software required
to run WordPress. The Core Development Team builds WordPress. abilities for WordPress
7.2 BetaBeta A pre-release of software that is given out to a large group of users
to trial under real conditions. Beta versions have gone through alpha testing in-
house and are generally fairly close in look, feel and function to the final product;
however, design changes often occur as part of the process. 1, including the status
of settings, content, and user abilities, architectural decisions around REST APIREST
API The REST API is an acronym for the RESTful Application Program Interface (API)
that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end
of an application (think “phone app” or “website”) can communicate with the data
store (think “database” or “file system”) [https://developer.wordpress.org/rest-api/](https://developer.wordpress.org/rest-api/)
independence, and naming conventions. Contributors also discussed the recent MCP
AdapterMCP Adapter Translates WordPress abilities into Model Context Protocol format,
allowing AI assistants like Claude and ChatGPT to discover and invoke WordPress 
capabilities as tools, resources, and prompts. release, improvements to abilityAbility
A registered, self-documenting unit of WordPress functionality that can be discovered
and invoked through multiple contexts (REST API, Command Palette, MCP). Includes
authorization and input/output specifications. exposure controls and connection 
management, and the longer-term goal of making AI integration with WordPress easier
for everyday users._

## Core Abilities: WordPress 7.2 Readiness

[@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/) provided an
update on the core abilities targeted for WordPress 7.2. The settings ability has
received approval from a core reviewer, content abilities have incorporated recent
feedback, and user abilities are undergoing another iteration. Additional abilities
for updating content, media, and comments are also progressing through the AI pluginPlugin
A plugin is a piece of software containing a group of functions that can be added
to a WordPress website. They can extend functionality or add new features to your
WordPress websites. WordPress plugins are written in the PHP programming language
and integrate seamlessly with WordPress. These can be free in the WordPress.org 
Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
or can be cost-based plugin from a third-party..

[@gziolo](https://profiles.wordpress.org/gziolo/) emphasized the importance of reviewing
the broader set of abilities together to ensure consistent naming, functionality,
and compatibility. He suggested prioritizing read-only abilities for content and
users, which would provide immediate value and allow developers to begin testing
integrations while more complex write operations continue to evolve.

[@jason_the_adams](https://profiles.wordpress.org/jason_the_adams/) supported moving
forward with the ready abilities rather than treating the broader catalog as an 
all-or-nothing release. He committed to reviewing the settings, content, and user
implementations, with a follow-up discussion planned if outstanding issues could
not be resolved through code review.

[@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/) will also 
update the draft merge proposal to reflect the current implementation status and
release timeline.

## Core Abilities Architecture and Security

The team discussed whether core abilities should proxy existing REST API functionality
or operate through an independent implementation.

[@gziolo](https://profiles.wordpress.org/gziolo/) outlined trade-offs between the
two approaches, including implementation complexity, compatibility with existing
plugins, and the potential for unintended behavior when REST API filters affect 
exposed data.

[@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/) clarified 
that the current implementation uses a parallel mechanism rather than routing ability
execution through REST. Post types must explicitly opt in using `show_in_abilities`,
independently of their REST API visibility. This prevents accidentally exposing 
content that plugins may have restricted through REST-specific filters.

The team generally supported maintaining this separation, recognizing that explicit
opt-in introduces additional work for developers but provides a safer foundation
for exposing WordPress functionality, including through AI tools.

## Ability Naming and Categorization

[@justlevine](https://profiles.wordpress.org/justlevine/) raised questions about
the proposed noun-verb naming convention, including names such as `settings/get`
and `content/query`.

[@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/) explained 
that placing the entity name first groups related abilities together when sorted
alphabetically and aligns with conventions already used by WooCommerce. The distinction
between `get` and `query` reflects whether an ability retrieves a specific value
or supports more complex filtering and searches.

[@raftaar1191](https://profiles.wordpress.org/raftaar1191/) also proposed allowing
abilities to belong to multiple categories rather than a single required categoryCategory
The 'category' taxonomy lets you group posts / content together that share a common
bond. Categories are pre-defined and broad ranging..

[@jason_the_adams](https://profiles.wordpress.org/jason_the_adams/) explained that
ability categories were originally introduced to help AI agents and other consumers
narrow down large collections of available tools. Allowing multiple categories could
weaken that filtering behavior, so the team encouraged documenting concrete use 
cases before reconsidering the existing design.

A tracking issue will be opened to explore the proposal further.

## MCP Adapter Release and Improvements

[@jason_the_adams](https://profiles.wordpress.org/jason_the_adams/) highlighted 
the positive community response to the recent release of the MCP Adapter on WordPress.
orgWordPress.org The community site where WordPress code is created and shared by
the users. This is where you can download the source code for WordPress core, plugins
and themes as well as the central location for community conversations and organization.
[https://wordpress.org/](https://wordpress.org/).

[@ovidiu-galatan](https://profiles.wordpress.org/ovidiu-galatan/) shared ongoing
work to improve the adapter, including breaking down an issue related to displaying
connection information and server status into smaller tasks. A maintenance release
addressing outstanding issues was planned for the following week.

The team also discussed compatibility concerns when different versions of shared
functionality are bundled across plugins and WordPress core. Further investigation
is needed to clarify version conflicts and how implementations should interact when
multiple versions are present.

## Ability Exposure Controls and User Experience

[@andrei](https://profiles.wordpress.org/andrei/) shared progress on an experimental
interface in the AI plugin for controlling which abilities are exposed through MCP
integrations. The implementation uses WordPress DataViews and could provide an initial
interface for users to manage exposed capabilities.

[@dkotter](https://profiles.wordpress.org/dkotter/) recommended continuing with 
the implementation in the AI plugin rather than delaying it to move the functionality
into the MCP Adapter. Because it is experimental, the interface can be refined or
relocated as the integration matures.

[@jason_the_adams](https://profiles.wordpress.org/jason_the_adams/) noted that the
MCP Adapter is increasingly reaching users beyond its original developer audience,
making clearer onboarding and management interfaces important. [@nikskyverge](https://profiles.wordpress.org/nikskyverge/)
is preparing a release post that explains the adapter’s development history and 
current capabilities.

Looking further ahead, [@apeatling](https://profiles.wordpress.org/apeatling/) emphasized
that the ideal experience should require minimal configuration, allowing users to
connect AI tools to WordPress without needing to understand the underlying protocols
or infrastructure. The discussion highlighted the importance of balancing secure,
flexible controls with an experience that feels seamless for everyday users.

---

## Next Steps

 * **Core abilities reviews:** [@jason_the_adams](https://profiles.wordpress.org/jason_the_adams/)
   will review the settings, content, and users query implementations, with contributors
   regrouping if significant blockers remain.
 * **WordPress 7.2 merge proposal:** [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/)
   will update the proposal to reflect the current scope and timeline.
 * **Ability categorization:** [@raftaar1191](https://profiles.wordpress.org/raftaar1191/)
   will open a tracking issue exploring support for multiple categories per ability.
 * **MCP Adapter:** [@ovidiu-galatan](https://profiles.wordpress.org/ovidiu-galatan/)
   will continue work on connection management improvements and prepare a maintenance
   release.
 * **Version compatibility:** Contributors will investigate conflicts when multiple
   versions of shared functionality are bundled across plugins.
 * **MCP Adapter communication:** [@nikskyverge](https://profiles.wordpress.org/nikskyverge/)
   will continue drafting the release post outlining the adapter’s capabilities 
   and intended audience.

## Upcoming Meetings

 * Contributors are welcome to join the weekly AI contributor call. All team meeting
   schedules are published on the [WordPress Meeting Calendar](https://make.wordpress.org/meetings/#ai).
 * **AI Team Office Hours:** Thursday, October 15, 2026 at 17:00 UTC.

_Props to [@nikskyverge](https://profiles.wordpress.org/nikskyverge/) for pre-publish
review._

[#core-ai](https://make.wordpress.org/ai/tag/core-ai/), [#summary](https://make.wordpress.org/ai/tag/summary/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fai%2F2026%2F10%2F22%2Fai-contributor-weekly-summary-7-october-2026%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/jeffpaul/) [Jeffrey Paul](https://profiles.wordpress.org/jeffpaul/)
6:21 pm _on_ 22 October 2026     
Tags: [core-ai ( 88 )](https://make.wordpress.org/ai/tag/core-ai/),
[summary ( 47 )](https://make.wordpress.org/ai/tag/summary/)   

# 󠀁[AI Contributor Weekly Summary – 30 September 2026](https://make.wordpress.org/ai/2026/10/22/ai-contributor-weekly-summary-30-september-2026/)󠁿

_This week’s meeting focused on the roadmap for bringing coreCore Core is the set
of software required to run WordPress. The Core Development Team builds WordPress.
WordPress abilities into future releases, the role of the AI pluginPlugin A plugin
is a piece of software containing a group of functions that can be added to a WordPress
website. They can extend functionality or add new features to your WordPress websites.
WordPress plugins are written in the PHP programming language and integrate seamlessly
with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
or can be cost-based plugin from a third-party. and Model Context Protocol (MCP)
Adapter in validating and distributing those abilities, and outstanding technical
considerations around schema design and compatibility. The team discussed a potential
timeline for WordPress 7.2 and 7.3, with an emphasis on balancing faster adoption
against long-term architectural stability._

## Core Abilities Roadmap and WordPress 7.2

[@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/) shared a draft
proposal outlining a path for developing and validating core WordPress abilities
ahead of their inclusion in WordPress core. The proposal calls for making a broader
set of abilities available through the AI plugin by the WordPress 7.2 release, with
the goal of including ready abilities in 7.2 and targeting broader core adoption
in 7.3.

The discussion focused on content-related abilities, including querying and managing
posts, as initial candidates. Contributors emphasized that these are fundamental
capabilities for a content management system and that a shared implementation would
reduce duplication across plugins and integrations.

[@gziolo](https://profiles.wordpress.org/gziolo/) noted that existing core pull 
requests have undergone security reviews and REST APIREST API The REST API is an
acronym for the RESTful Application Program Interface (API) that uses HTTP requests
to GET, PUT, POST and DELETE data. It is how the front end of an application (think“
phone app” or “website”) can communicate with the data store (think “database” or“
file system”) [https://developer.wordpress.org/rest-api/](https://developer.wordpress.org/rest-api/)
compatibility testing, providing confidence in their readiness. [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/)
also confirmed that earlier feedback on naming conventions has been addressed, though
additional validation against real-world implementations and AI clients remains 
valuable.

The team generally supported using the AI plugin to validate abilities before core
inclusion, while recognizing that neither WordPress 7.2 nor 7.3 should become a 
hard deadline for functionality that has unresolved technical concerns or lacks 
consensus.

## MCP AdapterMCP Adapter Translates WordPress abilities into Model Context Protocol format, allowing AI assistants like Claude and ChatGPT to discover and invoke WordPress capabilities as tools, resources, and prompts. and Abilities Distribution

[@justlevine](https://profiles.wordpress.org/justlevine/) proposed using the MCP
Adapter as an additional distribution channel for MCP-specific abilities, allowing
integrations to move forward without requiring every capability to be immediately
included in WordPress core.

The approach would separate immediate MCP integration needs from the longer-term
work of establishing reusable, protocol-independent abilities in core. This would
allow MCP-specific implementations to evolve independently while reducing pressure
to finalize core interfaces prematurely.

[@gziolo](https://profiles.wordpress.org/gziolo/), [@jason_the_adams](https://profiles.wordpress.org/jason_the_adams/),
and others emphasized that the MCP Adapter should not become a substitute for bringing
foundational abilities into core. Standardized core abilities would reduce ecosystem
fragmentation, improve consistency across plugins, and establish examples of secure
implementation practices for developers.

The discussion also highlighted that abilities serve more than MCP integrations,
with WebMCP and the WordPress AI Client representing additional consumers.

The general direction was to continue prioritizing core adoption while allowing 
the MCP Adapter to address immediate, protocol-specific needs independently.

## AbilityAbility A registered, self-documenting unit of WordPress functionality that can be discovered and invoked through multiple contexts (REST API, Command Palette, MCP). Includes authorization and input/output specifications. Schemas, Compatibility, and Deprecation

[@justlevine](https://profiles.wordpress.org/justlevine/) raised concerns about 
the long-term flexibility of flat input schemas, particularly as abilities expand
to support more sophisticated filtering, sorting, and pagination. Nested input objects,
following patterns established by GraphQL, were suggested as a way to improve extensibility
and reduce future compatibility challenges.

[@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/) noted that
the current schemas follow established WordPress REST API and WooCommerce conventions
and have not demonstrated significant compatibility issues in existing testing.

[@jason_the_adams](https://profiles.wordpress.org/jason_the_adams/) requested side-
by-side examples of the different schema approaches to help distinguish necessary
changes from potential future improvements. The team emphasized identifying concrete
blockers rather than delaying progress in pursuit of an ideal design.

[@justlevine](https://profiles.wordpress.org/justlevine/) also reported progress
on ability deprecation support, with a pull request already submitted and additional
work underway to support deprecating individual ability arguments. This work could
help abilities evolve without introducing unnecessary breaking changes.

---

## Next Steps

 * **Core abilities proposal:** [@jason_the_adams](https://profiles.wordpress.org/jason_the_adams/)
   will review the draft roadmap from [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/)
   and share feedback in the [#core-ai](https://make.wordpress.org/ai/tag/core-ai/)
   SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/).
   The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)
   channel.
 * **Schema examples:** [@justlevine](https://profiles.wordpress.org/justlevine/)
   will share side-by-side examples of flat and nested input structures to clarify
   the compatibility concerns.
 * **Ability development:** Continue work on core ability candidates, including 
   schema validation, deprecation support, and testing across MCP and other consumers.
 * **Slug fragments:** [@justlevine](https://profiles.wordpress.org/justlevine/)
   will continue work to unblock the slug fragments implementation.
 * **Release planning:** Continue refining the proposed WordPress 7.2 and 7.3 roadmap,
   identifying remaining technical blockers and opportunities for real-world validation
   through the AI plugin.

## Upcoming Meetings

 * Contributors are welcome to join the weekly AI contributor call. All team meeting
   schedules are published on the [WordPress Meeting Calendar](https://make.wordpress.org/meetings/#ai).
 * **AI Team Office Hours:** Thursday, October 1, 2026 at 17:00 UTC.

_Props to [@nikskyverge](https://profiles.wordpress.org/nikskyverge/) for pre-publish
review._

[#summary](https://make.wordpress.org/ai/tag/summary/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fai%2F2026%2F10%2F22%2Fai-contributor-weekly-summary-30-september-2026%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/nikskyverge/) [Nik McLaughlin](https://profiles.wordpress.org/nikskyverge/)
8:52 pm _on_ 7 October 2026     
Tags: [canonical plugins ( 17 )](https://make.wordpress.org/ai/tag/canonical-plugins/),
[core-ai ( 88 )](https://make.wordpress.org/ai/tag/core-ai/), mcp-release   

# 󠀁[The MCP Adapter Plugin is Now Available on WordPress.Org](https://make.wordpress.org/ai/2026/10/07/the-mcp-adapter-plugin-is-now-available-on-wordpress-org/)󠁿

![](https://make.wordpress.org/ai/files/2026/10/wp-mcp-adapter-icon.png)

The WordPress CoreCore Core is the set of software required to run WordPress. The
Core Development Team builds WordPress. AI team is excited to share the public release
of the [MCP Adapter](https://wordpress.org/plugins/mcp-adapter/) as a canonical 
pluginPlugin A plugin is a piece of software containing a group of functions that
can be added to a WordPress website. They can extend functionality or add new features
to your WordPress websites. WordPress plugins are written in the PHP programming
language and integrate seamlessly with WordPress. These can be free in the WordPress.
org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
or can be cost-based plugin from a third-party. on the WordPress Plugin Directory.
The MCP AdapterMCP Adapter Translates WordPress abilities into Model Context Protocol
format, allowing AI assistants like Claude and ChatGPT to discover and invoke WordPress
capabilities as tools, resources, and prompts. plugin provides the default MCP serverMCP
Server Exposes tools, resources, and prompts according to Model Context Protocol
specification. WordPress can run multiple MCP servers with different configurations.
architecture for all WordPress sites and its release on the plugin repository is
a big milestone. This release simplifies installation and gives developers a more
reliable way to build your own MCP functionality on top of shared canonical architecture.

## What is MCP Adapter?

MCP Adapter provides a way for WordPress sites to expose site functionality to AI
agents and harnesses via the [Model Context Protocol](https://modelcontextprotocol.org).

 * **Provides a default MCP server **– the plugin ships with a default MCP server(
   endpoint: `/wp-json/mcp/mcp-adapter-default-server`) that includes three fundamental
   MCP tools. This serves as a common model for the ecosystem to extend and build
   upon, with options for developers to register your own tools, resources, and 
   prompts.
 * **Bridges WP Abilities to MCP** – the plugin bridges WordPress’s Abilities APIAbilities
   API A core WordPress API (introduced in 6.9) that creates a central registry 
   of capabilities, making WordPress functions discoverable and accessible to AI
   agents, automation tools, and developers. Transforms WordPress from isolated 
   functions into a unified system. with the MCP specification, providing a standardized
   way for AI agents to interact with WordPress functionality. Any publicly exposed
   WordPress Abilities on your site are automatically discoverable and executable
   via the default server’s tools. You can read more about abilityAbility A registered,
   self-documenting unit of WordPress functionality that can be discovered and invoked
   through multiple contexts (REST API, Command Palette, MCP). Includes authorization
   and input/output specifications. exposure via MCP in [these plugin docs](https://github.com/WordPress/mcp-adapter/blob/54ed266a8c46b71fdb8e5b8a7d35668f90fb8994/docs/guides/creating-abilities.md#mcp-exposure).
 * **Enables the creation of custom MCP servers **– MCP Adapter enables developers
   to build custom MCP Servers for WP sites or plugins. Developers can hook into`
   mcp_adapter_init` to create their own custom server for more direct or explicit
   integrations. See the [plugin docs](https://github.com/WordPress/mcp-adapter/blob/trunk/docs/guides/default-server.md)
   for guidance on when to use a custom server versus extending the default server.

The plugin is focused on providing server infrastructure for MCP connections, so
it does not currently include an MCP clientMCP Client AI agents, IDEs, or assistants
that connect to MCP servers to access capabilities. or UIUI UI is an acronym for
User Interface - the layout of the page the user interacts with. Think ‘how are 
they doing that’ and less about what they are doing. for a full, end-to-end, user-
facing agentic workflow. Please leave feedback in [the GitHub issues](https://github.com/WordPress/mcp-adapter/issues)
if you’d like to see this (or other functionality) added in a future release.

## Why a canonical plugin?

Earlier versions of the MCP Adapter were managed exclusively through the GitHubGitHub
GitHub is a website that offers online implementation of git repositories that can
easily be shared, copied and modified by other developers. Public repositories are
free to host, private repositories require a paid subscription. GitHub introduced
the concept of the ‘pull request’ where code changes done in branches by contributors
can be reviewed and discussed before being merged by the repository owner. [https://github.com/](https://github.com/)
repository and required users to either manually download and install the plugin,
or bundle it as a Composer dependency in their own code. This allowed early-adopters
to experiment and iterate alongside the Core AI team’s work, but kept installation
out of reach for most WordPress users and required plugin developers to handle dependency
updates and cross-plugin conflicts themselves.

On the other end of the spectrum, building a piece of shared canonical infrastructure
like this naturally raises the question: Why isn’t this part of core WordPress? 
At the time of writing, the MCP specification itself is still in flux, with a major
breaking update having shipped [less than three months ago](https://blog.modelcontextprotocol.io/posts/2026-07-28/).
This volatility makes MCP a poor fit for inclusion in the core WordPress package
at this time, which has massive, often automated distribution, it’s own independent
release cadence, and a strong commitment to backwards-compatibility.

Keeping MCP Adapter outside of WordPress Core allows the plugin to iterate rapidly
and stay in sync with the fast pace of change in the MCP specification itself and
the broader AI ecosystem. As a canonical plugin on [WordPress.org](http://WordPress.org),
end-users and plugin developers can rely on MCP Adapter without worrying about multiple
conflicting, outdated copies. Core WordPress features, such as [plugin dependencies](https://make.wordpress.org/core/2024/03/05/introducing-plugin-dependencies-in-wordpress-6-5/)
and [conditional autoinstall from WordPress.org](https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/#8-plugins-may-not-send-executable-code-via-third-party-systems)
allow plugins to still treat MCP Adapter as a dependency with the added benefit 
of keeping AI-related functionality transparent and auditable, in line with the 
Core AI Team’s [“Building Blocks” approach](https://make.wordpress.org/ai/2025/07/17/ai-building-blocks/).

## What’s new in 0.7.0?

 * Added support for the new, stateless `2026-07-28` MCP spec. Clients that request`
   2025-06-18` or `2024-11-05` still connect, and are served through the `2025-11-
   25` schema.
 * Direct callable tools can request elicitation input under `2026-07-28` with `
   McpInputRequired`.
 * Default abilities register even when another plugin initializes the Abilities
   API first.

If you were already using an older version of the plugin through GitHub or Composer,
check out the [0.7.0 Migration Guide](https://github.com/WordPress/mcp-adapter/blob/trunk/docs/migration/v0.7.0.md)
to see if you need to make any changes to your integration.

## What’s next?

MCP Adapter is still experimental, and the current focus is on providing key infrastructure
while gathering feedback from developers to reach a stable v1.0 release.

You can follow progress or contribute via the [MCP Adapter plugin repo](https://github.com/WordPress/mcp-adapter).

## Thanks to our contributors!

**Thank you to everyone who has helped shape this release**: [@abhi3315](https://profiles.wordpress.org/abhi3315/),
[@dkotter](https://profiles.wordpress.org/dkotter/), [@euthelup](https://profiles.wordpress.org/euthelup/),
[@georgestephanis](https://profiles.wordpress.org/georgestephanis/), [@gziolo](https://profiles.wordpress.org/gziolo/),
[@jeffpaul](https://profiles.wordpress.org/jeffpaul/), [@justlevine](https://profiles.wordpress.org/justlevine/),
[@laurisaarni](https://profiles.wordpress.org/laurisaarni/), [@mmaattiiaass](https://profiles.wordpress.org/mmaattiiaass/),
[@obenland](https://profiles.wordpress.org/obenland/), [@otaconflex](https://profiles.wordpress.org/otaconflex/),
[@stormrockwell](https://profiles.wordpress.org/stormrockwell/), [@ugyensupport](https://profiles.wordpress.org/ugyensupport/),
[@urbankidro](https://profiles.wordpress.org/urbankidro/), and especially to [@ovidiu-galatan](https://profiles.wordpress.org/ovidiu-galatan/)
for the tireless work in getting MCP Adapter to where it is today.

_Props to _[@apeatling](https://profiles.wordpress.org/apeatling/) [@justlevine](https://profiles.wordpress.org/justlevine/)
and [@laurisaarni](https://profiles.wordpress.org/laurisaarni/)_ for pre-publish
review._

[#canonical-plugins](https://make.wordpress.org/ai/tag/canonical-plugins/), [#core-ai](https://make.wordpress.org/ai/tag/core-ai/),
[#mcp-release](https://make.wordpress.org/ai/tag/mcp-release/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fai%2F2026%2F10%2F07%2Fthe-mcp-adapter-plugin-is-now-available-on-wordpress-org%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/jeffpaul/) [Jeffrey Paul](https://profiles.wordpress.org/jeffpaul/)
2:09 pm _on_ 6 October 2026     
Tags: [AI Experiments ( 17 )](https://make.wordpress.org/ai/tag/ai-experiments/),
[AI Features ( 10 )](https://make.wordpress.org/ai/tag/ai-features/), [AI Plugin ( 10 )](https://make.wordpress.org/ai/tag/ai-plugin/),
[ai-release ( 15 )](https://make.wordpress.org/ai/tag/ai-release/), [canonical plugins ( 17 )](https://make.wordpress.org/ai/tag/canonical-plugins/),
[core-ai ( 88 )](https://make.wordpress.org/ai/tag/core-ai/)   

# 󠀁[What’s new in AI 1.4.0 (5 OCTOBER 2026)?](https://make.wordpress.org/ai/2026/10/06/whats-new-in-ai-1-4-0/)󠁿

**AI 1.4.0** has been released and is [available for download](https://wordpress.org/plugins/ai/)!“
What’s new in AI…” posts (labeled with the [#ai-release tag](https://make.wordpress.org/ai/tag/ai-release/))
are posted following every AI pluginPlugin A plugin is a piece of software containing
a group of functions that can be added to a WordPress website. They can extend functionality
or add new features to your WordPress websites. WordPress plugins are written in
the PHP programming language and integrate seamlessly with WordPress. These can 
be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
or can be cost-based plugin from a third-party. release, showcasing new features
included in each release

![](https://make.wordpress.org/ai/files/2026/10/ai-1-4-0.png)

We’re pleased to announce the release of [AI 1.4.0](https://github.com/WordPress/ai/releases/tag/1.4.0),
the latest update to the canonical plugin powering AI-powered features in WordPress.
This release introduces Markdown feeds for making WordPress content easier for AI
systems and other Markdown consumers to access, expands the Embeddings infrastructure,
and adds a new Comment Value score to Comment Moderation. It also improves Content
Translation, Type Ahead, Alt Text Generation, AI Request Logging, and several existing
developer tools.

## What’s new in 1.4.0?

### New Experiment: Markdown Feeds

The new Markdown Feeds experiment provides Markdown-formatted versions of WordPress
content alongside the existing HTMLHTML HTML is an acronym for Hyper Text Markup
Language. It is a markup language that is used in the development of web pages and
websites. and feed formats.

When enabled, sites gain a Markdown feed at `/feed/markdown/`, including the equivalent
feed URLs for other WordPress feed contexts. Individual posts and pages can also
be requested as Markdown by adding `?output_format=markdown` to their URLURL A specific
web address of a website or web page on the Internet, such as a website’s URL www.
wordpress.org. This provides a cleaner, structured representation of published content
for AI agents, language models, developer tools, and other systems that can work
more efficiently with Markdown than rendered HTML. The implementation converts WordPress
content to Markdown while preserving common structures such as headings, links, 
images, lists, blockquotes, and code. Post titles, excerpts, and other feed content
are also normalized to avoid leaking HTML entities into the Markdown output.

### Comment Moderation adds a value score

Comment Moderation now evaluates how substantive and relevant a comment is to the
post where it was submitted.

When moderation runs, each analyzed comment receives a value score between 0 and
1. The score is displayed as a new column on the Comments screen alongside the existing
moderation signals. The goal is to provide an additional signal beyond toxicity 
and sentiment. A comment can be perfectly civil while still adding little to the
discussion, while another may contain substantial information or meaningfully engage
with the post. Bulk comment analysis has also been updated to limit the size of 
the moderation queue, helping avoid unnecessarily large processing requests.

### Expanded embeddings and vector infrastructure

AI 1.4.0 significantly expands the embeddings foundation introduced in the previous
release.

The plugin now includes a storage and CRUD layer for embedding vectors using a new`
wpai_embeddings` database table. Stored vectors can include information about the
providerProvider An AI service offering models for generation, embeddings, or other
capabilities (e.g., Anthropic, Google, OpenAI). and model used to generate them,
providing a common foundation for future semantic search, retrieval, recommendations,
and other vector-based features.

The release also introduces `Vector_Math` and `Vector_Ranker` classes for calculating
vector similarity and ranking results.

These additions are primarily developer infrastructure rather than a new end-user
experiment today, but they establish reusable building blocks for future AI features
that need to understand the semantic relationship between content. Embedding generation
has also been updated to use the latest implementation from the PHPPHP PHP (recursive
acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose
scripting language that is especially suited for web development and can be embedded
into HTML. [https://www.php.net/manual/en/index.php](https://www.php.net/manual/en/index.php)
AI Client.

The `generate_embeddings` helper now requires callers to specify an embedding model.
Developers should pass either a model ID or a `ModelInterface` instance. When passing
a model ID, the provider offering that model must also be specified. **_This is 
a breaking change for third-party code that began using the embedding helper introduced
in earlier versions._**

### Content Translation improvements

Content Translation gains several workflow and language improvements in 1.4.0.

Nine additional default target languages are now available, and the underlying Content
Translation abilityAbility A registered, self-documenting unit of WordPress functionality
that can be discovered and invoked through multiple contexts (REST API, Command 
Palette, MCP). Includes authorization and input/output specifications. can incorporate
relevant WordPress editorial guideline categories when generating translations. 
If a translation request fails, editors can now retry it directly rather than closing
and restarting the workflow. The translation interface also better preserves existing
text and background colors while content is being processed. Title translation is
disabled with an explanatory notice when the title is too short to provide enough
useful context.

### Alt Text Generation understands decorative images

Alt Text Generation now integrates with the Image blockBlock Block is the abstract
term used to describe units of markup that, composed together, form the content 
or layout of a webpage using the WordPress editor. The idea combines concepts of
what in the past may have achieved with shortcodes, custom HTML, and embed discovery
into a single consistent API and user experience.’s decorative-image setting. Images
explicitly marked as decorative are treated accordingly rather than being presented
as candidates for generated alternative text. This brings the AI workflow into closer
alignment with the accessibilityAccessibility Accessibility (commonly shortened 
to a11y) refers to the design of products, devices, services, or environments for
people with disabilities. The concept of accessible design ensures both “direct 
access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s
assistive technology (for example, computer screen readers). (https://en.wikipedia.
org/wiki/Accessibility) semantics already available in the editor.

### Type Ahead workflow improvements

Type Ahead now provides a visible loading indicator while a suggestion is being 
generated, making it clearer when the feature is processing a request. The editor
also reserves space for suggestions when the caret is positioned at the end of a
paragraph, reducing layout and text-placement issues while ghost text is generated.

### AI Request Logging improvements

AI Request Logging now handles provider errors more accurately.

HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying
protocol used by the World Wide Web and this protocol defines how messages are formatted
and transmitted, and what actions Web servers and browsers should take in response
to various commands. 4xx and 5xx responses from providers are recorded as errors
with their status code and message rather than being incorrectly recorded as successful
requests. Gemini text-generation requests are also categorized correctly rather 
than appearing as metadata operations. These changes should make the request log
more useful when troubleshooting provider configuration or failed generations.

### Updated Abilities

Several of the general-purpose WordPress abilities introduced in earlier releases
have been renamed to better describe their behavior:

 * `core/read-content` is now `core/content-query`
 * `core/read-users` is now `core/users-query`
 * `core/read-settings` is now `core/settings-get`

The previous names continue to work as deprecated aliases for now, giving existing
integrations time to migrate. The `ai/get-post-details` ability is also deprecated.
Developers should use the single-post mode of `core/content-query` instead.

### The global “Enable AI” setting has been removed

The “Enable AI” toggle previously displayed at the top of the AI settings screen
has been removed. Features and experiments continue to be controlled individually
from the AI settings interface, eliminating the additional global toggle.

### Accessibility and workflow improvements

The release includes several fixes across existing experiments and interfaces:

 * Content Resizing now moves keyboard focus to the Accept button after content 
   generation completes.
 * Content Classification suggestion pills use focus styles aligned with WordPress
   coreCore Core is the set of software required to run WordPress. The Core Development
   Team builds WordPress. components.
 * Collapsible settings cards receive corrected focus styles.
 * Suggest Reply is hidden when a comment is being edited using Quick Edit.
 * Editorial Notes correctly analyzes template blocks when the editor’s “Show template”
   mode is enabled.
 * Generated summaries are inserted correctly when working in “Show template” mode.
 * Abilities Explorer no longer crashes when an ability input property supports 
   multiple data types.
 * Content normalization better preserves HTML entities and text surrounding shortcodes.
 * Saving general WordPress settings no longer produces validation errors when the
   plugin’s abilities are active.

The release also includes several compatibility and performance improvements, including
cached detection of active SEO plugins and improved handling of connector approval
checks.

### Minimum WordPress version is now 7.0.3

AI 1.4.0 increases the minimum supported WordPress version to 7.0.3. **_Sites running
an earlier WordPress release should update WordPress before upgrading the AI plugin._**

### Security improvements

AI 1.4.0 includes several additional security hardening changes. Bulk Comment Moderation
now verifies that the current user has the `moderate_comments` capability before
processing a request and checks the `edit_comment` capability for each individual
comment. The release also hardens JSONJSON JSON, or JavaScript Object Notation, 
is a minimal, readable format for structuring data. It is used primarily to transmit
data between a server and web application, as an alternative to XML. data parsing
within admin screens and improves the security of the WordPress Playground preview
publishing workflow by deriving pull request and commit metadata directly from the
triggering workflow run.

**_Sites using the AI plugin are encouraged to update promptly._**

## What’s next?

Work is already underway on additional Features, Experiments, Developer Tools, and
Abilities planned for [1.5.0](https://github.com/WordPress/ai/milestone/24) and 
future releases, including:

 * New Experiment: [Text to Speech](https://github.com/WordPress/ai/pull/888)
 * New Experiment: [Promoted AI Provider Connectors](https://github.com/WordPress/ai/issues/27)
 * New Experiment: [Embeddings Support](https://github.com/WordPress/ai/issues/962)
 * New Experiment: [Internal Link Suggestions](https://github.com/WordPress/ai/pull/887)
 * New Experiment: [Integrate with Gutenberg’s experimental Media Editor](https://github.com/WordPress/ai/issues/325)
   including [focus-aware crop suggestions](https://github.com/WordPress/ai/issues/238)
 * New Experiment: Content Provenance tracking for [text](https://github.com/WordPress/ai/pull/294)
   and [images](https://github.com/WordPress/ai/pull/302) via [C2PA](https://c2pa.org/)
   while [detecting C2PA manifests on upload](https://github.com/WordPress/ai/issues/421)
 * Updated Experiment: [Integrate Refine from Notes with Real-time Collaboration](https://github.com/WordPress/ai/issues/324)
 * New Developer Tool: [Role and User access controls](https://github.com/WordPress/ai/pull/749)
 * New Abilities: [`core/term-create`, `core/term-update`, and `core/term-delete`](https://github.com/WordPress/ai/pull/1103)
 * New Abilities: [`core/media-upload`, `core/media-update`, and `core/media-delete`](https://github.com/WordPress/ai/pull/1104)
   plus [`core/media-query`](https://github.com/WordPress/ai/pull/1098)
 * New Abilities: [`core/user-create`, `core/user-update`, and `core/user-delete`](https://github.com/WordPress/ai/pull/1105)
 * New Abilities: [`core/content-create`, `core/content-update`, and `core/content-delete`](https://github.com/WordPress/ai/pull/1025)
 * New Abilities: [`core/post-types-query`](https://github.com/WordPress/ai/pull/1106),
   [`core/settings-update`](https://github.com/WordPress/ai/pull/764), and [`core/terms-query`](https://github.com/WordPress/ai/pull/1099)

These concepts are still exploratory, but they help test how AI could support real
workflows across WordPress.

## Thanks to contributors!

A big thank you to everyone who contributed to this release, including:

[@dkotter](https://profiles.wordpress.org/dkotter/), [@jeffpaul](https://profiles.wordpress.org/jeffpaul/),
[@priyanshuhaldar](https://profiles.wordpress.org/priyanshuhaldar/), [@yogeshbhutkar](https://profiles.wordpress.org/yogeshbhutkar/),
[@ekamran](https://profiles.wordpress.org/ekamran/), [@colinmcdonough](https://profiles.wordpress.org/colinmcdonough/),
[@wprashed](https://profiles.wordpress.org/wprashed/), [@theaminuldev](https://profiles.wordpress.org/theaminuldev/),
[@noruzzaman](https://profiles.wordpress.org/noruzzaman/), [@euthelup](https://profiles.wordpress.org/euthelup/),
[@prasadkarmalkar](https://profiles.wordpress.org/prasadkarmalkar/), [@justlevine](https://profiles.wordpress.org/justlevine/),
[@ankitkumarshah](https://profiles.wordpress.org/ankitkumarshah/), [@hbhalodia](https://profiles.wordpress.org/hbhalodia/),
[@psykro](https://profiles.wordpress.org/psykro/), [@gziolo](https://profiles.wordpress.org/gziolo/),
[@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/), [@jason_the_adams](https://profiles.wordpress.org/jason_the_adams/),
[@aduth](https://profiles.wordpress.org/aduth/), [@youknowriad](https://profiles.wordpress.org/youknowriad/),
[@whyisjake](https://profiles.wordpress.org/whyisjake/), [@nielash](https://profiles.wordpress.org/nielash/),
[@epeicher](https://profiles.wordpress.org/epeicher/), [@sonaliprajapati](https://profiles.wordpress.org/sonaliprajapati/),
[@pranjal4804](https://profiles.wordpress.org/pranjal4804/), [@juanml](https://profiles.wordpress.org/juanml/),
[@rahultank](https://profiles.wordpress.org/rahultank/), [@obenland](https://profiles.wordpress.org/obenland/),
[@westonruter](https://profiles.wordpress.org/westonruter/), [@philsola](https://profiles.wordpress.org/philsola/),
[@dan2k3k4](https://profiles.wordpress.org/dan2k3k4/), [@milindmore22](https://profiles.wordpress.org/milindmore22/),
[@pravin1996](https://profiles.wordpress.org/pravin1996/), [@makanikaran](https://profiles.wordpress.org/makanikaran/),
[@andraganescu](https://profiles.wordpress.org/andraganescu/), and others involved
in review, testing, translating, and [89 commits across 275 files between 1.3.0 and 1.4.0](https://github.com/WordPress/ai/compare/1.3.0...1.4.0).
Your help and feedback are what make these Features and Experiments possible.

A similar thank you to translators assisting from the [Chinese (Taiwan), Czech, English (UK), Danish, German, German (Formal), ](https://translate.wordpress.org/projects/wp-plugins/ai/)
[Hindi, Japanese](https://github.com/WordPress/ai/pull/1025)[, ](https://translate.wordpress.org/projects/wp-plugins/ai/)
[Korean](https://github.com/WordPress/ai/pull/1025)[, Persian, Polish, Portuguese (Brazil), ](https://translate.wordpress.org/projects/wp-plugins/ai/)
[Russian](https://github.com/WordPress/ai/pull/1025)[, Spanish (Argentina), Spanish (Chile), Spanish (Spain), Turkish, and ](https://translate.wordpress.org/projects/wp-plugins/ai/)
[Vietnamese](https://github.com/WordPress/ai/pull/1025)[ locales](https://translate.wordpress.org/projects/wp-plugins/ai/)
ensuring language packs are available for users. [Translating the AI plugin](https://translate.wordpress.org/projects/wp-plugins/ai/)
is a **_great_** **_contribution_** and others contributing in this manner is very
much welcome and appreciated!

## Get involved

As always, we welcome feedback, testing, and contributions from the community. Whether
you are interested in editor UXUX UX is an acronym for User Experience - the way
the user uses the UI. Think ‘what they are doing’ and less about how they do it.,
APIs, accessibility, performance, or AI ethics and policy, there are many ways to
participate.

You can [explore the 1.4.0 release today](https://wordpress.org/plugins/ai/?preview=1),
review [open issues](https://github.com/WordPress/ai/issues) and [pull requests](https://github.com/WordPress/ai/pulls),
and [help shape what comes next](https://github.com/WordPress/ai/discussions).

_Props to [@laurisaarni](https://profiles.wordpress.org/laurisaarni/) [@ekamran](https://profiles.wordpress.org/ekamran/)
for reviewing this post._

[#ai-experiments](https://make.wordpress.org/ai/tag/ai-experiments/), [#ai-features](https://make.wordpress.org/ai/tag/ai-features/),
[#ai-plugin](https://make.wordpress.org/ai/tag/ai-plugin/), [#ai-release](https://make.wordpress.org/ai/tag/ai-release/),
[#canonical-plugins](https://make.wordpress.org/ai/tag/canonical-plugins/), [#core-ai](https://make.wordpress.org/ai/tag/core-ai/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fai%2F2026%2F10%2F06%2Fwhats-new-in-ai-1-4-0%2F%23respond&locale=en_US)

## Post navigation

[← Older posts](https://make.wordpress.org/ai/page/2/?output_format=md)