03.04.2026

WordPress Development

WordPress 7.0: AI Connectors, Real-Time Collaboration, and the Biggest CMS Shift Since Gutenberg

WordPress 7.0: AI Connectors, Real-Time Collaboration, and the Biggest CMS Shift Since Gutenberg

READING TIME: MIN

Table of Content

A Release Worth Marking on the Calendar

On April 9, 2026, the WordPress project ships version 7.0 – a release that core contributors and release lead Matias Ventura have described as the most transformative update since the Gutenberg block editor landed in WordPress 5.0 back in 2018. After a turbulent 2025 marked by legal disputes between Automattic and WP Engine, a reduced release cadence, and contributor uncertainty, the project deliberately reset. WordPress 6.9 “Gene,” released in December 2025, served as a stabilization release to clear technical debt. WordPress 7.0 is the payoff: a cohesive, well-tested platform upgrade built around three pillars – native AI integration, real-time collaboration, and a redesigned administration interface.

For any wordpress agency maintaining client sites, this release demands attention well before the update notification appears in dashboards. The changes are architectural, not cosmetic, and the preparation checklist is longer than usual.

The WP AI Client – Infrastructure First, Features Second

The most discussed addition to WordPress 7.0 is not a new block or a shinier dashboard. It is the WP AI Client – a core-level abstraction layer that standardises how WordPress communicates with external AI providers. The architecture is deliberate: rather than hard-coding support for a single AI service, the core team built a provider-agnostic interface. Plugins and themes can now tap into any AI model – whether that is OpenAI, Anthropic’s Claude, Google Gemini, or a self-hosted model – through a single, consistent API.

This distinction matters enormously. WordPress is not becoming an AI writing tool. It is becoming an AI-ready platform. The infrastructure ships in core; the intelligent features are built on top by the plugin ecosystem. The implication for a wordpress agency or development studio is clear: the next generation of intelligent WordPress plugins will be far more interoperable and maintainable because they share a common communication layer.

The Abilities API and Model Context Protocol Support

Running alongside the WP AI Client is the Client-Side Abilities API – a standardised registry for declaring what a WordPress site is capable of doing. Think of it as a capabilities manifest that AI agents can read and act upon. When an AI assistant queries a WordPress site through this API, it discovers available actions, contextual data, and site-specific workflows without requiring custom integration code.

WordPress 7.0 implements this through support for the Model Context Protocol (MCP), the same protocol used by AI assistants like Claude and ChatGPT to interact with external systems. In practice, this means an AI agent can, for example, discover that a site supports image resizing, retrieve a list of draft posts, or trigger a publishing workflow – all without a human intermediary. This is a foundational step toward agentic web experiences, and it positions WordPress as the first major open-source CMS with built-in AI agent support in core.

7 Growth Proven Strategies for Scaling Your WooCommerce

The Connectors Screen – Centralised AI Provider Management

The practical interface for all AI-related configuration in WordPress 7.0 lives under Settings > Connectors. Introduced in Beta 2 and refined through the RC cycle, the Connectors screen provides a central admin page for adding, updating, and removing external AI provider connections. The architecture is route-based and extensible: plugins can register their own connection types through a connections-wp-admin-init hook, making it straightforward to add proprietary or enterprise AI services to the same unified management surface.

For site administrators – and for every wordpress agency managing multi-client environments – this removes a persistent pain point. Previously, AI integrations meant scattered API keys across plugin settings screens, with no unified audit trail. The Connectors screen consolidates that into a single, auditable interface.

Phase 3 Collaboration – Notes, Fragments, and Co-Editing

WordPress 7.0 marks the primary push into Phase 3 of the Gutenberg roadmap, which is focused entirely on collaboration. The goal is to reduce editorial teams’ dependency on external tools like Google Docs, Notion, and Trello by bringing collaborative workflows directly into the block editor.

The key features entering core in this release include:

Fragment-level commenting: Building on the block-level Notes system introduced in WordPress 6.9, version 7.0 allows editors to highlight a specific phrase or sentence within a block and attach a comment to that exact selection – not just to the block as a whole.
Experimental real-time co-editing: Multi-user simultaneous editing arrives in an experimental state. It requires hosting infrastructure that supports WebSocket connections, so compatibility with the hosting environment should be verified before enabling the feature in production.
Workflow tools: The Command Palette receives significant improvements, becoming a faster keyboard-driven interface for navigating across editing, design, and administrative tasks.
Visual revision comparisons: Editors can now compare past and current versions of pages side-by-side in a visual diff view – a long-requested feature for content-heavy teams.

These additions collectively move WordPress from a “one editor at a time” model toward a genuine shared workspace. For a wordpress agency managing editorial workflows for clients in media, e-commerce, or enterprise sectors, these features address real operational friction without requiring third-party plugin dependencies.

The Admin Interface Redesign – DataViews Replaces List Tables

