WordPress AI contributors have set a core-first workflow for abilities planned for WordPress 7.3. The approach puts development and review in WordPress Core, with shared-package synchronization after merge. The team also discussed experimental abilities and proposed tests against AI providers, but these are plans under development, not shipped features.
That’s the main takeaway from the November 18 meeting, reported in the AI team’s November 19 summary. Contributors can review the proposed minimum set of WordPress 7.3 AI abilities and their input and output schemas, or follow the work on provider testing. ([make.wordpress.org](https://make.wordpress.org/ai/2026/11/19/ai-contributor-weekly-summary-18-november-2026/))
What the WordPress 7.3 AI abilities workflow changes
The team agreed that WordPress Core should be the source of truth for abilities targeted at WordPress 7.3. Under the proposed workflow, contributors will develop and review those abilities in Core, then synchronize them with the shared WordPress Abilities package after they merge.
This is a development-process decision, not an announcement that a new ability set has landed. The meeting summary says contributors are still discussing a proposed minimum set, including the structure of each ability’s inputs and outputs. WordPress 7.3 work is the target, and the summary asks contributors to provide feedback before implementation moves further.
For agencies and plugin developers, the distinction matters: an ability targeted for Core is meant to follow the Core-first route, while an experimental ability that is not yet targeted for Core can be developed and tested in the package. The team also wants shared abilities to use matching implementations in both places, so tests and feedback apply to the code intended for WordPress.
Why the team wants Core to be the source of truth
The summary says the workflow aims to reduce duplicated development and synchronization problems previously encountered when moving functionality from the AI plugin into Core. That is a practical concern: maintaining parallel versions creates extra work for contributors and makes it harder to tell whether feedback applies to the implementation that will ultimately ship.
The package still has a role. It can distribute abilities to projects such as the MCP Adapter, and it remains the place for experimenting with abilities that are not yet planned for Core. Contributors said exceptions may make sense when package testing needs to happen earlier, but the default for WordPress 7.3 functionality is core-first.
The meeting also addressed how contributors will track work. The team discussed keeping a central list of planned abilities and their status in the repository README, linking Core tickets and pull requests to tracking issues, and keeping the package synchronized with Core changes after they are committed.
Provider testing is still being developed
Another item in the November 18 update is proposed testing infrastructure for checking whether registered abilities work with AI providers. The team discussed tests involving three major providers; the summary names Gemini and Anthropic among them and says the goal is to catch compatibility issues earlier in development.
These provider-specific tests would run only when the relevant API keys are available. That avoids automatically using API credits during continuous integration. The summary describes work that contributors will continue developing and reviewing, so site owners should not treat it as an available testing feature yet.
There is also a review question here for developers: ability schemas need to be consistent and usable, and provider compatibility needs to be tested without making routine checks unexpectedly consume credits. The update does not specify a release date for the testing setup or say that the proposed abilities are already complete.
What contributors can do now
The clearest next step is to review the proposed minimum set of WordPress 7.3 abilities, with particular attention to the input and output schemas. The team has invited suggestions and pull requests. Contributors can also watch the abilities repository for its planned status list and links to related Core tickets and pull requests.
For site owners, this update is a progress report, not a prompt to install or change anything. The useful signal is that WordPress’s AI team is setting a process for getting selected abilities into Core while keeping room for package-based experiments. The meeting summary lists AI Team office hours for Thursday, November 26, 2026, at 17:00 UTC.
FAQ
What are WordPress abilities?
In this update, abilities are units of functionality being developed for WordPress and AI-related projects. The team is defining a proposed minimum set for WordPress 7.3, including each ability’s input and output schemas.
Will the abilities be available in WordPress 7.3?
The update describes abilities targeted for WordPress 7.3, but it does not announce that they are finished or guaranteed for the release. The team is still seeking feedback on the proposed set before implementation progresses further.
How can developers contribute?
Review the proposed schemas and send feedback or a pull request, as the AI team requested. Developers can also track Core tickets, pull requests, and package work through the repository’s planned tracking links.
Next step: Review the proposed WordPress 7.3 ability schemas in the AI team’s update and share feedback before implementation advances.