WordPress 7.0 is close, and AI 0.6.0 reads like groundwork for how machine learning will actually sit inside Core. Plenty of “experimental” plugins park in beta limbo for years and never come out of it. This release looks more like the team tidying the architecture up for production. Anyone following the WordPress 7.0 Connectors API will recognize the direction: less cool demo, more workflow you can build on.
From experiments to stable features
The biggest change in AI 0.6.0 is how functionality gets registered internally. Everything used to be a loose “experiment.” Now an experiment is a specific type of “Feature,” which gives the code a promotion path it did not have before. When an experiment matures, you toggle it into a stable Feature instead of rewriting it.
The plugin also dropped “Experiments” from its name. It is just “AI” now. That rename says something: these tools are no longer only for developers to poke at in staging, they are turning into the canonical bridge for AI in the WordPress ecosystem.
Image editing and refinement
Authors get more than a “generate” button now. AI 0.6.0 adds iterative refinement: expand a background, remove an element you do not want, all inside the Media Library. That matters more than it sounds for anyone actually publishing. A slightly wrong prompt used to mean starting over from nothing, and now you keep nudging the image until it fits the post.
On the developer side, the hook names have been standardized so they stop colliding as the plugin grows. If you wrote integrations against the older “Experiments” builds, expect some refactoring. Feature registration in your own code ends up looking roughly like this:
<?php
/**
* Registering a custom AI refinement ability.
* Prefixing with bbioon_ for safety.
*/
function bbioon_register_custom_ai_refinement() {
if ( ! class_exists( 'WP_AI_Feature_Registry' ) ) {
return;
}
// New structural approach in 0.6.0
WP_AI_Feature_Registry::register( 'bbioon-custom-editor', array(
'label' => __( 'Custom Contextual Editor', 'bbioon' ),
'type' => 'experiment', // Still in testing
'capability' => 'edit_posts',
'standardize' => true,
) );
}
add_action( 'ai_init', 'bbioon_register_custom_ai_refinement' );C2PA and content provenance
AI 0.6.0 ships the tooling, and the 0.7.0 milestone goes after the harder question. The team is working on content provenance via C2PA, which would let WordPress record whether an image or a text block came out of a model. With deepfakes and misinformation as common as they are, publishers working at enterprise scale will need that on the record.
The “Generate Alt Text” workflow got some attention too. The action moved to the Content tab, where editors will actually see it. Small UI move, but it puts accessibility in front of the person writing the post instead of leaving it for later. Enough of these and the plugin starts to feel like part of the block editor rather than something bolted on.
If AI 0.6.0 is eating your dev hours, I can take it on. I have been working with WordPress since the 4.x days, and I know where experimental features like these tend to break.
What to check in your own code
Do not skip past the naming changes. Going from “AI Experiments” to “AI” touched more than a folder name: constants and filters were renamed with it. If you have live deployments calling the old hooks, run your update routines against this version now, because the stability work here is pointed straight at WordPress 7.0.
