The WordPress AI Assistant is now an opt-in feature on every paid WordPress.com plan. Personal, Premium, Business, Commerce: the integrated writing and design tools no longer sit behind “Enterprise-level” access. AI has moved from a premium perk to part of the standard site-building kit.
Building locally with WordPress Studio Code
The plan change matters to users, but the more interesting release is a terminal tool. Studio Code is in beta: a coding agent built for the WordPress ecosystem rather than adapted to it. If you have ever fought a local environment, or an “Invalid Content” error caused by markup a generic LLM invented, that is the problem it goes after. It validates markup against the block editor’s schema before anything reaches your database.
The CLI takes plain language and generates blocks, themes, or whole site structures. It also captures its own screenshots to catch layout regressions, which puts it a step past being a wrapper around a model. If you work in the terminal, the flow 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 like to invent block attributes, and the editor rejects them. Studio Code reads your local configuration and your active theme, so the markup it writes tends to load without a repair pass afterwards. It is beta software, though. I would not sync a large production database into it before you have a WP-CLI backup you have actually restored once.
For how this fits with the bigger core changes, I wrote up WordPress 7.0 development and the AI client debate.
A new theme for the “micro-blogging” era
WordPress.com also shipped a theme aimed at short-form, social-style blogging. The point is portability: every update is a real post on a site you own rather than an entry in someone else’s algorithmic feed, and replies come back as native comments. The simplified “Compose” flow feels like a social app, but the output stays RSS friendly and exportable. On the theme-logic side, I also wrote about navigating PHP versions in AI development.
If the WordPress AI Assistant or the local CLI setup is eating your dev hours, I can take it off your plate. I have been working with WordPress since the 4.x days.
Reliability and fixes
There were smaller fixes too. Audio blocks in the Reader now show the correct duration right away, and “Contact Us” routing points straight at in-app help. Minor stuff, but it is the kind of snag a non-technical client notices first.
