WordPress 7.0 APIs were the main topic in the latest Dev Chat, and anyone reading the commit logs could see this is bigger than the usual point release. The 7.0 cycle has been extended for architectural stability, and the AI Client and Connectors API are the largest change to core logic since the REST API landed. After a decade of refactoring other people’s legacy code, a delay like this reads to me as an architectural breather core has earned.
The 7.0 delay and the WordPress 7.0 APIs
The core team, with @audrasjb facilitating, confirmed the 7.0 cycle is being extended. The release party moves to WordCamp Asia’s Contributor Day in Mumbai. I have seen enough race-to-the-finish releases break checkout flows to think a longer cycle is usually the right call. This release lands a new foundational layer, and that layer is where architectural integrity gets decided.
Matt Mullenweg also opened a “Rethinking Left Navigation” discussion, which points at a serious rework of the WP-Admin UI. @jorbin wants it kept as a Feature Plugin for now, and @joedolson raised accessibility concerns about keeping navigation order consistent. He is right to. Let users reorder menus with no strict schema behind it and you break WCAG 2.1 compliance for every site owner on the new UI.
The AI Client and Connectors API
The technical substance is in the new WordPress 7.0 APIs built for AI interoperability. The AI Client gives you a provider-agnostic way to send prompts, and the Connectors API handles the handshake between WordPress and external LLMs. Plugin developers who have been hand-rolling wrappers for OpenAI, Anthropic, or a local model get to delete a lot of code.
I went through how the AI Client works at the logic level in my breakdown of the Essential WordPress 7.0 AI Client.
A stripped-down registration for a custom provider, using the Connectors API, looks roughly like this:
<?php
/**
* Registering a custom AI Connector in WordPress 7.0
*/
function bbioon_register_custom_ai_connector() {
if ( ! function_exists( 'register_ai_connector' ) ) {
return;
}
register_ai_connector( 'custom-provider', array(
'label' => __( 'My Custom AI', 'bbioon' ),
'endpoint' => 'https://api.custom-ai.com/v1',
'auth_type' => 'bearer',
'capabilities' => array( 'text-generation', 'summarization' ),
) );
}
add_action( 'init', 'bbioon_register_custom_ai_connector' );
Accessibility and the Cover block argument
Removing YouTube video support from the Cover block set off a long argument. @wildworks and others say it violates the ToS and creates accessibility hurdles. @jorbin countered that WordPress has shipped video headers for nearly a decade with no real outcry. That is the usual standoff in core work: user freedom against technical purity. The discussion moved to a Slack thread for more feedback.
If the new WordPress 7.0 APIs are eating your dev hours, I can take that work over. I have been building on WordPress since the 4.x days.
What I would do now
7.0 is turning into a developer’s release. Between the AI Client and a stable Presence API, the core is getting more collaborative and more AI-aware at once. What I tell clients: do not rush the upgrade the week 7.0 drops. Spend the extended cycle testing these APIs on staging. Watch the Presence API for race conditions in particular, especially if you run heavy customization on the editor screen.
