WordPress 7.0 is right around the corner, and the big question on everyone’s mind—at least if you’re following the WordPress AI Client development—is whether it’s actually going to ship in core or stay in the plugin repository. As a developer who has seen countless “game-changing” features merged into core only to be refactored three releases later, I’m watching this one closely. We aren’t just talking about a few new blocks; we’re talking about a foundational API that will dictate how every plugin on the repo interacts with Large Language Models (LLMs).
Credential Management and the “Connectors” Vision
One of the most interesting pivots from the recent AI Contributor meeting is the shift toward a unified “Connectors” screen. Originally, the focus was solely on how the WordPress AI Client would handle API keys. However, leadership—including Matt Mullenweg—seems to be pushing for a more global approach. Instead of having fragmented settings for Google Maps, Mailchimp, and OpenAI scattered across the admin, the idea is to have a centralized location for external service credentials.
From an architectural standpoint, this makes total sense. We’ve all dealt with the nightmare of managing transients or option fields for different API keys. A unified interface would clean up the database and the UI. But there’s a catch: complexity. With the Beta 1 deadline looming, trying to build a robust, secure, and extensible credential system is a tall order. If we rush it, we end up with technical debt. If we wait, the WordPress AI Client might get pushed to version 7.1.
Abilities: The Move to Nested Namespaces
There was a significant technical consensus reached regarding “Abilities”—the tools that the AI can actually call to perform tasks. The team decided to support nested namespaces (e.g., core/settings/get instead of a flat get_settings). If you’ve spent any time working with the WordPress REST API, this will feel very familiar. It’s about organization and progressive disclosure. Furthermore, it allows the ecosystem to scale to thousands of abilities without name collisions.
Specifically, look at how this refactoring looks in practice. We are moving away from simple function-like strings to a structured hierarchy. Consequently, existing single-level abilities will likely need to be updated to follow this new convention.
// The "Naive" flat approach (Old)
bbioon_register_ability( 'get_post_meta', $callback );
// The "Senior" nested approach (New standard)
bbioon_register_ability( 'core/post/get-meta', [
'callback' => $callback,
'description' => 'Retrieves metadata for a specific post ID.',
'args' => [
'post_id' => [ 'type' => 'integer', 'required' => true ],
],
] );I’ve written a deeper dive into why standardizing these APIs is vital for performance in my post on WP AI Client Standardizing Generative AI.
Experiments and the MCP Protocol
While the core merge debate continues, the “AI Experiments” plugin is moving fast. Version 0.3.1 just dropped with fixes for image generation. One thing that has me excited is the progress on the Model Context Protocol (MCP). Standardizing how we provide context to LLMs is the only way to avoid the “hallucination” bottlenecks we currently face in complex WordPress environments. Therefore, seeing active community PRs for MCP support is a massive win for those of us building production-ready AI tools.
For more technical details, I highly recommend checking out the official merge proposal on Make WordPress and the GitHub release notes.
Look, if this WordPress AI Client stuff is eating up your dev hours, let me handle it. I’ve been wrestling with WordPress since the 4.x days.
The Final Takeaway
The WordPress AI Client is evolving from a cool experiment into serious developer infrastructure. Whether it lands in 7.0 or 7.1 is almost secondary to the fact that we are finally getting a standard way to handle AI in the WordPress ecosystem. If you are a plugin developer, now is the time to audit your settings and start thinking about how your features can be exposed as “Abilities.” The “under-the-hood” experience is about to get a lot more interesting.
