On June 19, 2026, Anne McCarthy published the roadmap to WordPress 7.1 on Make WordPress Core. The release is scheduled for August 19, 2026, and the headline feature is the one everyone has been waiting for: real-time collaborative editing. The same feature Matt Mullenweg pulled from WordPress 7.0 on May 8 — twelve days before the scheduled release — is back, and this time the team is treating it like the structural challenge it actually is.

If you missed the drama, here is the short version. WordPress 7.0 was supposed to be the release that brought Google Docs-style editing to the block editor. Multiple cursors in the same paragraph, presence indicators, conflict-free merging of concurrent edits. On May 8, Mullenweg pulled it, citing surface area concerns, race conditions, server load issues, memory efficiency problems, and recurring bugs surfaced through fuzz testing. His quote: "not confident the current approach is robust enough to include in Core at this time." WordPress 7.0 shipped on May 20 as a polish release instead.

Seven weeks later, collaborative editing is back on the roadmap. But this is not the same feature rushed back in. The 7.1 roadmap positions RTC alongside a broader set of collaboration tools, and there is a dedicated outreach effort specifically designed to get the feature the kind of community testing it should have had the first time around.

What is actually new in 7.1

The collaborative editing work in 7.1 goes beyond just restoring what was pulled from 7.0. The roadmap introduces Notes features, including suggestion mode and emoji reactions, that make asynchronous feedback richer. Think of it as the middle ground between "one person edits at a time" and "everyone types simultaneously." You can leave a note on a block, suggest a change without committing it, and react with emoji to indicate approval or disagreement. For editorial teams that do not need live co-editing but do need structured feedback loops, this is the feature that actually matters.

Real-time collaboration is still listed as a focus area, but the roadmap language is careful. It says RTC "remains an exciting focus area with a few strategic decisions remaining to shape exactly how it'll show up in the WordPress experience." That phrasing suggests the team is still deciding whether RTC ships as a full Core feature in 7.1 or arrives as an opt-in experimental feature behind a flag. Given what happened with 7.0, the cautious approach makes sense.

The AI client gets serious

The other major thread in 7.1 is the continued evolution of the WordPress AI Client. In 7.0, WordPress shipped a provider-agnostic AI client framework — a way for plugins to connect to any AI service through a standardized interface. In 7.1, two new capabilities are planned: generation streaming and embeddings.

Generation streaming means AI responses can start appearing in the editor as they are generated, instead of waiting for the full response to complete. If you have used ChatGPT or Claude, you know the difference. Watching text appear word by word feels responsive. Waiting for a full block of text to load feels broken. Streaming is the difference between "AI assistant" and "AI that feels like it is thinking."

Embeddings are the bigger technical addition. They represent content as vectors, which enables meaning-based search across a site. Instead of searching for exact keyword matches, you can search for concepts. "Posts about shipping delays" would find content that mentions "logistics problems" or "supply chain issues" even if those exact words never appear. For sites with large content libraries, this is the kind of search improvement that changes how editors find and reuse existing content.

The roadmap also mentions a Guidelines feature — a persistent, structured way to encode editorial rules into WordPress. This is explicitly designed for AI collaboration. If you want AI-generated content to match your site's voice, tone, and formatting preferences, Guidelines lets you define those rules once and have the AI client respect them across all interactions. It is the difference between telling an AI "write like we do" every single time and having the AI already know.

Styling and editor improvements

Two long-requested styling features are on the 7.1 roadmap: responsive styling and pseudo-state styling in the Site Editor. Responsive styling means you can set different values for different screen sizes directly in the editor, without writing media queries in custom CSS. Pseudo-state styling means you can define hover, focus, and active states visually. These have been CSS-only territory since the block editor launched, and moving them into the visual interface closes one of the most common complaints from designers who use WordPress.

There is also a new free-form image cropper for media uploads, expanded support for more image formats through client-side processing, and a new Identity section in the Site Editor for setting key site details. The command palette is getting recently used commands and suggestions. The admin bar will now appear inside editors, which sounds small but removes a constant context switch between the editor and the admin interface.

What this means for you

If you run a multi-author WordPress site, 7.1 is the release to watch. The combination of Notes for asynchronous feedback, potential RTC for live editing, and Guidelines for AI consistency addresses the three biggest workflow gaps in the current editor. If you are a developer building on the AI Client, streaming and embeddings are the features that will make your integrations feel native instead of bolted on.

The release is targeted for August 19, which aligns with WordCamp US. Between now and then, the outreach effort for collaborative editing is the best way to get involved if you want to help shape how RTC ships. The feature needs real-world testing on real hosting environments with real editorial workflows, not just the controlled conditions that caused it to fail fuzz testing in May.

WordPress 7.0 was supposed to be the big one. It wasn't. WordPress 7.1 might actually deliver on that promise — and the extra two months of structural work might be exactly why it does.

Sources: Roadmap to 7.1 — Make WordPress Core, June 19, 2026. RTC Removed from 7.0 — Make WordPress Core, May 8, 2026. SmartWP analysis — May 2026.