The Core AI team is finishing a guide for anyone who wants to give a talk on WordPress Core AI projects at a meetup or WordCamp, and they want feedback on it before it goes into the official handbook. WordPress 6.x has been moving toward a standard, modular way of connecting the platform to AI, and this guide is about how to present that.
I have sat through enough AI hype talks that ended with no takeaway at all. A guide that explains what Abilities and the standard AI Client actually do is worth more than another slide about the future of work. It also tries to pull the conversation away from proprietary vendor lock-in and toward open building blocks, which is the part I care about. If you are planning a talk, read the proposed structures before you outline anything.
The architecture behind WordPress Core AI projects
Three projects carry most of this work. They are core-level experiments in standardizing how WordPress talks to an LLM rather than plugins sitting on top of it:
- Abilities, a way for WordPress to describe its own functions to an external agent.
- AI Client, a standardized API for calling different providers such as OpenAI or Anthropic.
- MCP Adapter, which connects WordPress to the Model Context Protocol format.
The quick version of any of this is a hardcoded cURL request to an OpenAI endpoint. It works until the provider changes its response shape or you need to switch models, and then it is your problem. That is the whole argument for letting the WordPress Core AI projects abstract the call instead. The WordPress AI guidelines put maintainability first for the same reason.
// Conceptual: How an 'Ability' might be registered in the new framework
add_action( 'init', function() {
if ( function_exists( 'bbioon_register_ability' ) ) {
bbioon_register_ability( 'fetch_sales_stats', [
'description' => 'Provides WooCommerce sales data to the AI agent.',
'callback' => 'bbioon_get_woo_report',
] );
}
} );What the team needs from reviewers
The draft covers talk ideas, demo tips and how to plan a session. What the team cannot judge from the inside is whether any of it reads clearly to someone who does not already sit in #core-ai on Slack. Too dense and a first-time speaker gives up on it. Too vague and the talks stay shallow.
The draft guide is open for comments until Wednesday, 21 April 2026. Anyone already building with AI Agents and MCP will spot the gaps faster than the people who wrote it.
If the AI side of your site is eating hours you would rather spend elsewhere, I can take it on. I have been working with WordPress since the 4.x days.
What I would take from this
Most of the interesting work in WordPress Core AI projects sits in the architecture, not in the demos that get the applause. A speaker guide that says so will do more for the next WordCamp audience than another live prompt on stage. Read the draft and leave a comment while it is still open.
