WordPress 7.0’s Native AI Client: What It Is and Why It’s the Bigger Story Behind the Delay

WordPress 7.0 missed its April 9 launch. It was supposed to ship at WordCamp Asia in Mumbai — a big moment for the project after a quiet 2025. Instead, the core team pulled it back at the last minute to fix a critical performance issue in the real-time collaboration feature.

That’s the headline. But it’s not the most interesting part.

The bigger story — the one that will actually affect how WordPress sites get built over the next few years — is the WP AI Client. It’s shipping in 7.0 regardless of the delay, it’s already locked and ready, and it changes something fundamental about how AI works on WordPress.

Here’s what you need to know.

Why WordPress 7.0 Was Delayed

On March 31, WordPress core announced the release cycle needed to be extended to get the Real-Time Collaboration (RTC) database architecture right. Returning to beta status after entering the Release Candidate phase is, as the official post notes, unprecedented.

The technical issue: the current RTC implementation stores sync data via post_meta on a special wp_sync_storage internal post type, but this disables WordPress’s persistent post query caches whenever a user has the editor open. The fix involves a dedicated database table for collaboration data.

Pre-release versions are paused until April 17th. A new schedule will be published no later than April 22nd. Estimates put the actual release around mid-to-late May.

The delay is specifically about real-time collaboration — and only real-time collaboration. Everything else in 7.0 is ready.

What’s NOT Delayed: The WP AI Client

For most WordPress site owners and agencies, the real-time co-editing feature is a nice-to-have. The WP AI Client is a different category entirely.

For the first time ever, WordPress Core ships with a built-in AI Client — not a plugin, not a SaaS bolt-on. A provider-agnostic PHP API baked into Core that lets any plugin talk to any AI model through one unified interface.

This is infrastructure, not a feature. Think of it the way you think about the REST API — it doesn’t do anything visible on its own, but it makes everything else possible.

How the WP AI Client Actually Works

Your Plugin
wp_ai_client_prompt()

Connectors API
Settings › Connectors
API keys stored once

AI Provider
OpenAI · Anthropic · Gemini
OpenRouter · Ollama · Mistral
+ community providers

The entry point is wp_ai_client_prompt(). A plugin calls it, describes what it needs — generate text, analyze content, create an excerpt — and WordPress routes the request to whichever AI provider the site owner has configured.

WordPress Core ships zero AI providers. Instead, providers (OpenAI, Anthropic, Google) are installed as connector plugins via the new Settings › Connectors screen in wp-admin. Site owners add their API keys once, and every AI-powered plugin on the site can use them.

That last sentence is the key change. Before 7.0, every AI plugin handled its own API keys, built its own provider selector, and stored credentials differently. If you used three AI plugins, you managed three separate integrations. After 7.0, configure AI once and every compatible plugin benefits. A workflow can span multiple tools — like retrieving WooCommerce product data and passing it through an AI model to generate descriptions — without custom glue code holding it together.

What It Does and Doesn’t Do

This is worth being clear about, because the coverage has been messy.

WordPress 7.0 ships the infrastructure, not the features. If you want AI-powered content generation, alt text writing, or SEO suggestions, you’ll still need plugins that use the new API. The core team has deliberately kept “what AI does” separate from “how AI connects.”

What ships in core:

• The wp_ai_client_prompt() API for plugins to call
• The Connectors screen for managing provider credentials
• The Abilities API JavaScript layer
• An AI Experiments screen under Settings where users can opt into specific features like auto-alt text and excerpt generation

Feature detection checks don’t make API calls — they use deterministic logic to match the builder’s configuration against available models, so they’re fast to run with no cost. That matters at scale.

The Abilities API: The Part That Changes How Plugins Work

WordPress 6.9 introduced the Abilities API on the PHP side. WordPress 7.0 adds its JavaScript counterpart — two new packages: @wordpress/abilities for pure state management, and @wordpress/core-abilities for the WordPress integration layer, which auto-fetches server-registered abilities via REST. This lays the groundwork for browser agents and WebMCP integration.

In plain terms: plugins can now register specific things they’re capable of doing — “create a post,” “update product metadata,” “generate an excerpt” — and AI agents can discover and execute those capabilities through a standardized interface.

In WordPress 7.0, the MCP Adapter converts these abilities into tools that AI agents like Claude Desktop and Cursor can discover and execute.

This is the infrastructure that makes AI-controlled WordPress possible — not just AI-assisted.

The Playground MCP Server (Already Live)

While 7.0 is delayed, one piece shipped early and it’s worth knowing about.

WordPress Playground now has an official MCP server via the @wp-playground/mcp package. One command wires up Claude Code or Gemini CLI to a browser-based Playground instance, letting your AI agent read and write files, execute PHP, manage sites, and navigate pages — all locally, without touching the WordPress admin.

claude mcp add --transport stdio --scope user wordpress-playground -- npx -y @wp-playground/mcp

For agencies and developers, this means AI-assisted WordPress development in a sandboxed environment today — no waiting for 7.0.

What This Means for WordPress Sites in Practice

WordPress 7.0: Before vs After AI Client

Before 7.0
✗ Each AI plugin manages own API keys
✗ No shared provider credentials
✗ Duplicated settings UX per plugin
✗ No standard for AI capabilities
✗ Can’t chain workflows across plugins

After 7.0
✓ One Connectors screen, all providers
✓ Configure once, works across plugins
✓ Standardized wp_ai_client_prompt()
✓ Abilities API for AI-callable actions
✓ Cross-plugin AI workflows possible

The PHP version requirement is also changing. WordPress 7.0 drops support for PHP 7.2 and 7.3. The new minimum will be PHP 7.4, with PHP 8.2+ recommended. If you’re running sites on older PHP versions, that’s the first thing to check before this drops.

For WooCommerce stores specifically: WooCommerce 10.4.x tested fine against WordPress 7.0 RC. Yoast SEO current release loaded without errors. Most well-maintained plugin stacks should be fine — but always test against a staging environment first on any major release.

What We’re Watching

We’ve been building AI publishing workflows on WordPress for the past year — content pipelines that handle brief intake, draft generation, SEO metadata, and scheduled publishing. The WP AI Client changes the foundation those workflows sit on.

The standardized Connectors layer means the provider routing we’ve been handling manually can move to core infrastructure. Workflows become more portable. Client sites don’t need custom integration code just to route an AI prompt.

The Abilities API and WP AI Client together represent a meaningful step toward a world where WordPress doesn’t just support AI workflows but actively enables them.

The delay doesn’t change any of that. The new schedule drops April 22nd. When 7.0 ships — likely May — the plugin ecosystem will start moving fast. If you’re running a WordPress agency or a content-heavy WooCommerce site, it’s worth understanding this architecture now rather than after the fact.

We’ve been watching this closely for our own WordPress DevOps work and across client builds. If you want to talk through what 7.0 means for your specific stack, we’re around.