Fourteen years in this ecosystem and most of the “game-changers” turned out to be overhyped plugins that bloated somebody’s database. The WP AI Client proposal for WordPress 7.0 is infrastructure rather than a feature, which is why I am paying attention to it. I have lost too many hours untangling conflicting AI SDKs in client builds.
The core team published a merge proposal for bringing a provider-agnostic AI API into core. It does not put a “ChatWP” button in the dashboard. What it gives you is a consistent interface, so a developer can call a generative model without knowing whether the site owner runs OpenAI, Anthropic or a local Llama instance.
Why a provider-agnostic API
Today, building an AI feature in WordPress means bundling a large PHP SDK or writing your own wrapper around one vendor’s API. When a second plugin on the same site does the same thing, you get duplicated dependencies and two sets of updates to chase.
The WP AI Client sits in the middle of that. You get one PHP API, a fluent prompt builder, and credential management that is already wired up. It also works with the Abilities API, which showed up in WordPress 6.9 and beyond, for function calling and model discovery.
How the prompt builder works
The implementation uses a fluent builder that returns WP_Error objects instead of throwing exceptions, which follows WordPress convention rather than fighting it. Here is how it would look inside a custom plugin or theme once it lands in core:
<?php
/**
* Example of using the WP AI Client to generate a meta description.
* This assumes a provider (like OpenAI) has been configured via a plugin.
*/
function bbioon_generate_post_summary( $post_id ) {
$post_content = get_the_content( null, false, $post_id );
// Use the core helper function to build a prompt
$response = wp_ai_client_prompt()
->text( "Summarize this content in 150 characters: " . $post_content )
->model_preference( 'gpt-4o' )
->generate();
// The API returns a WP_Error if something fails (auth, network, etc.)
if ( is_wp_error( $response ) ) {
error_log( 'WP AI Client Error: ' . $response->get_error_message() );
return false;
}
return $response->get_text();
}The non-goals
What this proposal doesn’t do is the part that sold me. It ships without API keys, without a default provider, and without a UI assistant forced on site owners. What is left is plumbing, which keeps WordPress plugin-first while still stopping the ecosystem from splitting into incompatible AI tools. Progress is on Trac ticket #64591.
Security and privacy
Enterprise clients ask one question before any other: where does my data go. The WP AI Client makes no outbound calls by default. Access is capability-gated, and secrets live in the WordPress credential system so they do not leak through REST responses or logs. I wrote more about the roadmap in navigating the road to 7.0.
If this WP AI Client stuff is eating your dev hours, I can take it off your hands. I have been wrestling with WordPress since the 4.x days.
Where to start
If you build plugins, read through the GitHub repository for the WP AI Client now. Learning the architecture before the 7.0 merge is cheaper than refactoring a few hundred lines after it.
