WordPress 7.0: AI Web Client API Ships, Real-Time Collab Dropped

WordPress 7.0 lands on May 20 with a built-in AI Web Client API, React 19 powering the block editor, and PHP-only block registration that developers have been requesting since Gutenberg launched. What it won’t have is real-time collaboration—the marquee feature stripped from the release just 12 days before launch via a full code deletion. For plugin and theme developers, this is a foundation play, not a feature parade. Here’s what changed and what it means.

The AI Web Client API: WordPress Bets on Infrastructure

The biggest addition isn’t a feature users will notice immediately. WordPress 7.0 ships a provider-agnostic AI client directly in core—a PHP SDK that lets any plugin send prompts to any AI model through a standardized interface. The entry point is wp_ai_client_prompt(), which returns a WP_AI_Client_Prompt_Builder instance and converts provider exceptions into WordPress-native WP_Error objects.

The architecture matters more than the function signature. AI model providers remain entirely external to WordPress core. Plugin developers register their own providers via the new Connectors API, which surfaces under Settings > Connectors in the admin. Users configure their own API keys. WordPress ships none. No prompts go anywhere by default—it’s opt-in at every level.

This is the right approach. Every major CMS that has shipped AI features with a baked-in provider has created lock-in problems and privacy concerns. WordPress’s 43% market share means this API, if it gains traction, becomes the de facto standard for AI-augmented web content—and it won’t belong to OpenAI or Anthropic by default. Developers can start building against it now: the PHP AI Client SDK is open on GitHub, and the official merge proposal contains the full architecture documentation.

Real-Time Collaboration: The Full Code Deletion

Real-time collaboration was supposed to be the headline. Google Docs-style simultaneous editing had been in development for years and positioned as 7.0’s signature feature. Then RC3 dropped on May 8 and it was gone—not disabled behind a flag, not deferred to a settings toggle. Deleted.

The official announcement cites race conditions, server load, memory efficiency issues, and recurring fuzz-test failures. Matt Mullenweg also attributed part of the problem to the ongoing WP Engine litigation, claiming depositions created a time burden for critical contributors. That explanation deserves scrutiny. Race conditions and memory issues don’t get worse because lawyers are busy. The full code deletion—not a feature flag—suggests the problems ran deeper than a sprint of fixes could address.

The RC3 post says RTC will be “re-evaluated during the 7.1 release cycle.” Note the careful phrasing: not “shipped in 7.1.” If the architectural issues are as fundamental as the deletion suggests, the 7.1 timeline is optimistic. Teams relying on collaborative editing should look at third-party solutions and not plan around a native WordPress implementation before late 2026 at the earliest.

PHP-Only Block Registration: Finally

Among the additions that actually ship, PHP-only block registration is drawing the loudest enthusiasm from developers who’ve wanted it since Gutenberg launched. Pass 'autoRegister' => true in the supports array of register_block_type() alongside a render_callback, and the block appears in the editor with zero JavaScript required.

register_block_type( 'my-plugin/cta-banner', [
    'attributes' => [
        'heading'    => [ 'type' => 'string', 'default' => 'Default Heading' ],
        'buttonText' => [ 'type' => 'string', 'default' => 'Click Here' ],
    ],
    'supports'        => [ 'autoRegister' => true ],
    'render_callback' => 'my_plugin_render_cta',
] );

WordPress automatically generates Inspector Controls for string, integer, boolean, and enum attribute types and uses ServerSideRender for the editor preview. This won’t replace complex interactive blocks—but for author boxes, CTA banners, and theme-specific components, it’s a genuine quality-of-life improvement that lowers the barrier for PHP-first developers to participate in the block ecosystem.

The Migration Tax: Block API v3 Is Enforced

If you’re running blocks on apiVersion 2, you’re overdue. WordPress 6.9 introduced deprecation warnings; 7.0 enforces Block API v3. Any block code that references document or window directly will fail in the iframed editor. The fix: use a ref and access ownerDocument or defaultView instead.

The full iFrame enforcement was revised to a gradual rollout—7.0 won’t immediately break every legacy plugin. But the direction is clear. Meta boxes that inject directly into the editor DOM and admin scripts assuming global document access need updates. The May 2026 developer digest has the complete migration checklist.

What Else Ships

Two new core blocks: an Icon block for accessible, scalable icons, and a Breadcrumbs block with filter hooks (block_core_breadcrumbs_items, block_core_breadcrumbs_post_type_settings) that make it WooCommerce-friendly. The block editor upgrades to React 19 for performance and new framework features. A backwards-compatible polyfill for script module translations means plugin authors targeting older WordPress installs get broader compatibility without code changes.

Test RC3 Before May 20

The RC3 release is live now. If you maintain plugins, themes, or custom blocks, test against it before May 20. The AI Web Client API is the long-game story—the architectural shift that will define WordPress development for the next decade. RTC’s absence is a short-term gap and a longer-term question mark about project execution. The PHP-only block registration is the win developers will feel immediately. And the Block API v3 migration is not optional.