WordPress 7.0 is right around the corner, and the AI Experiments 0.5.0 release just dropped a major hint about how the core ecosystem is shifting. If you have been following the “WP AI Client” development, you know it started as a standalone Composer package. Consequently, that’s changing; it is now being baked directly into WordPress core.
I have spent years managing dependency bloat in enterprise WooCommerce sites, so seeing a “canonical” plugin shed its dependencies in favor of native core functions is always a win. However, this move comes with a steep price for those on legacy stacks. Specifically, this version now requires WordPress 7.0 as a minimum. If you are still on 6.9, you are officially locked out of the newest experiments until April 9th.
The Core Refactor: WP AI Client Goes Native
In previous iterations, the AI Experiments plugin had to bundle its own AI client infrastructure. This often led to version conflicts if other plugins tried to load different versions of the same library. Therefore, the decision to bundle the WP AI Client into WordPress 7.0 core solves a massive architectural bottleneck.
By relying on the core infrastructure, AI Experiments 0.5.0 ensures that any experiment you run is using the exact same API that core features will eventually use. This is crucial for stability. I have seen too many “experimental” features die because they diverged too far from the core roadmap. Furthermore, this update aligns perfectly with the WP AI Client ecosystem changes we have been tracking.
Credential Migration and the Connectors Screen
One of the most practical changes in this release is the migration of credentials. Previously, you would store your API keys within the plugin’s specific settings. Now, those are being moved to the centralized Connectors screen. This is located under Tools -> Connectors in WordPress 7.0.
This centralized management is a relief for developers. Instead of hunting for where a specific OpenAI or Anthropic key is stored, WordPress now handles the provider registry via the Connectors API. If you are building custom AI features, you should stop hardcoding keys or using custom option fields and start using these core connectors.
<?php
/**
* Simple check to see if the new Core AI infrastructure is available
* before running an experiment.
*/
function bbioon_check_ai_capability() {
if ( function_exists( 'wp_ai_client_prompt' ) ) {
// We are on WP 7.0+ with core AI support
return true;
}
return false;
}
?>What is on the Horizon for 0.6.0?
The roadmap for the next version is even more ambitious. We are looking at image editing experiments (erase, replace, and background removal) and “Contextual Tagging,” which will suggest taxonomies based on your content. This is a significant leap toward a more interactive editor experience. Most importantly, the plugin will likely be renamed from “AI Experiments” to simply “WordPress AI.”
Look, if this AI Experiments 0.5.0 stuff is eating up your dev hours, let me handle it. I’ve been wrestling with WordPress since the 4.x days.
The Senior Dev’s Takeaway
Don’t upgrade your production sites to AI Experiments 0.5.0 unless you are already running the WordPress 7.0 beta or RC. The breaking change in minimum version support is real. However, if you are a developer, you need to start testing these connectors now. The shift from “Plugin-land” to “Core-land” for AI functionality is the biggest architectural change we’ve seen in years. Ship it, but ship it carefully.
” queries:null},excerpt:{raw:
