I have been through enough major release cycles to know the ten days before Beta 1 are mostly high-speed commits and architectural panic. The latest dev chat agenda for WordPress 7.0 Development puts us squarely in that window. There is a big push for AI-ready infrastructure, and after 14 years of fixing broken sites, a core merge this late with no Pull Request (PR) ready makes me uneasy.
The AI client gamble in WordPress 7.0 development
The headline item is the proposal to merge the WP AI Client into core. The idea is sound: a provider-agnostic API so plugins can talk to an LLM without each one bundling its own heavy SDK. Call it the “REST API moment” for generative AI in WordPress.
The timing is the problem. Felix Arntz (@flixos90) pointed out that Beta 1 is 10 days away and there is still no PR to test. Merging developer infrastructure that has not been exercised in trunk is how you end up maintaining a first draft for the next decade. I went through what this API is meant to standardize in my piece on WP AI Client standardization.
The admin reskin and ticket #64308
The AI discussion takes up all the oxygen, but the admin reskin (Ticket #64308) matters just as much to the 7.0 roadmap. It is not a React rewrite of the dashboard, which is still a distant dream. It is a coat of paint to bring the legacy PHP screens in line with the Gutenberg design system.
The core team is deciding whether to commit these tickets or punt them. The open problems are inconsistencies on the login screen and the way buttons get enqueued. Anyone building custom admin pages should watch the CSS changes closely, particularly how the wp-admin classes are being refactored for the new scheme.
<?php
/**
* Example: Checking if the proposed WP_AI_Client class exists
* to safely wrap your experimental features.
*/
function bbioon_check_ai_infrastructure() {
if ( class_exists( 'WP_AI_Client' ) ) {
// WordPress 7.0+ AI infrastructure is present
return true;
}
return false;
}
add_action( 'admin_init', 'bbioon_check_ai_infrastructure' );
Roadmap and core stability
The WordPress 7.0 Release Squad is in place and the bug scrub schedule is live. Gutenberg 22.5 shipped as well, with more refinements to the site editor. From here the work turns from adding features to stability and polish.
If keeping up with WordPress 7.0 Development is eating your dev hours, I can take it on. I have been wrestling with WordPress since the 4.x days.
Where this leaves us
7.0 is the most ambitious release in years. Between the AI Client and the admin refresh, the core team is reworking the backend and the developer experience at the same time. The merge timeline is the weak point. If the AI Client lands without a PR in the next few days, the RC phase is going to be full of patches. The Make WordPress Core proposal is where that decision gets recorded.
