WordPress 7.0 RC1 Drops Real-Time Collaboration, AI Connectors, and a Redesigned Dashboard

What Shipped in WordPress 7.0 RC1

WordPress 7.0 Release Candidate 1 became available on March 24, 2026, marking the final testing milestone before the scheduled stable release on April 9. The RC1 build includes over 134 updates and fixes since Beta 5, stacked on top of features introduced across Gutenberg versions 22.0 through 22.6.

Two major additions arrived after Beta 1 and landed specifically in RC1. The first is an AI Connectors screen – a dedicated wp-admin page for registering and managing connections to external AI providers. The second is a global Command Palette, triggered via Cmd+K or Ctrl+K from the admin bar, giving keyboard-driven users instant access to actions and navigation without touching the mouse. Both features fill gaps that the community flagged during beta testing, and both ship with extensibility hooks that plugin authors can tap into from day one.

Real-Time Collaboration Reaches Opt-In Stability

Multiple users editing the same post simultaneously is no longer experimental.

WordPress 7.0 ships a refined Real-Time Collaboration (RTC) system built on HTTP polling with data syncing and offline editing support. The default sync provider uses polling intervals that got increased in RC1 to reduce server load, and hosts or plugin developers can swap in WebSocket-based providers for lower latency. A WP_ALLOW_COLLABORATION constant gives site administrators a single toggle to enable or disable the feature at the server level, while individual users can turn session notifications on or off from the editor toolbar.

RTC stays opt-in for the 7.0 cycle. That decision came from the release squad to allow broader feedback before making it a default, which is a reasonable call given the infrastructure requirements. Hosting providers running shared environments should test the polling behavior under concurrent-user scenarios – the default intervals work fine for 2-3 simultaneous editors, but a site with 10+ active collaborators will benefit from the WebSocket path. If your server already handles persistent connections for features like async JavaScript loading, the upgrade path is straightforward.

The WP AI Client API and Connectors Screen

WordPress 7.0 introduces a centralized AI client baked into Core.

The Web Client AI API acts as a broker between WordPress and external generative AI providers. No AI model ships inside WordPress itself – the API only provides a standardized interface for plugins and themes to register providers, send prompts, and receive responses. The new AI Connectors screen under wp-admin surfaces all registered providers and lets site owners manage API keys and connection settings in one place. A PHP AI Client package (updated to version 1.3.1 in RC1) handles the server-side communication, while the Abilities API on the client side exposes AI-driven capabilities to the block editor and command palette.

