WordPress 7.0 Ships May 20 With a Provider-Agnostic AI Client in Core, an Admin Refresh, and No Real-Time Collaboration
WordPress 7.0 arrives May 20 with a built-in AI Client API and a wp-admin refresh, after real-time collaboration was cut from the release over stability concerns.
Overview
WordPress 7.0 is scheduled for general release on May 20, 2026, according to the project’s Make WordPress Core release schedule. The release headlines a built-in, provider-agnostic AI Client in core and a refresh of the wp-admin interface, but it ships without the real-time collaboration feature that had anchored early planning for the version. The collaboration work was pulled from scope before the third release candidate over a list of stability concerns, as documented on the Make WordPress Core blog.
The result is a release whose most durable additions are developer-facing infrastructure rather than the headline collaboration feature, alongside interface changes aimed at modernizing an admin screen set that has changed little in over a decade.
What We Know
The schedule
WordPress 7.0’s release date moved to May 20, 2026, with the project citing the need for “necessary architectural improvements for the 7.0 release,” according to the updated release schedule. That schedule lists Release Candidate 4 on May 14, 2026, a 24-hour code freeze and dry run on May 19, and the general release on May 20.
Release Candidate 3 arrived on May 8, 2026. The RC3 announcement notes that the milestone addressed “143+ issues” since RC2 and marked the hard string freeze point of the 7.0 cycle, after which translatable text is locked.
A provider-agnostic AI Client in core
The central new platform capability in WordPress 7.0 is the AI Client. As described in the Make WordPress Core developer note introducing it, “WordPress 7.0 includes a built-in AI Client — a provider-agnostic PHP API that lets plugins send prompts to AI models and receive results through a consistent interface.” The intent is that plugin developers describe what they need from a model without hard-coding a specific vendor.
Developers interact with the client through an entry point, wp_ai_client_prompt(), which creates a fluent builder for customizing prompts — for example, wp_ai_client_prompt('Write a haiku about WordPress.')->generate_text(); — per the same developer note. The API supports generating text and images, handling multiple modalities, and requesting structured JSON responses.
Core itself does not bundle the model vendors. WordPress 7.0 ships three official provider plugins — AI Provider for Anthropic, AI Provider for Google, and AI Provider for OpenAI — and site administrators configure which providers are available through a Settings > Connectors screen, according to the AI Client developer note. API keys are managed through the Connectors API; provider plugins that register with the AI Client’s provider registry get automatic connector integration, including the Settings > Connectors admin UI for key management.
That separation tracks the project’s stated design from the start. The December 2025 planning post for 7.0 described the goal as “an AI client and API for WordPress to communicate with any generative AI models of various capabilities using a uniform API,” with the explicit constraint: “Strictly no providers included in core.”
A JavaScript counterpart to the Abilities API
WordPress 7.0 also adds a Client-Side Abilities API, a JavaScript counterpart to the server-side Abilities API that the project introduced in WordPress 6.9. According to the Make WordPress Core developer note, the client-side API provides “a common interface that AI agents, workflow automation tools, and plugins can use to interact with WordPress,” and enables “client-side abilities like navigating, or inserting blocks.”
The same note describes the work as “fundamental to integrate with browser agents/extensions and WebMCP.” Server-side abilities registered via PHP are “automatically made available on the client when @wordpress/core-abilities is loaded,” and the client-side functionality is split into two packages: @wordpress/abilities for state management and @wordpress/core-abilities for the WordPress integration layer that fetches server-registered abilities via the REST API.
The admin refresh
The other visible change in 7.0 is to the wp-admin interface. The December 2025 planning post set out goals of “improving screens across wp-admin” and exploring “CSS improvements that can modernize the look and feel,” including a proposal to make the “modern” admin color scheme the default. The same post listed continued work on DataViews, with “DataForms/QuickEdit/Document inspector design iterations” and an aim to make “DataViews screens extensible in the site editor.”
What got cut
Real-time collaboration — the ability for multiple users to edit content simultaneously — was a major planned feature for 7.0. It was removed from the release before RC3. The removal post on Make WordPress Core cited “concerns around surface area, race conditions, server load, memory efficiency, and recurring bugs found through fuzz testing.” The post framed the cut as a “difficult decision, especially given the amount of work that has gone into the feature,” but necessary for “shipping a stable and reliable WordPress 7.0 release for our users.”
The RC3 announcement states that real-time collaboration “will be re-evaluated during the 7.1 release cycle,” and thanks the hosts that helped test variations of the collaboration architecture: Kinsta, Bluehost, GoDaddy, WordPress.com, XServer, and Ionos. The removal post adds that “once the immediate release work is complete, a plan will be shared for broader testing and continued iteration to help prepare the feature for a future release.”
What We Don’t Know
The project has not published a specific timeline for when real-time collaboration will return beyond the statement that it will be re-evaluated during the 7.1 cycle. The exact final feature set of 7.0 will only be fully fixed once the May 20 release ships; the schedule still listed RC4 and a dry run after RC3.
The planning post that mapped out 7.0 also carried a status note indicating that, by a February 2026 update, several roadmap items had moved into blocked or cancelled categories — but the public posts do not enumerate, item by item, everything that shifted between the December plan and the final release.
Analysis
The shape of WordPress 7.0 inverts its original framing. Real-time collaboration was the marquee user-facing feature in the December 2025 plan; the AI Client and the Abilities work were the infrastructure beneath it. With collaboration deferred, the infrastructure is what actually ships.
That is not necessarily a weaker release. The AI Client’s provider-agnostic design — a uniform PHP API in core, with model vendors confined to optional plugins configured per site — is a deliberate architectural choice that keeps WordPress core neutral on which AI companies a site owner trusts. Combined with the Client-Side Abilities API and its stated WebMCP integration goal, 7.0’s developer surface is being positioned for a web where automated agents act on sites, not just humans. For a platform that powers a large share of the web, standardizing how plugins talk to AI models, rather than letting each plugin wire up its own vendor integration, is a structural decision with a long tail.
The collaboration cut, meanwhile, is a reminder that fuzz testing and stability review can still override a high-profile feature late in a release cycle. Shipping the plumbing on schedule and re-evaluating the headline feature later is a conservative call — and, on the evidence of the removal post, a deliberate one.