WordPress 6.9: Notes Lands, and the Abilities API Opens the Agent Door

The collaboration gap we have flagged for years started closing on December 2. The content teams drafting in Google Docs and pasting into WordPress, because the CMS could not host a conversation about its own content. The workflow indignity we have documented across three platform generations. WordPress 6.9 ships Notes. Block-level editorial commenting in core. The comment attached to the paragraph it concerns. The thread resolved where the work lives. The mention that pulls a colleague into the draft.

It arrives alongside the release’s strategic sleeper, covered at length below, because almost nobody else will. The Abilities API. A standardized registry that exposes WordPress capabilities (what a site can do: its queries, its actions, its services) to code. And, pointedly per the project’s own framing, to AI systems.

A collaboration feature the editors have waited a decade for, and hookup architecture for the agent era, in the same December release, from a project whose year we have tracked with honest wariness. Three jobs, then. The feature, assessed from the chair that owns editorial experience. The sleeper, read alongside our protocol coverage. And the year-end platform note the release itself argues better than any editorial could.

Notes, from the editorial chair

The feature, honestly. Block-level commenting covers the core review conversation. The feedback on the draft, threaded at the content it concerns, with resolution states. It lands as a v1 with a v1’s edges: young notification plumbing, an early workflow-integration surface, and a roles-and-permissions tier that will mature over releases per the standard core rhythm.

What it is not, and the expectation-setting is our job. Real-time co-editing remains the announced 7.0 destination. The Google-Docs-grade simultaneous editing that phase three of the decade-old Gutenberg roadmap has always pointed toward is the next mountain. Notes is the reviewing half of collaboration arriving first, and sites should plan accordingly.

The adoption advice is unchanged from every change-management piece we have written. The doc-then-paste pipeline finally has an expiration path, and workflow habits will outlast the feature gap by quarters. The teams whose entire review culture lives in Docs will not move because a feature shipped. They will move when the workflow is retrained, the templates updated, and the pilot group’s experience shared. The muscle-memory project the 5.0 era taught, at review-workflow scale.

Retraining is the actual project. Budget it. A pilot editorial team this winter. The workflow docs updated. The wider rollout against 6.9’s maturing point releases. And the Docs pipeline formally retired on a named date, rather than left to linger as the shadow workflow governance experience says it will otherwise become.

The Abilities API and the agent era

• What it is, exactly: a core registry where capabilities are declared with names, schemas, and permissions. The site’s operations (query this content, perform this action, call this service) become discoverable and callable through a standard surface. No more ad-hoc plugin-API sprawl for hookups to navigate.

• Why it reads as agent-era architecture: this is the world’s largest CMS formalizing how outside systems, agents included, find and call what a site can do. The composability question from our 2024 MCP coverage, the N-times-M collapse, answered at the platform layer by the platform with the most sites to expose. The protocol watch from October, advanced. And the abilities-to-MCP bridging already visible in the ecosystem’s early work, which is exactly the convergence our protocol coverage predicted rewards watching by name.

• The governance inheritance, applied on day one: a registry of what a site can do is also the enforcement point for what an agent may do. The permission mapping and audit logging. The expose-and-lock approach from our earlier capability coverage, now with its natural home. The copilot-configuration assignment of 2023 gains its structural layer. Sites should treat the Abilities surface as governed plumbing from its first declared ability, not after its first incident.

The year-end platform note

The note the release writes itself, recorded with the governance series’ full context. After the turbulence of 2024-25 (the dispute, the contribution pullbacks, the slowed rhythm) a substantive release shipped on schedule. The collaboration phase of a decade-old roadmap visibly executing. A forward-looking hookup architecture landing as quiet plumbing. And the compatibility promise holding throughout, which argues the resilience case in the only currency that counts. Delivery.

The watchfulness stands unrevised. Governance remains unresolved, the tempo remains uncertain, and the annual update remains on the calendar. The both-things reading we hold at every platform juncture holds here. The ecosystem’s health is measured in releases like this one. Its risks are measured in the structures around them. The sites we run enter 2026 with current maps of both.

The project that spent the decade absorbing the block paradigm now ships the collaboration and hookup layers that paradigm was always building toward. On schedule, mid-weather. That is the promise-keeping behavior we have learned to weight heavily.

Closing out 2025

The year-end paragraph, in the tradition, for the year the agent era got practical. 2025 opened with a packaged Drupal contesting its lost tier and closes with WordPress shipping the registry agents will call. Between them, the answer engines got their date, May 20. The crawl economy got its prices, July 1. The zero-click numbers got published, September. The machine customers arrived, October. And the capacity dashboards learned to count visitors who aren’t people, November.

A year in which the topics we have covered for nearly two decades converged on the same underlying event. The platforms and the economics. The measurement, the governance, the craft. The web acquiring a second kind of visitor, and the institutions of the first one learning, deliberately or by default, to serve both.

The method that navigated it is unchanged and, per our whole history, unchangeable. Instrument first, position deliberately, govern what you expose, and own what matters. Write it all down where next year can find it. The blog turns twenty in March. See you in January: piloted, governed, and in writing.