This matters for developers building LLM-powered features for WooCommerce or any plugin that needs AI inference. Instead of bundling your own HTTP client and provider logic, you register your provider through register_ai_provider() and the Core API handles authentication, rate limiting, and response normalization. A single config option added in RC1 (#62067) lets administrators disable all LLM-related features at once – a critical requirement for enterprise deployments where AI usage needs explicit approval.

// Register a custom AI provider in WordPress 7.0
add_action( 'init', function() {
    if ( function_exists( 'register_ai_provider' ) ) {
        register_ai_provider( 'my-local-llm', [
            'label'       => 'Local Ollama Instance',
            'endpoint'    => 'http://localhost:11434/api/generate',
            'auth_type'   => 'none',
            'capabilities' => [ 'text-generation', 'summarization' ],
        ] );
    }
} );

The Connectors screen also supports non-AI providers as of RC1 (#GB-76722), turning it into a general-purpose external service registry.

Refreshed Admin UI and Visual Revisions

The wp-admin dashboard gets a new default color scheme – cleaner, flatter, and more consistent with the block editor’s visual language.

Cross-document view transitions now animate navigation between admin screens, replacing the hard page reloads that have defined wp-admin since its inception. The effect is subtle but noticeable: clicking from Posts to Pages feels like moving within an application rather than loading separate HTML documents. Visual Revisions take the existing revision comparison and add a side-by-side rendered preview, so editors can see exactly how a paragraph reflow or image swap changed the page layout without reading raw diffs. The revision sidebar in RC1 also shows changed block attributes, making it possible to spot a modified CSS class or alignment setting at a glance.

New Blocks, Responsive Controls, and Pattern Editing

WordPress 7.0 ships Breadcrumbs and Icons as new core blocks.

The Navigation block got a significant rework. Overlay menus are now template parts, meaning you can design separate mobile navigation overlays with custom breakpoint triggers. The Heading block introduces level-based variations (H1 through H6 as distinct block types in the inserter), which simplifies programmatic page hierarchy control. The Cover block accepts video embeds as backgrounds – a feature that eliminates the need for third-party hero section plugins on most sites. Grid layouts are responsive-enabled, and the Gallery block now includes lightbox support natively.

Responsive editing controls let you hide or show any block based on screen size. This is different from CSS display: none – the blocks are conditionally rendered, which means they do not add to the DOM on devices where they are hidden. For stores where INP optimization matters, fewer DOM nodes on mobile directly translates to faster interaction times.

Pattern editing received a dedicated Spotlight mode that isolates the pattern content you are working on, dimming surrounding elements. Content-only interactivity lets template authors lock down design elements while exposing only text and media slots to content editors. The contentOnly mode is now opt-out rather than forced, and a tree view for Button and List blocks makes nested structures easier to navigate.

Client-Side Media Processing

Image resizing and compression now happen in the browser before upload.

This shifts CPU-intensive operations off the server and onto the client, which is a significant change for shared hosting environments where PHP memory limits and execution timeouts frequently break large image uploads. The browser-based pipeline supports modern formats like AVIF and WebP natively, applies compression algorithms that were previously only available through server-side libraries, and generates thumbnails without a single PHP process. Existing media in the library can also be reprocessed client-side. Plugin authors building on the media pipeline should note that RC1 moved client-side media to a plugin-only feature (#GB-76700), meaning it ships in Core but stays behind a feature flag until 7.1.

Sites that already handle WebP conversion at the Nginx level will still benefit from the client-side approach for initial compression before the file ever hits the server.

Developer API Changes Worth Tracking

PHP-only block registration with auto-generated inspector controls is production-ready.

This means you can define a block entirely in PHP – no block.json, no JavaScript build step – and WordPress auto-generates the sidebar controls based on your declared attributes. For developers who structure plugins with OOP patterns, this fits naturally into a class-based architecture where blocks are registered inside service providers.

// PHP-only block with auto-generated controls
register_block_type( 'myplugin/notice-box', [
    'attributes' => [
        'message' => [ 'type' => 'string', 'default' => '' ],
        'level'   => [ 'type' => 'string', 'enum' => [ 'info', 'warning', 'error' ] ],
    ],
    'render_callback' => function( $attrs ) {
        $level = esc_attr( $attrs['level'] ?? 'info' );
        $msg   = esc_html( $attrs['message'] ?? '' );
        return "<div class="notice-box notice-{$level}">{$msg}</div>";
    },
] );

Block Bindings now support pattern overrides for custom dynamic blocks, extending what was previously limited to core blocks. The DataForm component ships a new combobox control and validation support across all control types. DataViews gets an activity layout and groundwork for registering third-party content types. CodeMirror jumps to 5.65.40, which resolves several extension compatibility issues that affected custom code editor implementations.

The Font Library screen is enabled for all themes in 7.0, not just block themes. Any site can now browse, install, and manage WordPress fonts from a dedicated admin interface. This is a notable shift from the previous approach where font management was theme-dependent.

Site Health gains an OPcache section under Server info (#63697), exposing cache hit rates and memory usage directly in the dashboard. Developers maintaining production WordPress installations can finally check OPcache status without SSH access or custom debug plugins.

How to Test RC1 Safely

RC1 is not for production sites.

The fastest way to try it is WordPress Playground – a browser-based sandbox that runs the full 7.0 build with zero setup. For local testing, WP-CLI handles the upgrade with a single command: wp core update --version=7.0-RC1. The WordPress Beta Tester plugin works as well if you prefer a GUI approach. Report issues to the Alpha/Beta support forum or file Trac tickets directly if you can write reproducible steps.

Plugin and theme authors should finalize compatibility testing during the RC phase and update the “Tested up to” field in their readme to 7.0. The hard string freeze is in effect, which means all translatable strings are locked and localization teams can begin their work.

What This Release Signals for the WordPress Roadmap

WordPress 7.0 is the largest feature release since the block editor launched in WordPress 5.0.

Real-time collaboration, AI integration at the Core level, and client-side media processing represent three distinct bets on where content management is heading. The AI Connectors screen alone opens a surface area for plugin development that did not exist six months ago. The responsive block visibility controls solve a problem that previously required custom CSS or JavaScript workarounds. The fact that RTC ships opt-in and client-side media stays behind a feature flag shows the release team is balancing ambition with stability – both features will likely become defaults in 7.1 after a cycle of production feedback.

April 9 is the target date. Test early, file bugs, and update your plugins.

Често задавани въпроси