WordPress 7.0 “Armstrong” shipped in May 2026, and its biggest change is plumbing: an AI Client, a Connectors API, and a Connectors screen, all in core. My reaction after working through the docs is mostly relief, because WordPress standardized the boring part (providers and API keys) instead of shipping a chatbot and calling it a release.
The announcement on the WordPress.com blog covers the whole release: visual revisions, the refreshed dashboard, navigation overlays, the new Breadcrumbs and Icon blocks. It’s worth the read. I want to stay on the AI layer, because that’s the part that changes how plugins and client sites get built. The official release post is on WordPress.org if you want the core version of the story.
I wrote about the AI client while 7.0 was still in beta, so this is the “it actually shipped” pass.
7.0 sends nothing to a provider unless you enable it
The announcement says it directly: the AI features are optional and have to be enabled by the site owner, and nothing is shared automatically when you install 7.0. The AI Client is a library. Core ships no model and no key. You install a provider plugin for Claude, ChatGPT or Gemini from the Connectors screen and enter the key there.
That one screen is the practical win when you maintain sites for other people. If a client asks whether AI is running, the answer is a look at Settings > Connectors instead of a tour through five plugin settings tabs. If they want nothing to do with it, remove the connector and it’s off. I’ve spent enough hours hunting API keys across plugin pages to appreciate one place that holds them. (I haven’t tested how connector keys behave on multisite yet, so check before promising anything there.)
What can you build on the WordPress 7.0 AI client?
Every call starts with wp_ai_client_prompt(), which returns a WP_AI_Client_Prompt_Builder you configure and then run. The Make WordPress dev note lists the full builder API, and the developer blog walkthrough shows a complete plugin. The part most people will forget is the version guard:
<?php
if ( ! function_exists( 'wp_ai_client_prompt' ) ) {
return new WP_Error(
'bbioon_ai_unavailable',
'This feature needs WordPress 7.0 with a provider connector.'
);
}
$builder = wp_ai_client_prompt();
// Configure the prompt, then call a generation method.
// Returns WP_Error on a missing key, a rate limit, or a provider outage.The client is provider independent. Your feature asks for a completion, and core resolves the provider, the credentials, retries and transport. Swap Anthropic for OpenAI and your code does not change, because the key lives in core rather than in your plugin. On a WooCommerce store, the obvious first uses are drafting product short descriptions and alt text, which is roughly what the optional AI plugin shows as a reference implementation.
Next to the client sits the Abilities API, a standard way to register a unit of functionality so that REST, the block editor, or an AI agent can discover and run it. Register sparingly at first. An agent can call anything it can discover, so that surface deserves the same review you would give a public REST endpoint.
If you’re deciding whether to rebuild an existing AI integration on the client, or wire one up for a store for the first time, that’s work I take on. Choosing the architecture now costs far less than unpicking a hardcoded provider next year.
Updating client sites to 7.0
Yes, update them. The 7.0 branch has already had security releases; 7.0.2 addressed one critical and one high severity issue, and WordPress.org forced the update for affected versions. Sitting on 6.9 buys you nothing. Copy the site to staging and update there first.
What tends to break on a release like this: plugins that style the admin, since 7.0 brings a new default color scheme, refreshed buttons and a Command Palette shortcut in the admin bar; anything with its own API-key page that now overlaps Connectors; and themes doing custom navigation, since overlays got their own editing canvas. One commenter on the announcement reported the editor breaking after updating, and the staff reply pointed at plugin conflicts, which is where the fault usually is on majors. The quieter items help more than they get credit for. Visual revisions, responsive block visibility and block-level CSS remove hacks people were shipping anyway, and the Font Library now working in classic themes kills a small category of plugin work.
If you look after a lot of sites, automating WordPress updates is worth setting up, so the 7.0.x point releases land without someone clicking through each dashboard.
Where to start today
Take one site, copy it to staging, and run wp core update followed by wp plugin update –all. Then open Settings > Connectors, install one provider plugin with a throwaway key, and see what shows up. Twenty minutes tells you whether your plugin stack already registered connectors, whether any settings pages collide, and whether the AI story for that client just got simpler.
