I thought I had seen every way a site can white-screen, and then I ran the latest AI Experiments plugin on a WordPress 7.0 dev build. The next major release is in its final stretch, the new WordPress 7.0 AI features are real, and getting to them is currently a minefield if you test early.
What breaks is a namespace collision. WordPress 7.0 bundles its own AI client in core, so an older AI Experiments plugin and core both try to claim the same namespace, and you get a fatal error. @jorgefilipecosta flagged that the current release crashes the moment you activate it on 7.0. That is the sort of debt a project takes on when it moves fast, and it is still a bad day for anyone testing on Beta.
The AI Experiments rebrand and graduation
After feedback from the leadership team, these tools are being sorted into two buckets instead of one: Features that are stable, and Experiments that are still under test. Image Editing is set to be the first feature to graduate inside the plugin. The plugin itself looks likely to be renamed as well, with WordPress AI and AI Labs both on the table, so it reads as a bridge to core rather than a playground.
For anyone running client sites, that graduation matters. It means you can lean on these hooks without expecting them to disappear in a point release. The price is a higher floor: version 0.5 of the plugin drops WordPress 6.9, so you move to 7.0 or you go without the bundled client.
Loading the core AI client without a crash
If you write custom integrations and would rather not reproduce the fatal errors showing up in the experiments plugin, be careful about how your AI logic loads. Check that the core client exists before you initialise a wrapper around it.
<?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
Trac 64706 adds one high level switch that turns off every LLM feature in core. Plenty of site owners are wary of LLM integration on privacy or performance grounds, and until now there was no clean way to refuse all of it at once. If you run an agency and have to promise a compliance heavy client a site with no AI in it, that is the ticket to follow.
API key masking is moving too, in Trac 64819. Raw keys committed into transients or the options table are a familiar sight in code review. The new implementation validates them and masks them in the UI, following the design treatment used on the WordPress 7.0 About page.
MCP adapter and accessibility
The MCP (Model Context Protocol) adapter is at version 0.5.0. It connects WordPress Abilities to outside AI agents such as Claude or Cursor, and the official MCP repository is worth an hour of your reading time. That layer is how AI will eventually reach site content without wrecking it.
Over on the Gutenberg side, the connectors interface still has accessibility problems. @jorgefilipecosta and @raftaar1191 have patches in flight to clear them before the RC1 milestone. Shipping WordPress 7.0 AI features that part of the audience cannot use is not an option.
If WordPress 7.0 AI features are eating your dev hours, hand the work to me. I have been wrestling with WordPress since the 4.x days, and I have seen enough Beta breakage to know where code tends to snap.
Takeaway for developers
Audit your AI code before the official release rather than after it. If you run the Experiments plugin, move to version 0.5 now and the fatal error goes away. There is more detail in my write-up of AI Experiments 0.5.0 and Core AI and in the piece on the WordPress 7.0 AI roadmap.
The transition is messy, and moving the client into core is still the right call. Refactor now, or spend release day chasing namespace collisions.
