WordPress.com changelog: a Telegram bot and wider Studio Sync
WordPress.com shipped an alpha Telegram bot for managing a site from your phone, opened Studio Sync to Personal and Premium plans, and split MCP read and write tool access per site.
WordPress.com shipped an alpha Telegram bot for managing a site from your phone, opened Studio Sync to Personal and Premium plans, and split MCP read and write tool access per site.
Voice picking used to mean vendor-locked hardware. ElevenLabs voice AI does the same job off an ordinary smartphone, and this covers the WordPress side of it: a cached text-to-speech wrapper, plus the latency and noise problems that sink most builds.
WooCommerce 10.7 is mostly a performance release: the /wc/v4/orders endpoint drops from 271 queries to 132 and checkout loses about 15% of its SQL. It also ships a Fulfillment API beta and moves the Fulfillments namespace, which breaks old use statements.
Jetpack now lets you comp a paid subscription from the Subscribers screen, so gifting access no longer means a custom VIP role and a pile of expiring metadata. Here is what changes, plus the math on Substack’s 10% cut.
WordPress AI Plugin 0.7.0 adds content classification that can stick to your existing terms, context-aware meta descriptions, bulk alt text in the Media Library, and a filter for system instructions.
VLA models put vision, language and motion in one latent space instead of three separate pipelines. Notes on why that unification works, and how action tokenization, diffusion heads and flow matching differ once the model has to output real movement.
The 7.0 release went back from RC to Beta so Real-Time Collaboration data could move out of post_meta and into its own table. Also covers the WP AI Client, pseudo-states in theme.json and the Playground MCP server.
Notes from the April 8, 2026 dev chat: WordPress 7.0 makes the collaboration sync layer provider agnostic, so polling is only the default. What that means for WebSocket providers, CRDT reconciliation and block API v3.
WordPress 7.0 ships three pieces of AI plumbing: the Abilities API for registering what a site can do, the AI Client for provider-agnostic model calls, and the MCP Adapter that exposes both to assistants like Claude.
Notes from the April 8 contributor chat: the AI Client centralizes the transport layer, the Connectors page holds credentials for any service and not just AI, and the MCP adapter is close to 0.5.0.