WordPress 7.0 is close now, and Beta 1 lands on February 19. I have watched enough core releases strand their experimental features in limbo to stay skeptical, but the WordPress AI Core integration work is moving at a different pace. This week’s contributor meeting was mostly about shipping safely rather than about what might be possible.
The weekly AI Contributor meeting, recently renamed, went through the fallout from the AI Experiments 0.2.0 release. Coordination is tightening up so the Abilities work reaches core without dragging a pile of regressions in with it.
The Abilities API moves toward core post management
The Abilities API is the piece everything else in WordPress AI Core is waiting on. Jorge Costa reported that reviews for the Settings portion are nearly finished. This is the layer that lets an AI do something on your site instead of only talking about it.
The Core Post Management Abilities PR is under heavy review, with the aim of finer control such as per-post-type abilities. That granularity matters. Once you let an LLM touch the database, coarse permissions are how you end up with a race condition or a permissions leak.
I covered the background on this in my earlier take on Integrating the WordPress AI Client for the 7.0 roadmap.
PHP AI Client v0.4.0 and integration testing
Jason Adams confirmed that PHP AI Client v0.4.0 is out, with integration tests next on the list. Recent bug reports made the case for that: with a provider-agnostic SDK, a small change in an OpenAI or Claude response can break a transient or a hook two layers downstream.
<?php
/**
* Conceptual example of a Post Management Ability registration
* in the upcoming WordPress AI Core structure.
*/
function bbioon_register_ai_post_ability() {
if ( ! function_exists( 'register_ai_ability' ) ) {
return;
}
register_ai_ability( 'core/post-management', [
'capability' => 'edit_posts',
'callback' => 'bbioon_handle_ai_post_request',
'args' => [
'post_type' => [
'type' => 'string',
'required' => true,
],
],
] );
}
add_action( 'init', 'bbioon_register_ai_post_ability' );
The MCP Adapter stays outside core
Model Context Protocol (MCP) work is moving along, and the team repeated that the MCP Adapter stays a canonical plugin, separate from the WordPress AI Core client being proposed for core. Review bandwidth is the bottleneck right now. Good code sits in a PR because the handful of people qualified to review it are buried in the 7.0 Beta 1 milestone.
On why MCP is in the picture at all, see my analysis in Why the MCP Adapter Changes Everything.
TypeScript and Data Views in v0.3.0
For v0.3.0 of the AI Experiments plugin, the plan is to refactor the Abilities Explorer to TypeScript, which should sit better with the new Data Views and Forms. The reason is type safety. AI-generated payloads arrive in shapes nobody planned for.
If this WordPress AI Core work is eating your billable hours, I can take it on. I have been working with WordPress since the 4.x days.
What to watch before February 19
February 19, the WordPress 7.0 Beta 1 date, is the real test. The merge proposals for the AI client and Abilities have to land before then or the window closes. Worth watching as well: the WP Bench tests. Ollama Cloud results have been poor next to the hosted providers, but the tool itself is earning its place for benchmarking these core integrations.