The traditional WordPress WP_List_Table – the tabular interface used across posts, pages, users, comments, and plugins – is replaced in WordPress 7.0 by DataViews. This is not a superficial reskin. DataViews is a modern, application-style component built on @wordpress/components that supports filtering, sorting, and switching between grid and list layouts. The result is an admin experience that feels far closer to a contemporary web application than to the dashboard that has been largely unchanged for over a decade.

The Benefits of Using Next.js for Enterprise WordPress Websites

The new default theme for 2026 accompanies the redesign, providing a visual baseline that aligns with the updated admin aesthetic. For agencies maintaining white-label WordPress environments or custom admin skins, the transition will require review of any custom admin_enqueue_scripts overrides or custom list table implementations.

PHP Requirements and Technical Infrastructure Changes

WordPress 7.0 raises the minimum supported PHP version to 7.4, dropping official support for PHP 7.2 and 7.3. The recommended version is PHP 8.3 or higher. This is not merely a housekeeping change. PHP 7.4 introduces typed properties and improved type consistency, and many modern AI SDKs already require PHP 8.x. Retaining a lower minimum was actively blocking core from adopting those libraries.

Additional technical changes worth noting for developers:

PHP-only block registration: Blocks can now be registered entirely in PHP with auto-generated inspector controls, reducing the JavaScript overhead required for simple custom blocks.
Client-side media processing: Image resizing and compression now leverage the browser’s native capabilities, reducing server load and enabling support for modern image formats like AVIF.
Block Bindings updates: Pattern overrides now extend to custom dynamic blocks, giving block authors more expressive power without custom JavaScript.
CodeMirror updated to v5.65.40: Affects the custom CSS and HTML editors in the Site Editor and classic widgets.

Any wordpress agency running client sites on shared hosting should audit PHP versions now. Requesting a PHP version upgrade from a hosting provider typically takes less time than debugging a broken plugin post-update.

How to Prepare Before April 9

The release is days away. The following checklist reflects what a responsible Vipe Studio WordPress inquiry commonly surfaces when agencies prepare client sites for major WordPress transitions:

Confirm the hosting environment is running PHP 7.4 as a minimum, with 8.3 recommended.
Verify WebSocket support with the hosting provider if real-time co-editing will be used.
Audit custom list table implementations for DataViews compatibility.
Review any AI plugins currently installed for overlap with the new Connectors architecture.
Test the site against WordPress 7.0 RC1 using a staging environment.
Check plugin compatibility, particularly any plugin that extends the admin interface or registers custom blocks.

Staging environments running RC1 are already available through tools like WordPress Playground, which has also gained MCP support – meaning AI agents can spin up a WordPress instance, install plugins, and run PHP directly in the browser for testing purposes.

How Outsourcing WordPress Development Can Actually Boost Your Profit

What Comes After – The 2026 Release Roadmap

WordPress is returning to a three-release cadence in 2026. WordPress 7.1 is tentatively scheduled for August 19, 2026, with a focus on media workflow improvements and more granular user permissions. WordPress 7.2 is expected in early December 2026, continuing the Phase 3 collaboration push and introducing early groundwork for native multilingual capabilities – a Phase 4 feature that has been on the roadmap for years. If certain features, such as advanced connector filtering, are not sufficiently mature for the 7.0 final release, they will slide to 7.1 rather than ship in an unstable state. The advanced connectors filtering feature is already explicitly flagged as a potential 7.1 candidate by the core team.

Teams working with a wordpress agency on long-term platform strategy should factor this cadence into planning cycles. The 2026 roadmap is the most predictable WordPress release schedule in several years, and it offers a genuine opportunity to build forward-looking editorial and AI integration strategies around confirmed milestones. Project specifications submitted through a WordPress inquiry form can already account for these upcoming platform capabilities when scoping new builds or major upgrades.

Conclusion – A Platform Maturing Into the AI Era

WordPress 7.0 is not a feature dump. It is a platform maturation. The AI Client and Abilities API lay a foundation that the plugin ecosystem will build upon for years. The Phase 3 collaboration tools address the real-world editorial friction that drove teams toward Google Docs and Notion. The DataViews admin redesign finally modernises a UI that has remained largely static since 2008. And the PHP 7.4 minimum sets a technical baseline that allows the project to adopt modern tooling without compromise.

For developers, for content teams, and for every wordpress agency responsible for keeping client platforms current, April 9, 2026 is not just another WordPress update. It is the beginning of a meaningfully different platform era.

Key Takeaways

WordPress 7.0 releases on April 9, 2026, led by Matias Ventura, and represents the largest architectural shift since Gutenberg.
The WP AI Client and Abilities API introduce a provider-agnostic AI integration layer into WordPress core, with support for the Model Context Protocol.
The new Connectors screen (Settings > Connectors) centralises AI provider management across the admin interface.
Phase 3 Gutenberg collaboration brings fragment-level commenting, experimental real-time co-editing, and visual revision comparisons into core.
PHP 7.4 is now the minimum supported version; PHP 8.3 is strongly recommended for sites making use of AI features.
WordPress 7.1 and 7.2 are planned for August and December 2026, continuing the collaboration and AI infrastructure roadmap.