magicwp/blog
WordPress 7.0 'Armstrong' adds native AI infrastructure, new blocks, a redesigned admin, and a higher PHP minimum. Here's what changed and how to update safely.
WordPress 7.0, codenamed "Armstrong," landed on May 20, 2026 as the first major release of the year. For most of its development cycle it was billed as the "collaboration release," the version that would finally bring Google Docs-style multi-user editing to the block editor. That feature got pulled twelve days before launch. What shipped instead is arguably more consequential: a native AI layer baked into core, two new blocks, the start of a long-overdue admin redesign, and a raised PHP floor that some sites will need to plan around before they can update at all.
This is a foundational release rather than a flashy one. The AI additions don't turn WordPress into a content generator on their own; they're plumbing that plugins and themes build on. But the practical effects reach every kind of site, from a single blog to a WooCommerce store to an agency managing dozens of client installs. Below is a grounded walkthrough of what actually changed in WordPress 7.0, what it means for how you run a site, and how to update without breaking production.
TL;DR
- WordPress 7.0 "Armstrong" shipped May 20, 2026. It adds native AI infrastructure to core: the WP AI Client (a provider-agnostic PHP interface), an expanded Abilities API, and a Settings > Connectors screen with Anthropic, Google, and OpenAI as default providers. Nothing is switched on until you configure it.
- Actual AI features like alt-text suggestions and excerpt generation ship separately in an optional official AI plugin. Core stays lightweight.
- Two new blocks arrived: Icon and Breadcrumbs. The admin got a DataViews-based redesign and an admin-wide command palette. Visual Revisions replaced the old revisions screen.
- Real-time collaboration was removed before release over stability concerns and is deferred to a future version.
- PHP 7.4 is the new minimum. Sites on PHP 7.2 or 7.3 stay on the 6.9 branch until they upgrade PHP. Test on staging and take a backup before updating.
The biggest change in 7.0 is that WordPress now ships infrastructure for talking to AI models. It's worth being precise about what that does and doesn't mean, because a lot of the early coverage blurred it.
WordPress 7.0 does not include a built-in AI writer, and it does not pick an AI provider for you. Core stays deliberately thin. What it adds is a standardized way for plugins, themes, and core itself to connect to external AI services in a consistent, governable way. Until now, every AI plugin shipped its own API key field, its own provider dropdown, and its own billing relationship. Install three AI plugins and you had three separate setups to manage. WordPress 7.0 replaces that pattern with a shared layer.
There are four pieces to understand.
The WP AI Client is a provider-agnostic PHP interface built into core. A plugin describes what it wants (a text completion, an image, an excerpt) and WordPress routes that request to whichever provider you've connected, without the plugin hard-coding anything provider-specific. It uses the WordPress HTTP API under the hood, so it behaves like other core network calls. The value here is maintainability: plugin authors write against one interface instead of maintaining separate integrations for each model vendor.
Under Settings > Connectors there's now a single place to add, update, and remove external AI connections. WordPress 7.0 ships three official provider presets: Anthropic (Claude), Google (Gemini), and OpenAI (ChatGPT). Community-built connectors can add others. One credential entered here is shared across every compatible plugin, so you manage keys in one location instead of scattering them across plugin settings.
Behind that screen sits the Connectors API, the extensibility layer that handles the provider registry, authentication metadata, and future connection types. Its architecture is designed to eventually support external services beyond AI, though AI is the first use case.
The Abilities API was introduced on the server side in WordPress 6.9 and expanded in 7.0, including a JavaScript counterpart. It gives plugins, themes, and core a structured, machine-readable way to describe what they can do, along with the permission boundaries around each action. An AI tool can then discover what it's allowed to do on a site rather than guessing at the interface. Abilities can be listed, filtered, executed, and gated behind permission callbacks.
This is the piece that points toward more agentic workflows. Combined with the official MCP Adapter that also shipped, agents like Claude Code, Cursor, and Codex can read from and write to a site through a defined, permissioned surface rather than by scraping the admin.
None of the above generates content by itself. The user-facing features (image generation, title and excerpt writing, alt-text suggestions) live in a separate, official AI plugin that's opt-in and marked experimental. If you don't install it and don't configure a connector, WordPress 7.0 sends nothing to any AI provider. That separation is intentional: core provides the framework, and the actual AI behavior is something you turn on deliberately.
Important: Connecting a provider means storing (or referencing) an API key that plugins can use to run billable requests. Treat that key like any other production credential.
For most site owners, the day-one impact is small, because nothing is enabled by default. The real significance is directional. WordPress is building the structure that AI workflows (drafting, alt text, SEO assistance, agent-driven site changes) will run on for years. If you plan to use any of it, a few practical concerns matter:
Managing AI credentials cleanly is easier when your host gives you real environment separation. On MagicWP, per-site environment variables and one-click staging let you keep development, staging, and production keys apart instead of hard-coding a single key into a live site.
WordPress 7.0 adds two blocks to the editor.
The Icon block lets you insert and style icons natively, without a plugin or custom SVG markup pasted into an HTML block. It's a small quality-of-life addition that removes a common reason people reached for third-party icon plugins.
The Breadcrumbs block is the more interesting one for content sites. Breadcrumbs improve navigation and give search engines a clearer picture of your site hierarchy, and having a native, schema-ready block means you no longer depend on an SEO plugin or theme feature to place them. For blogs, documentation sites, and stores with deep category structures, this is a genuinely useful native option.
Both blocks work in the block editor and the Site Editor like any other core block.
The WordPress dashboard had looked largely the same since 2013. WordPress 7.0 begins changing that through a system called DataViews.
DataViews rebuilds the Posts, Pages, and Media list screens to feel like a modern application rather than a static database table. You get inline filtering and sorting without full page reloads, and multiple layout options: table, grid, or list. For anyone who spends real time in wp-admin, the difference is felt daily. This is the start of a broader redesign, not the finished product, so expect more screens to adopt these components in later releases.
Alongside the visual work, the command palette is now available across all of wp-admin, not just the editor. Press Ctrl + K (or Cmd + K on macOS) anywhere in the admin to jump to a screen, run an action, or navigate without hunting through menus. Agencies managing many client sites tend to get the most out of this, since it turns repetitive navigation into a couple of keystrokes.
The revisions experience in the block editor was reworked. Instead of jumping to a separate screen to compare versions, WordPress 7.0 keeps you in the editor and activates a revision mode in place, with a color-coded view of what changed and a timeline slider to move between versions. It's a clear improvement for editorial teams who review changes regularly, and it makes rolling back an unwanted edit less of a chore.
Beyond the headline items, 7.0 bundles a long list of editor and design refinements. A few stand out:
None of these is dramatic on its own, but together they cut down on the small pile of plugins many sites accumulate just to handle basic design tweaks.
WordPress 7.0 removes some real friction for developers.
The most notable is PHP-only block registration. You can now register certain blocks without a JavaScript build step, which lowers the barrier for server-side developers who don't want to maintain a React toolchain for simple dynamic blocks.
There's also the DataViews, DataForm, and Fields API surface that plugin authors can build custom management interfaces on, plus the client-side Abilities package with built-in UI hooks and command palette integration. The editor now also runs inside an iframe when every block on a page uses the latest Block API, which keeps editor styles and site styles from leaking into each other, something theme authors have wanted for a while.
For most of the release cycle, real-time collaboration (RTC) was the headline: multiple people editing the same post simultaneously with live cursors, no more "someone else is editing this" lock screen. On May 8, 2026, twelve days before launch, it was removed from the release.
The core team cited stability problems found during release-candidate testing, including race conditions and server load concerns, and an architectural issue in how the feature synchronized data. Rather than ship it in a fragile state, they pulled it and deferred it to a future version. The feature isn't dead; work continues, and it remains testable in the Gutenberg plugin. But it is not part of the 7.0 upgrade.
For most sites this is a non-event, and arguably a relief: there's less new behavior to adapt to, and pulling a risky feature rather than shipping it broken reduced the odds of instability in the first release. If your team was specifically planning workflows around live co-editing, though, that plan needs to wait for a later version.
A major (x.0) release is exactly the kind of update to approach carefully. The pattern to follow hasn't changed: check requirements, test on staging, back up, then update production.
WordPress 7.0 raises the minimum to PHP 7.4. Support for PHP 7.2 and 7.3 was dropped. If your server runs an older version, WordPress won't push you to 7.0; your site stays on the 6.9 branch with security updates only until you upgrade PHP.
Practically, you should be targeting well above the minimum anyway. The performance and security work in recent releases is aimed at PHP 8.x, and running PHP 8.2 or 8.3 is the sensible baseline for a production site in 2026. Confirm your current version and check that your active plugins and theme support your target PHP version before you move.
Note: The exact PHP versions available and recommended can change. Confirm current guidance in the official WordPress requirements rather than assuming a specific number.
Never run a major update against a live site first. Clone your site to a staging environment, update there, and check that your theme, page builder, SEO plugin, multilingual tools, and any WooCommerce extensions still behave. Editor-level changes, the new block APIs, and the AI infrastructure can affect plugins that customize the editor or rely on older workflows, so a page builder or SEO plugin is exactly where a compatibility issue would show up.
On MagicWP, one-click staging and cloning make this straightforward: spin up a copy, run the update, verify, and only then apply it to production.
Before touching production, take a full backup so you have a clean restore point if something goes wrong. MagicWP keeps daily off-site backups with one-click restore and lets you take an on-demand backup right before a change, so you're not relying on the last scheduled snapshot.
For sites that depend on many plugins working together, there's a reasonable argument for holding off a couple of weeks after a major release. Early patch releases (a 7.0.1, for example) tend to clean up compatibility issues that surface once a broad range of sites start running the new version, and plugin authors need a little time to ship their own updates. Testing on staging still tells you most of what you need to know, but on a complex production site, a short wait is cheap insurance.
WordPress 7.0, codenamed "Armstrong" after jazz musician Louis Armstrong, was released on May 20, 2026. It had originally been targeted for April 9 to coincide with WordCamp Asia, but the release was extended by several weeks to stabilize the AI infrastructure and admin work. You can update from Dashboard > Updates or download it from WordPress.org.
No. WordPress 7.0 adds AI infrastructure to core (the WP AI Client, the Abilities API, and a Connectors screen), but it does not generate content on its own and does not choose a provider for you. Actual features like title, excerpt, and alt-text generation ship in a separate, optional official AI plugin. Nothing is sent to any AI provider until you install that plugin (or another AI plugin) and configure a connection under Settings > Connectors.
Out of the box, the Connectors screen includes presets for Anthropic (Claude), Google (Gemini), and OpenAI (ChatGPT). You add your own API key for whichever provider you choose. Because connections run through the Connectors API, community-built connectors can add other providers, and one credential entered in Connectors is shared across all compatible plugins.
Two: the Icon block, for inserting and styling icons natively without a plugin, and the Breadcrumbs block, a native, schema-ready way to add breadcrumb navigation that improves both usability and how search engines read your site structure. Both work in the block editor and the Site Editor.
Real-time collaboration was pulled on May 8, 2026, twelve days before launch, because release-candidate testing surfaced stability problems, including race conditions and server-load concerns, along with an architectural issue in how the feature synced data. The core team chose to defer it to a future version rather than ship it in a fragile state. It's still being developed and can be tested in the Gutenberg plugin, but it is not part of the 7.0 release.
Possibly. WordPress 7.0 requires at least PHP 7.4, and support for PHP 7.2 and 7.3 was dropped. If you're on an older version, your site stays on the WordPress 6.9 branch (with security updates) until you upgrade PHP. In practice, aim higher than the minimum: PHP 8.2 or 8.3 is the sensible target for performance and security. Confirm current requirements in the official WordPress documentation before you update.
For most sites, yes, provided you test first. Clone to staging, update there, and confirm your theme and critical plugins (page builders, SEO, multilingual, WooCommerce extensions) still work before applying it to production. Take a full backup before updating the live site. If your site relies on many interdependent plugins, waiting a couple of weeks for the first patch release and for plugin authors to catch up is a reasonable precaution.
WordPress 7.0 is a foundational release rather than a feature parade. The native AI layer, the WP AI Client, the Abilities API, and the Connectors screen, doesn't hand you AI features so much as give the ecosystem a consistent, governable way to build them, while keeping core lightweight and everything opt-in. Add the Icon and Breadcrumbs blocks, the DataViews admin redesign, the admin-wide command palette, and Visual Revisions, and you get a release that quietly changes how WordPress feels to use day to day, even with real-time collaboration deferred to a later version.
The practical takeaway is simple: WordPress 7.0 is worth adopting, but treat it like any major update. Confirm your PHP version, test on staging, back up before you touch production, and turn on AI features deliberately rather than by default. If you'd rather not manage staging, backups, and PHP versions by hand, MagicWP handles those parts for you, so you can test WordPress 7.0 on a staging clone and restore in one click if anything goes wrong, and keep the actual updating boring.
Monthly engineering notes, product updates, and WordPress performance tips. No spam, unsubscribe anytime.