News
WordPress 7.2 Takes Shape as Playground Expands AI Tools
WordPress has named the team guiding its final major release of 2026, with Matt Mullenweg leading WordPress 7.2 and a December release window on the calendar. Separately, WordPress Playground is expanding how AI agents can work with sites inside a browser, including tools registered by plugins. Release squad announcement, release schedule, Playground announcement.
The developments sit alongside a nearer-term maintenance release, Gutenberg editing improvements, and a community-built WordCamp game. They represent different stages of work: some features are available now, some are ready for testing, and others remain on a release schedule.
WordPress 7.2 has its release team
Jeffrey Paul announced the release squad on September 9. David Baumwald handles release coordination, while George Mamadashvili and Peter Wilson serve as tech leads. Jb Audras and Eshaan Dabasiya lead triage, with Md Noruzzaman, Jina Parekh, and Erick Wambua overseeing testing.
The project is continuing its smaller release-squad model, working with Make team representatives to coordinate contributions. The announcement says more people volunteered than there were available roles, while emphasizing opportunities to contribute through testing, documentation, and bug scrubs. Official squad announcement.
Twenty Twenty-Seven is planned to accompany the release. Henrique Iamarino leads its design, with Maggie Cabrera and Carolina Nymark leading development. The theme effort also includes Juanfra Aldasoro as lead mentor, with an emphasis on supported opportunities for new contributors. Default-theme team announcement.
December is the target, with testing beginning in October
The current WordPress 7.2 schedule lists these milestone windows:
- Beta 1: October 20–22, 2026.
- Release Candidate 1: November 17–19, 2026.
- Final release: December 8–10, 2026.
These are planning targets. The published call for volunteers explicitly allows adjustments based on development progress and release-team coordination. Official schedule, planning announcement.
The release page also makes clear that the feature list depends on readiness:
New features will be considered if deemed reasonably ready.
For plugin and theme developers, the calendar provides a testing window rather than a guarantee that every proposal under discussion will ship. The schedule moves contributors toward testing and bug fixes at Beta 1, followed by release-candidate preparation and the Field Guide. WordPress 7.2 release page.
Playground gives AI agents tools inside the browser
In a September 5 announcement, Fellyph Cintra described how WordPress Playground exposes actions to compatible AI agents through WebMCP. Those actions include running PHP, managing sites, navigating pages, and reading or writing files.
The interaction happens alongside a running WordPress site that a person can inspect and continue using. As Cintra explains:
You can continue using the interface, inspect the result, and guide the next step.
WebMCP is a proposed browser API, currently a W3C Community Group draft. It is not an official W3C standard, and using the integration requires a compatible browser environment. Playground team's announcement.
An implementation change merged on September 3 addresses a specific obstacle: WordPress runs inside an iframe in Playground, where a plugin's tools may be hidden from an agent inspecting the outer page.
The new proxy advertises those registered tools on the Playground page and forwards calls into the embedded WordPress site. It follows the active site and updates the available tools as registrations or navigation change. WordPress Playground pull request #4301.
This opens a practical route for plugin demonstrations and experiments in a shared browser session. Cintra's examples include building landing pages and preparing repeatable plugin demos. The announcement distinguishes browser-based WebMCP from Playground's separate MCP integration, which uses a local server and a WebSocket bridge. Workflow examples and integration details.
WordPress 7.1.1 is the nearer-term update
Before 7.2 reaches beta, WordPress 7.1.1 is approaching its planned September 17 release. Adrian Duffell announced the first release candidate on September 10, with testing available through the WordPress Beta Tester plugin, WP-CLI, or a direct download.
The announcement describes its scope:
WordPress 7.1.1 is intended as a bug-fix only maintenance release.
The candidate includes fixes for issues introduced during the 7.1 cycle or deferred near its end. Listed work covers media handling, editor behavior, layout styles, and a multisite user-deletion regression involving content reassignment.
The final date remains subject to issues discovered during release-candidate testing. For maintainers already running 7.1, that makes the maintenance candidate the more immediate testing opportunity. Original RC1 announcement and fix list.
Gutenberg and the Code Reference get practical improvements
Gutenberg 23.9, announced September 2, brings changes aimed at reducing small editing frustrations. Blocks can be inserted from the block toolbar, while Global Styles marks blocks with custom overrides and provides a way to filter for them.
The release also adds independent vertical and horizontal gaps for Group block flex and grid layouts, along with additional styling controls. These are changes in the Gutenberg plugin release; its release notes are the source for the individual features. Gutenberg 23.9 announcement.
Meanwhile, Playground is appearing in developer documentation. Adam Zieliński announced that WordPress 7.1 shipped the first two runnable Code Reference examples, with more planned during the 7.2 cycle. A Run button executes the example in the browser, and contributors can define interactive snippets alongside methods in their DocBlocks. Runnable Code Reference announcement.
WordCamp World turns the conference into a game
Away from release schedules, The WP World has built a browser game around a fictional WordCamp. WordCamp World includes registration, a keynote, Contributor Day activities, and a closing ceremony, with exploration inspired by the real conference experience.
The game's own notice makes its status explicit:
This is a fictional, unofficial fan game.
It offers keyboard and gamepad controls and device-local saving. It is a community entertainment project, separate from the official release and contributor infrastructure described above. WordCamp World.
Together, these announcements give developers several concrete ways to participate: test the 7.1.1 candidate, follow the 7.2 milestones, explore Gutenberg's editing changes, or try Playground's browser tools. Each has its own requirements and maturity level, which the original project announcements document.