WordPress 7.0 shipped last week. I have watched WordPress releases since 2007, and this is one of the more honest ones. It admits what is not ready and ships the parts that are, laying the groundwork for a year of AI work the platform has been quietly preparing for.
If you want the plain feature-by-feature walkthrough first, I wrote the site-owner version here. This piece is the read from a few feet back — what the release means, not only what it contains.
The AI integration is mostly plumbing, and that is the right call
The headline feature is the Abilities API plus a Connectors admin screen plus the WP AI Client. The breathless version of this story will read “WordPress ships AI.” The accurate version is “WordPress ships the connection layer plugin developers needed for their AI integrations to play well together.” I run an AI routing layer across my own client work — a frontier-model-versus-local-model decision layer that now handles a majority of my routine output — and from that seat the distinction is the whole story: 7.0 did not ship intelligence, it shipped the wiring intelligence plugs into.
That distinction matters. WordPress did not ship a built-in chatbot, content generator, or any other AI feature you can use directly out of the box. What 7.0 ships is the contract: a standard way for plugins to register their AI capabilities, and a single screen where users connect and manage those services. Behind that screen sits a client that abstracts the model calls so each plugin no longer has to. Plugin developers now have a place to plug into, and AI credentials get one managed home instead of ten plugin-specific settings panels.
Before Each plugin holds its own key
Ten plugins meant ten plugin-specific settings panels and ten places a key could live.
After Plugins share one AI Client and one credential
AI credentials get one managed home; plugins register their abilities and plug into the shared client.
This is the same shape as WP_REST_Server in 4.4 or the Site Health screen in 5.2 — infrastructure that becomes important once an ecosystem builds on it. The features people will judge WordPress AI on are the ones that ship in plugins over the next twelve months. The platform built the connecting layer. What runs through it is the next conversation.
For plugin authors maintaining AI-adjacent work: the Abilities API documentation is worth reading this week. Register your abilities. Test the Connectors screen. The compatibility window is open now.
What did not ship: real-time collaboration
This is the more interesting story. Real-time collaboration was on the 7.0 roadmap for months. On May 8, the release team announced it would not ship — “the current approach is not robust enough.” They published the performance testing analysis that informed the decision.
Pulling a roadmap feature twelve days before release is the senior move. It would be easy to read this as “WordPress could not deliver real-time collaboration.” That is not what happened. The team had built a version, tested it under load, and decided that shipping something fragile cost more than waiting. That kind of decision-making is what mature platforms do. Half-shipped real-time collaboration would have been the next four years of plugin-versus-core trench warfare and editor-team frustration. The team that pulled it knew that.
If you are running editorial workflows on WordPress that have been waiting for real-time collaboration: the alternative is still external. The team will iterate. The next version of this — when it ships — will be the version that holds up.
The quieter changes that matter more than the headline
Visual Revisions ships in 7.0 — side-by-side post-version comparison that finally treats revisions like a thing editors need to look at, not a thing the database happens to store. For newsroom and member-association editorial teams who have been routing this through external tools, the in-core version is now adequate for most use cases.
Pattern Overrides combined with the new contentOnly default for patterns means design-system work becomes meaningfully simpler. If you have been building bespoke block-pattern libraries for clients, audit your patterns this week — contentOnly becoming the default changes what is editable without an explicit opt-out.
The iframed editor is a stability win for full-site editing work that has been carrying CSS-leak debt for two releases. The Command Palette shortcut (Cmd+K / Ctrl+K) is a small productivity gift. Responsive editing mode with device-specific block visibility makes mobile-conscious editorial work less of a fight.
PHP 7.4 is the new minimum, with 8.3 the recommended floor. If you are still on a host that ships PHP 7.3, the upgrade conversation is now mandatory rather than recommended.
What to do this week
If you maintain plugins or themes: install 7.0 on a staging environment today. Run your full plugin suite. The title-attribute removal from author link functions has a backward-compatibility parameter, but any custom code wrapping those functions wants a review pass. Patterns with editable blocks need an explicit "role": "content" declaration if you want them editable — the default flipped.
If you run editorial teams on WordPress: the Visual Revisions change is the one to walk your editors through. The responsive editing mode is the second. Both are quiet quality-of-life improvements that compound over a year of use.
If you are a buyer choosing between WordPress and a competing CMS this quarter: the AI infrastructure ships now. The features that will live on it ship from the plugin ecosystem through 2026 and 2027. The platform is positioning for that. You are choosing the platform on that trajectory, not a finished AI product.
Where this puts the platform
WordPress 7.0 is a confident release. It shipped the part of the AI story it could ship well and held back the part that was not ready. It still made the quieter editorial improvements that compound. That combination — ship what is ready, hold what is not, sweat the small features — is what a mature platform looks like.
The conversation that will define the next eighteen months is what runs on the new AI infrastructure. Core did the part core should do. The next chapter belongs to the plugin and theme authors who build the features people will judge WordPress AI on.
What I am watching for is the first plugin that makes the new AI layer feel inevitable rather than optional.
Last reviewed May 27, 2026.
Rate and review this content
Be the first to rate this. Submissions are reviewed before they appear.