WordPress 7.0 is hitting the home stretch, and the recent AI Contributor meeting made one thing clear: the WordPress 7.0 AI features are no longer just experiments. We are looking at a fundamental shift in how Core handles external model providers. However, as any senior dev will tell you, the road to Release Candidate 1 (RC1) is always paved with architectural friction and “ship it now, fix it later” decisions.
The Architecture of the AI “Off Switch”
The most heated debate right now involves how to let users walk away. There is a conflict between using a strict global constant (a hard “Off Switch”) and a WordPress filter. Specifically, the team is weighing the reliability of a constant against the flexibility of the Hook API. In my experience, while filters are the “WordPress way,” a constant is the only way to guarantee a plugin won’t override a site owner’s privacy decision.
Consequently, the current plan is to merge a baseline implementation for RC1 and continue the discussion. If you are managing high-security client sites, you need to understand the difference in implementation:
<?php
/**
* The strict constant approach (Hard Switch)
*/
define( 'WP_AI_DISABLED', true );
/**
* The flexible filter approach (Soft Switch)
* Warning: Other plugins can override this!
*/
add_filter( 'wp_ai_enabled', '__return_false', 999 );
MCP and the Quest for Stability
Furthermore, the Model Context Protocol (MCP) remains a major focus. We’ve discussed standardizing AI connectors before, but the pressure is on to decide if the MCP adapter should be a standalone package or bundled. If AI is going to be user-facing in 7.0, the underlying infrastructure must be rock solid. Therefore, stabilizing the codebase before RC1 is the top priority for contributors like @ovidiuiulian.
Image Editing Moves to Core
One of the biggest wins is that Image Editing has been officially promoted from an “Experiment” to a core feature for the 7.0 cycle. This means native AI-assisted cropping and editing are landing in the media library. While this is exciting, we’ve seen similar AI features trigger fatal errors in early builds, so testing version 0.6.0 of the AI Experiments plugin is critical.
On the design side, there is some pushback on the new “WordPress in bits” banner design. Some contributors feel the floating elements look like WordPress is breaking apart. You can check the feedback on Trac ticket #64711 if you want to weigh in before the design is locked.
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.
Summary of the RC1 Push
- Global Constant: Expected to land in RC1 for total AI opt-out.
- MCP Adapter: Version 0.5.0 aims to stabilize the model bridge.
- Open Source Models: A lack of local-LLM providers (like Ollama) on the initial screen is still a concern.
We are watching the merge closely. WordPress 7.0 is shaping up to be a defining moment for the CMS, but only if the “Off Switch” is as reliable as the features themselves.
