WordPress 7.0 landed with the most controversial feature set in years: AI baked straight into core. An AI Client, an Abilities API, and a Connectors hub in Settings that hooks up to OpenAI, Anthropic, and Google out of the box. I didn’t read about this one from the sidelines — my own site runs WordPress 7.0 with the Anthropic and Google provider plugins active. So here’s my honest, hands-on take on the WordPress 7 AI features, minus the press-release gloss.
The WordPress 7 AI Features That Shipped
Three pieces matter. The AI Client gives plugins one standard way to talk to language models instead of every plugin shipping its own API wrapper. The Abilities API lets plugins register what they can do — “create a post,” “resize an image” — in a way AI tools can discover and call. And the Connectors hub in Settings is where you paste your API keys once, centrally, instead of into nine different plugin settings pages. InfoQ has a solid technical rundown of the release worth reading, and the official details live on make.wordpress.org.
The Part I Genuinely Like
The centralized connectors solve a real, annoying problem. Before this, every AI plugin wanted its own key, its own settings page, its own billing surprise. One hub, one place to revoke access — that’s how it always should have worked. I recently built a plugin with Claude Code, so I can vouch for this. The Abilities API is the missing piece that would have saved me a chunk of custom glue code. Plugins that expose abilities become automation-friendly by default. That’s a big deal.
The Part That Made Me Wince
It’s rough in places. The developer docs are still catching up, some hooks feel half-decided, and the community reaction has been… spicy. Plenty of developers didn’t want AI in core at all, and I understand them — core features become everyone’s maintenance burden. There’s also a practical worry I’ve written about before. AI features tend to slow sites down when they’re bolted on carelessly. Core integration doesn’t automatically fix that; it just moves the responsibility.
Should You Actually Use It Yet?
My honest advice depends on who you are:
- Site owners: nothing forces you to touch any of it. No API key, no AI. Your site behaves exactly as before.
- Plugin developers: start experimenting now. The Abilities API is clearly where the ecosystem is heading, and early movers will have the polished integrations when demand arrives.
- Agencies: wait one point-release. Let the sharp edges get sanded before you standardize client sites on it.
My Verdict After Running It
The WordPress 7.0 AI features are a foundation, not a finished product — and honestly, that’s fine. Core adopting a standard beats the wild west of forty incompatible AI plugins, which is what we had. I’m keeping it enabled on my site, I’m building against the Abilities API, and I’m keeping my expectations calibrated: this is year one of a long story.
Quick Answers
Does WordPress 7.0 force AI on my site?
No. The features sit dormant until you connect a provider key in Settings. Skip that, and nothing AI-related runs.
Which AI providers work out of the box?
OpenAI, Anthropic (Claude), and Google Gemini connect natively through the new hub, and providers can add themselves via plugins.
Will it slow my site down?
The core framework itself is light. The risk is the same as always — what plugins do with it. Measure before and after, like I did in my speed checklist.
