We need to talk about WordPress Core AI development. The standard advice has somehow become “install an AI plugin” and hope for the best, and the result is a pile of unstandardized wrappers. Recent announcements from the Core AI team suggest we’re finally moving toward a shared infrastructure.
Leadership is changing: Felix Arntz and James LePage are stepping back, and Jason Adams is taking the lead. The Abilities API landed in WordPress 6.9, and the WP AI Client is scheduled for core in 7.0. The point is less about “adding AI” and more about standardizing how automated agents discover and call WordPress functions.
Why the roadmap for WordPress Core AI development matters
In the early days of WordPress Core AI development, everyone built their own isolated solution. Developers ended up juggling multiple API keys and conflicting prompt templates, with no security logging at all. And with no central registry, AI agents couldn’t reliably work with core WordPress functions.
The Abilities API fixes this with a central registry. Instead of a plugin calling a function directly, it registers that function as an “Ability,” which makes it discoverable to AI assistants like Claude or ChatGPT through the MCP Adapter. For the bigger picture, see my thoughts on WordPress 7.0 and Core AI integration.
Registering an ability properly
A common mistake is wrapping your logic in a plain callback without defining the schema. That fails because the AI client has no idea which parameters to send. Use the Abilities API (or the current AI Plugin filters) to register capabilities formally instead.
<?php
/**
* Register a custom ability for bbioon product search.
*/
function bbioon_register_product_search_ability() {
if ( ! function_exists( 'register_wp_ability' ) ) {
return;
}
register_wp_ability(
'bbioon/product-search',
array(
'description' => 'Searches for WooCommerce products by keyword and price range.',
'callback' => 'bbioon_ai_product_search_callback',
'parameters' => array(
'keyword' => array( 'type' => 'string' ),
'max_price' => array( 'type' => 'number' ),
),
)
);
}
add_action( 'init', 'bbioon_register_product_search_ability' );
This way the model knows exactly what data it can request. Skip the structure and you’re inviting race conditions and hallucinations into your backend.
Stability over shiny tools
I’ve seen too many sites break because a developer hacked in a third-party AI library. So I’m glad the WP AI Client is going into core. It gives WordPress Core AI development a stable bridge we can rely on for enterprise sites. For release plans, read about WordPress 7.0 AI security and logging.
If WordPress Core AI development work is eating your dev hours, I can take it on. I’ve been working with WordPress since the 4.x days.
Where this leaves you
Handing leadership from the founding members to a consolidated Team Rep is a sign the project is maturing. WordPress wants to be the operating system for AI-driven sites, and these core APIs are what that plan rests on. Don’t ignore them. Start refactoring your AI wrappers into registered Abilities now.
