WordPress 7.0 is fast approaching, and the WordPress Core AI leadership is seeing its first major transition. Felix Arntz and James have officially announced they are stepping back, with Jason Adams taking the reins as Team Rep. In my 14 years of wrestling with core updates, I’ve learned that leadership shifts usually signal one of two things: burnout or a massive shift in technical direction. Here, it looks like the latter.
We aren’t just talking about a change in titles. This transition happens as the Abilities API (introduced in WordPress 6.9) starts to mature and the “WP AI Client” prepares for its core debut in WordPress 7.0. This isn’t just “shiny object” development; it’s about refactoring how WordPress handles machine-readable functionality.
Why the WordPress Core AI Leadership Shift Matters for Devs
For most of us, “AI” in WordPress has been a chaotic landscape of 500 different plugins all trying to hit the OpenAI API in their own messy ways. The current WordPress Core AI leadership under James and Felix spent the last year building the “Abilities API” to fix this. Specifically, they’ve been creating a standardized registry where any plugin can declare what it can do in a way that an AI agent actually understands.
If you haven’t looked at the source code for the Abilities API yet, you’re missing the boat. It’s not just a wrapper for REST endpoints; it’s a discovery layer. However, I’ve seen enough “Beta” features land in core to know that the implementation phase is where things get breakable. Specifically, managing race conditions when multiple “Abilities” are triggered in a single AI orchestration loop.
You can read more about the earlier phases of this work in my breakdown of WordPress Core AI Development: Leadership & Roadmap Insights.
The Abilities API: A Senior Dev’s Perspective
The “Naive Approach” to AI integration was just sending a prompt and hoping for the best. The “Architect’s Approach” is registering an ability so that WordPress handles the heavy lifting of validation and permissions. Here is a simplified example of how we might register a custom ability using the new framework:
<?php
/**
* Example of registering a custom ability for the Core AI framework.
*/
function bbioon_register_inventory_ability() {
if ( ! function_exists( 'wp_register_ability' ) ) {
return;
}
wp_register_ability( 'bbioon/get-stock-levels', [
'label' => __( 'Check Stock Levels', 'bbioon' ),
'description' => __( 'Returns current stock for a specific SKU.', 'bbioon' ),
'category' => 'ecommerce',
'schema' => [
'input' => [
'type' => 'object',
'properties' => [
'sku' => [ 'type' => 'string' ],
],
'required' => [ 'sku' ],
],
],
'callback' => 'bbioon_handle_stock_query',
'permission_callback' => function() {
return current_user_can( 'manage_options' );
},
] );
}
add_action( 'init', 'bbioon_register_inventory_ability' );
This is where the new WordPress Core AI leadership will be spending most of their time: ensuring that these callbacks don’t become massive performance bottlenecks. When an AI client starts querying twenty registered abilities at once, your server’s transient cache is going to be your best friend or your worst enemy.
Looking Toward WordPress 7.0 and Beyond
With Jason Adams taking the lead, the focus is clearly on the WP AI Client’s move into core. For those of us who have been following the WordPress 7.0 AI Integration plans, we know that security and logging are the biggest hurdles. We need to know exactly *what* an AI agent did to a site, especially when it uses a “Capability” to refactor content or change settings.
I’ve seen plenty of “Canonical” plugins die on the vine, but the MCP Adapter and AI Plugin are different. They are the testing grounds for what eventually becomes stable core code. If you’re building for the AI era, you need to be following the official Make WordPress Core notes on this transition.
Look, if this WordPress Core AI leadership stuff is eating up your dev hours, let me handle it. I’ve been wrestling with WordPress since the 4.x days.
Final Takeaway: Stability Over Shiny
Transitions in the WordPress Core AI leadership are healthy. They bring fresh eyes to complex problems like the Model Context Protocol (MCP) and the Abilities registry. As a dev, your job isn’t to chase every update, but to ensure your sites are ready for the WP 7.0 floor. Start refactoring your custom logic into registered “Abilities” now, or you’ll be playing catch-up when the AI Client lands.
