The WordPress AI plugin 1.0.0 just hit the repository, and the docs make it look like a routine milestone. Read the source and the new experiments, though, and you can see the direction change. AI in WordPress is leaving the “cool demo” phase and turning into infrastructure. If you build enterprise sites, the WordPress AI Plugin Features in this version are mostly about governance.
I’ve spent about fifteen years watching “canonical” plugins try to set the standard for how we build in WordPress. They usually start messy. This one hasn’t. Since the Building Blocks initiative started in 2025, the team has been refining a reference implementation that manages AI instead of just calling it. If you’re a developer, look closely at how they handle provider abstraction.
Request logging: why you want it on
The biggest of the new WordPress AI Plugin Features in 1.0.0 is the Request Logging experiment. On a typical client site you might have three plugins hitting OpenAI or Anthropic APIs. Without logging you have no idea which feature is burning through tokens, or why a request came back with a 429.
The logging screen shows administrators the full request and response for each call. That helps when a single post save fires several AI operations at once and they trip over each other. It also leaves a paper trail you can use for performance audits. I’d turn it on in staging right away and watch what your active plugins are actually doing.
If you want the bigger picture, I wrote about the WordPress 7.0 AI Integration plans, and these features are obviously groundwork for them.
Governance through connector approvals
Until now, plugin access to AI was a free-for-all. The Connector Approvals experiment lets site owners decide which plugins can use the global AI connectors. That’s a big security improvement. Before, any plugin could quietly use an API key you had configured for something else. Now there’s an approval step.
So if you’re building a custom plugin that uses the core AI infrastructure, make sure it copes with the unauthorized state instead of breaking. Here’s a quick way to check for a configured, authorized provider before running anything expensive:
<?php
/**
* Example: Checking for an authorized AI connector
* Prefix: bbioon_
*/
function bbioon_check_ai_readiness() {
// Ensure the AI building blocks are active
if ( ! function_exists( 'wp_ai_get_provider' ) ) {
return false;
}
// Attempt to get the default text provider
$provider = wp_ai_get_provider( 'text-generation' );
// Check if the provider is both configured and authorized for this context
if ( is_wp_error( $provider ) || ! $provider->is_authorized() ) {
return false;
}
return true;
}
Renamed workflows and newsroom terminology
WordPress is dropping some of the engineer-flavored labels. “Review Notes” is now “Editorial Notes,” and “Refine from Notes” is now “Editorial Updates.” Small change, but it matches how real newsrooms talk. The Comment Moderation experiment can also sort by Toxicity and Sentiment now, which helps a lot on busy sites where manual moderation is the bottleneck.
Sentiment analysis is only as good as the provider behind it, though. Run moderation on a cheap model and you’ll get false positives. That’s why the new “failed-analysis” indicators matter: they tell you when your provider timed out during a toxicity check.
The road to 1.1.0: C2PA and provenance
Next up, the plugin is starting to experiment with C2PA (Content Credentials). The idea is content provenance: proving what was AI-generated and what wasn’t. It’s ambitious, and it will need deep integration with Gutenberg’s media editor. You can follow progress on the official GitHub repository.
If the WordPress AI plugin work is eating your dev hours, I can take it off your plate. I’ve been working with WordPress since the 4.x days.
What developers should do now
- Enable Request Logging: Find out where your API tokens are actually going.
- Respect Connector Approvals: Update custom integrations to check the authorization state.
- Watch C2PA: Content authenticity looks likely to become a legal requirement in a lot of industries, and the groundwork is going in now.
For how this ties into the core roadmap, see my post on WordPress Core AI Leadership and where things are heading.
