WordPress.com just dropped a massive update, and specifically, the WordPress AI Assistant is now an opt-in feature on every single paid plan. Consequently, whether you are on a Personal, Premium, Business, or Commerce plan, you no longer have to wait for “Enterprise-level” access to use the integrated writing and design tools. This marks a significant shift in how the platform treats AI—moving it from a niche premium perk to a core component of the site-building stack.
Building Locally with WordPress Studio Code
While the plan updates are great for users, the real noise is coming from the terminal. Studio Code has launched in beta as a coding agent built specifically for the WordPress ecosystem. If you have ever wrestled with local environments or “Invalid Content” markup errors from generic LLMs, this tool is actually designed to solve those bottlenecks. Furthermore, it validates markup against the block editor’s schema before it even hits your database.
Specifically, you can run the CLI to generate blocks, themes, and entire site structures using natural language. It’s not just a wrapper; it’s an agent that captures its own screenshots to spot layout regressions. Specifically, for those who live in the terminal, the workflow looks like this:
# Install the Studio CLI globally
npm install -g @wordpress/studio-cli
# Fire up the agent
studio code "Build a portfolio site with a dark mode toggle and a custom post type for Case Studies"Why This Beats Generic Coding Agents
Generic agents often output “hallucinated” block attributes that break the editor. In contrast, Studio Code is site-aware. It understands your local configuration and current theme. Consequently, you spend less time refactoring broken markup and more time shipping. However, keep in mind this is still in beta, so I wouldn’t recommend syncing a massive production database without a solid backup strategy via WP-CLI first.
If you’re interested in how this fits into the bigger picture of core updates, check out my thoughts on WordPress 7.0 development and the AI client debate.
A New Theme for the “Micro-Blogging” Era
WordPress.com also shipped a new theme focused on short-form social-style blogging. The goal here is portability. Instead of being locked into an algorithmic feed on a third-party platform, every update is a real post on a site you control. This allows for replies to be saved as native comments. Specifically, it uses a simplified “Compose” flow that feels like a social app but keeps the data RSS-friendly and exportable. For more on optimizing theme logic, see my guide on navigating PHP versions in AI development.
Look, if this WordPress AI Assistant or local CLI stuff is eating up your dev hours, let me handle it. I’ve been wrestling with WordPress since the 4.x days.
Reliability and Fixes
Beyond the shiny new tools, several polish updates were shipped. Specifically, audio blocks in the Reader now display the correct duration immediately, and the “Contact Us” routing has been refactored to point directly to in-app help. These are the types of small “gotchas” that improve the overall UX for non-technical clients.
