WordPress 7.0 Beta 2 is on the development stream. The testing label puts some people off, which is a mistake if you ship plugins, because this is the release where the core team settles how AI integrations and block architecture are going to sit together. The headline piece is a central WordPress 7.0 Beta 2 Connectors UI, and it changes how third-party services get registered.
How AI connectors work in WordPress 7.0 Beta 2
Every AI plugin used to arrive with its own settings page, each one arranged differently. Under Settings > Connectors there is now a single dashboard for all of them, built as a route-based interface on @wordpress/components. The part that matters to plugin authors is the new connections-wp-admin-init hook, which is where an external provider gets registered.
I have spent 14 years watching WordPress try to standardize one API after another. If your plugin talks to OpenAI, Anthropic, or a local LLM, move the connection logic onto these registration APIs now. Skip it and you are shipping technical debt before the version is even out. I went into more detail on the reality of AI progress in Beta 2 here.
<?php
/**
* Example: Registering a custom AI provider connector.
* This should be hooked into the new 'connections-wp-admin-init'.
*/
function bbioon_register_custom_connector() {
if ( ! function_exists( 'register_connector_provider' ) ) {
return;
}
register_connector_provider( 'bbioon-custom-ai', array(
'label' => __( 'Bbioon AI Provider', 'textdomain' ),
'description' => __( 'Custom endpoint for local inference.', 'textdomain' ),
'icon' => 'admin-generic',
'route' => '/bbioon/v1/connect',
) );
}
add_action( 'connections-wp-admin-init', 'bbioon_register_custom_connector' );Block API version 3 and the iframed editor
The other thing to watch in WordPress 7.0 Beta 2 is strict enforcement of the iframed editor. Blocks on Block API version 3 now load inside an iframe so their styles stay encapsulated. That keeps a theme’s leaky CSS out of the editor, and it breaks any block that reaches into the parent window’s DOM.
I have watched dozens of custom blocks break on exactly that assumption of a global window scope, which is now restricted. Update block.json and register your styles through editorStyle. My longer write-up on how the iframed editor affects your blocks has the full fix.
{
"apiVersion": 3,
"name": "bbioon/custom-block",
"title": "Encapsulated Block",
"editorStyle": "file:./editor.css",
"style": "file:./style.css"
}How to test Beta 2 without losing a site
Please, for the love of your database, do not run this on production. Use a staging environment or the WordPress Playground. If you prefer the terminal, WP-CLI is the most efficient way to spin up the update without clicking through the UI.
# Update to Beta 2 using WP-CLI
wp core update --version=7.0-beta2Beta 2 carries over 70 fixes since the first beta, a good number of them regressions from the Gutenberg 22.6 cycle. The final release is still set for April 9, 2026, and that date holds only if the edge cases surface now.
If WordPress 7.0 Beta 2 testing is eating your dev hours, I can take it on. I have been building on WordPress since the 4.x days.
What to do before April
A Connectors API plus enforced Block API v3 is WordPress behaving like a platform for professional applications. Do the refactor now and release day in April stays quiet. Leave it and you spend that day firefighting instead. The Make Core blog is where the rest of the changes will show up as this moves toward the release candidate.
