WordPress 7.0 Armstrong: Native AI Client, Abilities API, and What Got Cut

WordPress 7.0 “Armstrong” landed on May 20, 2026, six weeks behind its original April 9 target.

Whats actually in the box

The release shifted scope twice during the cycle. Real-time collaborative editing, the headline feature on the roadmap since 2024, was pulled on May 8 and is unlikely to ship before 2027. What did make it into core is a different kind of foundation: a provider-agnostic AI Client, a server-side Abilities API with a JavaScript counterpart, a Connectors hub for managing external AI services, and the first substantial admin redesign since 2013. The version is named after Louis Armstrong, continuing the WordPress tradition of honoring jazz musicians.

Matias Ventura led the release. Contributions came from 875+ developers, including 200+ first-time contributors, across 70+ translated locales.

The AI Client and Abilities API

Core now exposes a wp_ai_client_prompt() PHP function and a matching JavaScript REST interface. The client is provider-agnostic, which means it abstracts the request payload away from any specific vendor. A new Settings -> Connectors screen handles authentication and routing, with presets for OpenAI, Google Gemini, and Anthropic Claude already wired up.

The Abilities API is the deeper change. It is the registry layer that lets plugins declare what they can do in a machine-readable format that any connected model can call. WooCommerce, for example, can register an ability like create_product with a JSON schema for arguments. An AI request can then invoke it directly without bespoke prompt engineering. This is the same pattern that powers WooCommerce MCP exposure, now applied at the WordPress core level.

add_action( 'abilities_api_init', function () {
    wp_register_ability( 'my-plugin/summarize-post', [
        'label'            => 'Summarize a post',
        'description'      => 'Returns a 2-3 sentence summary of a given post ID.',
        'input_schema'     => [
            'type'       => 'object',
            'properties' => [ 'post_id' => [ 'type' => 'integer' ] ],
            'required'   => [ 'post_id' ],
        ],
        'output_schema'    => [ 'type' => 'string' ],
        'execute_callback' => function ( $args ) {
            $post = get_post( $args['post_id'] );
            return wp_ai_client_prompt( 'Summarize: ' . $post->post_content );
        },
    ] );
} );

A separate AI plugin (not bundled with core) layers user-facing editorial helpers on top: image generation and editing, title suggestions, excerpt drafting, and alt-text proposals. The plugin reads from registered abilities, so adding a new connector instantly makes new capabilities available throughout the editor without rewiring anything. Teams that previously stitched together bespoke integrations such as local LLMs for product recommendations now have a standard surface to plug into.

Client-Side Abilities and the Command Palette

A JavaScript companion package called Client-Side Abilities mirrors the server registry in the browser. It ships with built-in UI hooks that feed directly into the Command Palette. The Command Palette itself got a dedicated Cmd+K / Ctrl+K icon in the admin bar, accessible from anywhere in wp-admin, not just the editor.

Hybrid abilities are also supported, where part of the work runs in PHP and part runs in JavaScript, with the registry routing between them.

The dashboard redesign

This is the first substantial visual overhaul of wp-admin since 2013. The new color scheme, view transitions between screens, and React-based DataViews replace the classic list tables for posts, pages, media, and users. DataViews eliminates full-page reloads for filtering, sorting, and bulk operations. On a site with 50,000 posts, switching from “all posts” to “published, last 30 days” no longer triggers a fresh request to edit.php; the view updates in place.

Typography management moved to a dedicated Fonts page that works across block, hybrid, and classic themes. Revisions now render visually scrubbable, with change markers that make editorial diffs readable without opening the full comparison view.

New blocks and design tools

Four blocks are new: Gallery with a lightbox slideshow mode, Heading (a refined replacement for the existing one), Breadcrumbs, and Icons. The Breadcrumbs block matters for SEO because it removes the need for plugins like Yoast or Rank Math to inject structured navigation. Schema markup for breadcrumbs is generated automatically when the block renders on the page.

Responsiveness controls now let you hide or reveal individual blocks per device viewport without writing custom CSS or relying on theme hooks. Block-level custom CSS is editable directly in the inspector, so you can scope styles to a specific block instance without touching theme.json or a stylesheet.

Developer toolbox

PHP-only block registration is the headline developer change. Calling wp_register_block_type_from_metadata() with a block.json that includes a render.php file now auto-generates inspector controls for attributes declared in the schema. The JavaScript build step is no longer mandatory for blocks that do not need interactivity. For teams maintaining many small blocks across client sites, this cuts the toolchain footprint substantially. Cleanly structured plugin code benefits the most here, since auto-registration assumes a predictable metadata layout.

The Site Editor exposes a new routing API and a wordpress/boot package that lets plugins register custom pages inside the site editor without hijacking admin menus. Route validation hooks let you guard URLs based on capabilities, post types, or arbitrary conditions. PHP 7.4 support is dropped, with PHP 8.1 as the new minimum and PHP 8.3 recommended, which makes strict PHP 8.x exception handling a hard requirement for plugin authors.

What to test before updating

Custom blocks registered with incomplete metadata can break under the new auto-controls layer. Plugins that injected admin notices via legacy DOM positions may render in unexpected locations under the redesigned dashboard. REST API consumers should retest schema responses; a handful of internal endpoints changed their _links structure. Stage the upgrade first, then sweep the Field Guide for the 419 Trac tickets and 486 Gutenberg fixes that touch custom integrations.

The collaboration question

Real-time co-editing is the most-asked-about absence. The CRDT sync engine, Notes with inline comments, and presence indicators were being merged from earlier release candidates but failed stability review on May 8 and were cut from the final build.

The pulled code stays in the Gutenberg plugin and will keep iterating there until a future core release picks it back up.

WordPress 7.0 is a platform release more than a feature release. Adopt the AI Client only after writing a clear data-handling policy for whichever provider you connect, and treat the dashboard redesign as a UX change worth a team walkthrough before rolling it out to editors site-wide.

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