Notes from the WordPress performance chat: bridging classic scripts with script modules for the CodeMirror upgrade, memoizing wp_normalize_path, and why Copilot kept reintroducing a PCRE bug that had already been fixed.
WordPress 7.0 may merge the WP AI Client into Core, giving plugins one provider-agnostic API for calling models instead of each shipping its own SDK. Notes on the Connectors keychain, the package size argument, and what it changes for developers.
WordPress 6.9 shipped the Abilities API, and the MCP Adapter is what lets AI agents find those abilities and call them. Ahmad Wael covers flagging an ability for MCP, the two transport methods, custom servers, and keeping permission callbacks tight.
Notes from the January 28 dev chat: WordPress 6.9.1 hits beta on January 29 and ships February 3, 2026, which Trac tickets still need eyes, where Gutenberg 22.4 and the 7.0 release squad fit in, and why a self-contained first ticket rarely is.
WordPress 6.9.1 clears 49 bugs in Core and the Block Editor, with fixes for wp_mail and classic themes. Here is what changed, how to run the update through WP-CLI, and where it fits before WordPress 7.0 in April.
Make WordPress published its AI guidelines: disclose AI assistance, keep contributions GPLv2-or-later, and own the code either way. Includes the AJAX save function AI keeps getting wrong and the version that passes review.
The WordPress 6.9 “Gene” retrospective is more useful than the release notes. Two triage leads in different time zones, too many manual release steps, and contributor pairing that actually worked. Here is what that means if you run client sites on Core.
WordPress 6.9.1 RC1 closes 23 core bugs and 25 Block Editor issues, including the mail function error, the double-escaped class names from the HTML API, and the broken Add Plugins screen. Plus how to test the RC on staging with WP-CLI.
The core team wants the legacy 1024-bit certificates out of the WordPress root bundle before 7.0 ships in April 2026. NIST disallowed those keys in 2013, and CentOS 7, the main reason they stayed, went end of life in mid-2024.
WordPress now has a repository for AI agent skills, starting with wp-playground. It uses the Playground CLI so an agent can mount a plugin or theme, wait for WordPress to be ready, log in, and check its own work in seconds.