The WordPress 7.1 AI Client: What Actually Ships on August 19

The WordPress 7.1 AI Client has been described everywhere as the release that brings streaming and embeddings to WordPress. The release lands August 19, timed to WordCamp US. If you are a plugin developer planning against those two capabilities, the schedule matters less than a detail almost nobody has checked: where the code actually is.

The short version is that the AI Client is real, it has been in core since 7.0, and the two headline additions live one layer below WordPress in a standalone PHP library. That distinction is not pedantry. It determines whether you can call these APIs from a plugin on August 19 or whether you are waiting on a separate release cycle.

What the WordPress 7.1 AI Client actually is

It is two layers, and both ship in core rather than as a feature plugin.

The lower layer is wordpress/php-ai-client, a standalone PHP SDK that is deliberately not coupled to WordPress. Core vendors it into wp-includes/php-ai-client/ and namespaces it with PHP-Scoper so it cannot collide with a plugin shipping its own copy.

The upper layer is the WordPress wrapper at wp-includes/ai-client.php, loaded during wp-settings.php. It gives you wp_ai_client_prompt(), which returns a prompt builder, plus wp_supports_ai() and the WP_AI_SUPPORT constant for capability checks. Two filters are available: wp_supports_ai and wp_ai_client_prevent_prompt. The builder’s using_abilities() method is the bridge to the Abilities API, which is how a prompt gets access to registered WordPress capabilities rather than raw model output.

Everything in that list carries an @since 7.0.0 tag. The WordPress 7.1 AI Client is not new in 7.1. It is the 7.0 client with a newer copy of a library bundled underneath it.

Core bundles no providers. Anthropic, Google and OpenAI each ship an official plugin, configured under Settings then Connectors, which is the surface we covered in our look at WordPress 7.0’s AI foundations and Connectors.

Where streaming and embeddings actually are

Both are pull requests against the PHP AI Client repository, not against WordPress core. Their status differs, and the difference matters.

Embeddings merged, and shipped. Pull request 244 adds Embedding and EmbeddingResult classes and a separate EmbeddingBuilder, reached through AiClient::input(), carrying withInput(), usingDimensions(), isSupported(), generateEmbedding(), generateEmbeddings() and generateEmbeddingResult(). Note that these are not methods on the prompt builder. It merged on July 15, 2026, and the library tagged 1.4.0 and published it to Packagist the same day, at 01:43 UTC.

Streaming has not. Pull request 255 adds StreamingTextGenerationModelInterface, an SSE event stream parser, StreamedGenerativeAiResult, GenerativeAiResultChunk and streamGenerateText() on both the client and the builder. As of this writing it is still open, with its most recent commit on July 16, 2026.

Now the part that decides what you can call in August. The library’s most recent published release on Packagist is 1.4.0, dated July 15, 2026, and it contains the embeddings work. So this is not a case of code stranded on an untagged trunk that core could not reasonably consume. A tagged, installable release has existed for thirty-five days, and WordPress 7.1 still vendors a copy from before it. Check the bundle the right way, because the obvious test gives a false negative. Grepping the prompt builder for generateEmbedding returns nothing even in the shipped 1.4.0, since embeddings never lived there. The test that actually works is whether src/Builders/EmbeddingBuilder.php is present in wp-includes/php-ai-client/. In WordPress trunk at Beta 4 it is absent, and so is AiClient::input(). What is present is the pre-existing isSupportedForEmbeddingGeneration() capability check, which tells you whether a provider could do embeddings, not how to ask for them.

So at the time of writing, neither capability is in the version of the library that WordPress 7.1 carries.

The framing is the story, and it is stated plainly

This is not a case of a project overpromising. WordPress said what it was doing, in public, in June.

Jason Adams wrote the AI team’s preview of the 7.1 AI Client work on June 19. Two sentences from it do more work than any roundup. On the absence of visible features: "There’s still no visible AI within the default WordPress interface and this is because the present focus is on empowering the ecosystem of plugin authors."

And on streaming specifically: "we’re starting by introducing streaming to the PHP AI Client, the underlying framework which powers the AI Client but isn’t coupled to WordPress. This means streaming will be available within WP 7.1, but not as something naturally supported by WordPress."

That second sentence is the whole post in miniature. Streaming arriving in the bundled library is a different claim from streaming being a WordPress API, and the AI team drew the line themselves. The official call for testing, published July 15, lists no AI features at all.

The three core abilities moved to 7.2

The other piece of 7.1 AI news was a merge proposal, and it did not land.

Jorge Costa published Expanding WordPress Core Abilities on July 2, proposing three read-only abilities: core/read-settings, core/read-content and core/read-users. These would have given any agent connecting through the Abilities API a standard, permission-checked way to read a site without a plugin author writing the plumbing.

The settings ticket was previously committed during the 7.0 cycle and then reverted in February, and now sits against the 7.2 milestone. The users ticket was moved from 7.1 to 7.2 on July 14, with the stated reason being feedback on the merge proposal, plus a naming collision with an existing ability. The objection on record came from the Abilities API component maintainer, arguing the abilities were undertested and should run a full cycle in the AI plugin before entering core.

Be careful with one widely repeated claim here. Coverage from late July reports core/read-content and core/read-users as added. Those landed in the AI plugin, not in core. It is the same distinction as streaming: the capability exists somewhere in the WordPress orbit without existing in WordPress.

What the WordPress 7.1 AI Client means if you build plugins

The practical read is better than the headline suggests, because a stable primitive you can rely on beats a feature that shifts under you.

If you are building AI features today, the prompt builder, provider abstraction and abilities bridge from 7.0 are all available and unchanged. That is a real foundation, and the reason the AI team’s framing is defensible: a plugin author who writes against wp_ai_client_prompt() does not need to care which provider the site owner configured.

If your roadmap depends on embeddings, you have two paths. You can require the PHP AI Client directly as a Composer dependency at 1.4.0 or later and accept that you are shipping a second copy alongside core’s, or you can wait for a core release that bumps the bundled library. Semantic search over your own content is exactly the case where embeddings earn their keep, and our explainer on vector databases covers what you do with them once you have them.

If your roadmap depends on streaming, the pull request is open and unmerged. Plan for a later cycle.

What a site operator should do before August 19

Very little, which is the honest answer.

Test 7.1 on staging using the beta channel, but test it for the changes that affect every site rather than for AI. The persistent toolbar work and the React 19 upgrade touch far more installations than any of this does. Confirm 7.0.2 is applied, since it was a security release covering one critical and one high severity issue.

Nothing in 7.1 changes AI configuration for a normal site. There is no new interface, and no new outbound network calls unless a provider plugin is installed and configured. If you do configure one, the credential handling is the part to think about, and our coverage of encryption at rest for the Connectors API is the relevant reading. The governance question of what an agent may actually do once connected is the one we worked through across platforms in CMS agent permissions, and the Abilities API explainer covers the registration layer underneath all of it.

Watch for the Field Guide, which usually appears close to RC and is the single most reliable summary of what actually landed. It will also be the first document to state the WordPress 7.1 AI Client’s final shape without a marketing filter.

Frequently Asked Questions