From Real‑Time Collaboration to a Native AI Future
WordPress 7.0, code‑named Armstrong, arrives after weeks of delay with a clear message: the future of the CMS is powered by native AI integration, not by the originally hyped real‑time collaboration. While real‑time collaboration was expected to define this release, it was ultimately deprioritized in favor of building AI infrastructure directly into WordPress Core. This makes WordPress 7.0 AI capabilities a foundational layer rather than a bolt‑on feature. For site owners, that shift is significant. Instead of relying on a patchwork of third‑party AI plugins, basic AI workflows can now tap into core tools that are provider‑agnostic, centrally managed, and designed to evolve. In practice, this release is less about a single flashy feature and more about equipping WordPress to support AI‑driven publishing, design, and automation over the long term.
The Four Pillars of AI Infrastructure in WordPress
WordPress 7.0 introduces four core components that together form the AI infrastructure WordPress will build on: the WP AI Client, the Client‑Side Abilities API, the AI Connectors screen, and the Connectors API. The WP AI Client is the central interface that lets plugins communicate with generative models while remaining provider‑agnostic. The Client‑Side Abilities API extends AI into actions inside the browser—such as navigating the admin, inserting blocks, and running commands—so AI can participate in real workflows rather than just producing text. The AI Connectors screen gives site owners a single place in Settings to configure external AI providers, while the Connectors API standardizes how those providers are registered, authenticated, and discovered. Together, these building blocks shift WordPress from being a passive destination for AI‑generated content to an active environment where AI tools can operate natively.
WP AI Client: Native AI Integration Without Plugin Sprawl
At the heart of native AI integration is the WP AI Client, which routes AI requests through WordPress itself. Instead of each plugin building and maintaining its own integration for every provider, developers can integrate once with the WP AI Client and let WordPress handle model selection and request routing. The AI infrastructure WordPress provides includes model preference ordering, feature detection, advanced configuration options, and a Prompt Builder class, allowing developers to choose models based on capabilities, cost, or efficiency. For site owners, this means fewer overlapping plugins and less duplicated configuration. You can connect your preferred providers via the central Connectors screen, and any compatible plugin can use them without extra setup. The result is a cleaner, more maintainable AI stack, where WordPress Core becomes the stable hub for AI instead of each plugin reinventing the wheel.
Abilities, Connectors, and What Site Owners Can Do Today
The Client‑Side Abilities API and Connectors layer turn WordPress into an environment that AI agents and automations can actually act within. Because the Abilities API is integrated into the WP AI Client, developers can chain AI‑powered actions—like generating content, inserting specific blocks, adjusting layouts, or triggering SEO routines—in fluid workflows. The Connectors screen centralizes API keys and provider metadata so you no longer have to hunt through individual plugin settings to manage AI services. For site owners, this infrastructure means you can start leveraging WordPress AI features—such as content assistance, intelligent block operations, or automated site management—through compatible plugins without installing dedicated AI connectors for each service. Over time, expect more plugins to tap into this shared AI layer, enabling complex publishing, design, and agent‑based workflows that run natively inside WordPress rather than depending on external tools and manual copy‑paste.