WordPress 7.0 “Armstrong” shipped on May 20, 2026, named after the jazz trumpeter Louis Armstrong and built by more than 875 contributors. It carries the first piece of AI infrastructure to live inside WordPress core: the AI Client. Most of the write-ups that followed compressed the release into a single line, “WordPress can now generate content with AI.” That is not what the AI Client does, and the gap between those two readings is worth your time. Let’s walk through it together, starting with what this new core API actually is and what it deliberately is not.
A standard socket, not a content generator
The AI Client is THE standard socket that WordPress core now exposes to plugins. The Make WordPress Core dev note that introduced it describes a “provider-agnostic PHP API that lets plugins send prompts to AI models,” reached through a single entry point, the wp_ai_client_prompt() function, which returns a WP_AI_Client_Prompt_Builder object. The AI Client is a provider-agnostic PHP interface that lives server-side in core, and its only job is to route a plugin’s request to a model.
Read the dev note’s own framing and one line settles the matter: “Your plugin describes what it needs and how it needs it. WordPress handles routing the request to a suitable model from a provider the site owner has configured.” WordPress core itself calls no model and writes no text or images on its own. A plugin or an agent decides when to send a prompt and what to do with the answer. The socket is in the wall. The appliance is still your extension.
Why nothing happens until you configure a provider
The same dev note is blunt about the limits of the feature, telling developers to “never assume that AI features will be available just because WordPress 7.0 is installed.” No provider configured means no model to route to. A fresh WordPress 7.0 install ships the plumbing, not a working AI feature, which is the part the headlines tend to skip. The capability becomes real only once two conditions are met: a plugin that actually calls the AI Client, and a provider connected with valid credentials.
This is the reframe we want you to keep. Upgrading to 7.0 does not turn your site into an AI writer, and it sends nothing to OpenAI, Anthropic or Google by itself. It gives developers one stable way to reach those providers when, and only when, you have chosen to wire one in.
Where the providers get plugged in: the Connectors screen
Wiring a provider in is the job of a second piece that shipped alongside the AI Client: the Connectors API. Registered connectors appear on a new Settings, Connectors admin screen, and the screen renders each connector as a card. From the release announcement, those connections “are easily managed from a single hub in the dashboard,” so the routing the AI Client performs has somewhere to point.
One detail on that screen deserves a careful eye. For an API-key connector, the system looks for the key in a fixed order: an environment variable first, then a PHP constant, then the database. The dev note then states plainly that API keys stored in the database are not encrypted but are masked in the interface, with encryption only explored in a follow-up ticket. If you manage sites where the database may be dumped or shared, set the key in an environment variable or a PHP constant rather than pasting it into the admin form.
How the AI Client differs from the Abilities API
Two core APIs are easy to blur together, so let us separate them. The Abilities API is the older brick, merged into core back in WordPress 6.9 in late 2025; it is how a site declares what it can do in a machine-readable form an agent can read. The AI Client is the 7.0 brick that handles the other side of the conversation, talking to AI providers. One describes capabilities, the other carries requests, and a third-party MCP plugin is yet another thing again. We unpack how these layers stack in our companion piece on the three building blocks that make WordPress agentic.
Our take
The AI Client is a quietly important change, less for what it does today than for giving the whole ecosystem one shared way to reach AI models instead of a dozen incompatible ones. For a daily WordPress practitioner, the news is reassuring rather than dramatic: your core gained a standard interface, not an opinion about your content.
So here is a calm way to act on it. If you run a content site and want AI assistance, wait for a plugin that targets the AI Client, then connect a single provider and test it in staging before production. If you maintain client sites, audit which plugins call the AI Client and check where each key is stored before you enable any provider. And if you have not upgraded yet, treat AI as one line item among many, not the reason to rush; our cautious checklist for upgrading to WordPress 7.0 walks through the rest. The socket is in the wall now, on millions of sites. What you plug into it, and whether you plug in anything at all, stays your call.
