WordPress 7.0, named “Armstrong,” was released on May 20, 2026, with contributions from over 875 people and more than 420 enhancements and fixes. The headline is that AI is now part of WordPress core rather than something you bolt on with a plugin. For most site owners, the practical impact is smaller than the announcement suggests, and the parts that do matter are not the parts getting the most attention.
AI in core does not mean your site now uses AI. It means the plumbing is there if you connect something to it. Nothing turns on by itself.
Primo Collab
What actually shipped
The release notes describe 7.0 as laying the foundation for AI across the WordPress experience. Concretely, that foundation is:
- An AI Client in core, which lets WordPress communicate with generative AI models.
- The Abilities API, which manages those connections through a centralized dashboard hub.
- An accompanying AI plugin that adds image generation, content generation, and alt text suggestions.
The word doing the work in all of this is “foundation.” Core ships the ability to connect to AI models. It does not ship an AI that starts writing your posts.
The changes you will actually notice day to day
Set the AI features aside for a moment. These are the 7.0 changes most likely to affect how it feels to use your site:
- A modernized dashboard with an updated color scheme and smoother transitions. If your admin suddenly looks different after updating, this is why.
- A Command Palette, opened with Cmd+K or Ctrl+K, giving you quick keyboard access to dashboard tools. This is the single best quality of life improvement in the release for anyone who works in WP admin regularly.
- New blocks: gallery lightbox slideshows, breadcrumbs, and icon blocks.
- Better responsiveness controls, letting you show or hide content based on device type without custom CSS.
What this means if you are on WordPress right now
Nothing breaks on update, and nothing AI related activates on its own. But three things are worth doing deliberately.
Update on a staging copy first
This is not specific to 7.0, it is just the discipline that keeps a major version update from becoming an incident. A major release touches the admin interface, block rendering, and APIs that plugins depend on. Test there, confirm your key pages and forms still work, then push to live.
Decide about the Connectors hub on purpose
The Abilities API manages AI model connections through a dashboard hub, which means an administrator can authenticate an external AI provider from inside WP admin. That is convenient and it is also a decision with real consequences: it determines which third party gets access to content on your site. It deserves an explicit choice, not a default.
Check who has admin access
The more that can be configured from the admin dashboard, the more an admin account is worth. If you have old contractor accounts, an agency login nobody has used in two years, or shared credentials, this release is a good prompt to clean that up.
What it does not do
- It does not write or publish content without someone setting that up.
- It does not connect to any AI provider until an administrator authenticates one.
- It does not change your existing content, themes, or plugins.
- It does not require you to use any of the AI features to stay on a supported version.
Should you update?
Yes, on the normal schedule you would use for any major release, which means after your plugins have confirmed compatibility and after testing on staging. Staying on an old major version to avoid AI features is not a good trade, because you also give up security patches and bug fixes that have nothing to do with AI.
The mistake to avoid
Reading “AI in core” as either a threat or a solution. It is neither on its own. It is infrastructure, and like any infrastructure the outcome depends entirely on what gets built on top of it and who you let connect to it. The site owners who get burned here will not be the ones who ignored the AI features. They will be the ones who connected a provider without thinking about what it could reach.