I honestly thought I’d seen every way a site could white-screen until I tried running the latest AI Experiments plugin on a WordPress 7.0 dev build last week. We are in the final stretch for the next major release, and while the new WordPress 7.0 AI features promise a lot, the transition is proving to be a bit of a minefield for early adopters and developers.
The core issue is a classic race condition mixed with architectural shifting. WordPress 7.0 is bundling its own AI client directly into core. If you are running an older version of the AI Experiments plugin, you’re going to hit a fatal error because both core and the plugin are trying to claim the same namespace. Specifically, @jorgefilipecosta flagged that the current release crashes immediately upon activation on 7.0. It’s the kind of technical debt we expected when moving fast, but it’s a headache for site owners testing on Beta.
The AI Experiments Rebrand & Graduation
Following feedback from the leadership team, there is a significant shift in how we categorize these tools. We are moving away from everything being an “Experiment.” Instead, the team is identifying “Features” (stable) versus “Experiments” (testing). Image Editing is slated to be the first “graduated” feature within the plugin. Consequently, the plugin itself is likely getting a rebrand—suggestions like WordPress AI or AI Labs are on the table to make it feel less like a playground and more like a bridge to core.
For those of us managing client sites, this graduation is critical. It means we can finally start relying on these hooks without worrying they’ll vanish in a minor point release. However, this shift requires a bump in the minimum supported version. Version 0.5 of the plugin will officially drop support for WordPress 6.9, forcing a move to 7.0 to leverage the bundled client.
Technical Fixes: Handling the Core AI Client
If you’re writing custom integrations and want to avoid the fatal errors we’re seeing in the experiments plugin, you need to be technically precise about how you load your AI-related logic. Specifically, you should be checking for the existence of the core client before attempting to initialize your own wrappers.
<?php
/**
* Bad Approach: Assuming the plugin client is always there.
* This causes a fatal error in WordPress 7.0.
*/
function bbioon_legacy_ai_init() {
$client = new \WP_AI_Experiments\Client(); // CRASH on 7.0
}
/**
* Senior Dev Approach: Check Core first.
*/
function bbioon_safe_ai_init() {
if ( class_exists( 'WP_AI_Client' ) ) {
// Use the new WordPress 7.0 AI features core client
return \WP_AI_Client::get_instance();
}
// Fallback or Bail
return false;
}The Core LLM Kill Switch
One of the most important updates in Trac 64706 is the introduction of a high-level “Kill Switch.” Some site owners are rightfully hesitant about LLM integration due to privacy or performance bottlenecks. The team has introduced a single switch to disable all LLM-related functionality in core. This is a massive win for agency owners who need to guarantee a “no-AI” environment for specific compliance-heavy clients.
Furthermore, progress is being made on API key masking (Trac 64819). We’ve all seen developers accidentally commit raw keys to transients or the options table. The new implementation ensures these are validated and masked in the UI, following the design treatment of the WordPress 7.0 “About” page.
MCP Adapter and Accessibility
The MCP (Model Context Protocol) adapter has reached version 0.5.0. This bridges the gap between WordPress “Abilities” and external AI agents like Claude or Cursor. If you haven’t looked at the official MCP repository, you’re falling behind. It’s how we’ll eventually allow AI to interact with site content safely.
On the Gutenberg side, there are still some lingering accessibility issues in the connectors interface. @jorgefilipecosta and @raftaar1191 are pushing patches to ensure these are resolved before the RC1 milestone. We can’t ship WordPress 7.0 AI features if they aren’t usable by everyone.
Look, if this WordPress 7.0 AI features stuff is eating up your dev hours, let me handle it. I’ve been wrestling with WordPress since the 4.x days, and I’ve seen enough “Beta” breaks to know how to future-proof your code.
Takeaway for Developers
Don’t wait for the official release to audit your AI implementations. If you are using the Experiments plugin, update to version 0.5 immediately to avoid the fatal errors mentioned. For more on what’s changing, check out my deep dive on AI Experiments 0.5.0 and Core AI or read about the upcoming WordPress 7.0 AI roadmap.
The transition is messy, but the architectural move to a core client is the right one. Refactor now, or spend your release day debugging race conditions.
