WordPress.com just dropped the WordPress AI Assistant right into the core editor experience. The market is flooded with “ChatGPT-in-a-sidebar” plugins, but this one is different because it actually has access to your site’s internal state. It generates text, sure, but it also manipulates blocks, adjusts layouts, and works inside your Media Library.
Why context awareness changes the workflow
The main bottleneck with standalone AI tools has always been the “manual labor” of implementation: you prompt a tool, it hands you code or text, and then you have to figure out where to paste it without breaking your CSS grid or theme hierarchy. The WordPress AI Assistant removes that friction by working inside the editor itself. It understands your content structure and can take actions like “Add a testimonials section below this block” without you touching a single line of PHP.
It also uses Google’s Nano Banana (Gemini) models for image generation right inside the Media Library. That means you can generate, edit, and swap visuals, like turning a stack of pancakes into waffles, without leaving your dashboard. It’s a clean integration that respects your brand’s visual consistency.
Technical specs: block themes and logic
One technical caveat worth knowing: this tool is optimized for Block Themes (Full Site Editing). If you’re still running a legacy Classic theme, the assistant won’t show up in your editor. You’ll still get the AI image features in the Media Library, but the layout manipulation needs the modern block-based architecture. For more on how to prepare your site for these integrations, check out my guide on AI project evaluation.
Translating natural language to CSS
When you tell the WordPress AI Assistant to “make this section feel more modern and spacious,” it isn’t guessing: it translates that prompt into specific block attributes. Seeing how AI handles these requests is genuinely interesting for developers. A “spacious” section, for instance, usually turns into a refactor of padding and gap properties like this:
/* What the AI Assistant essentially applies to the block container */
.wp-block-group.is-modern-spacious {
padding: clamp(2rem, 8vw, 5rem);
gap: clamp(1.5rem, 5vw, 3rem);
line-height: 1.6;
letter-spacing: -0.01em;
}Instead of hardcoding pixels, the AI leans more and more on fluid typography and spacing variables. That avoids the “vibe coding” errors I’ve written about before in security risks and technical debt.
Collaborative AI via Block Notes
One of the most practical features here is the integration with Block Notes. Using the @ai mention, you can ask for fact-checks, headline variations, or content strengthening right inside the collaborative notes system. That turns the AI into a peer reviewer rather than just a generator, so it fits into the existing team workflow instead of disrupting it.
Look, if this WordPress AI Assistant stuff is eating up your dev hours or you’re struggling to migrate your legacy site to a Block Theme to take advantage of these features, let me handle it. I’ve been wrestling with WordPress since the 4.x days.
Summary: the future of integrated building
The WordPress AI Assistant is a clear sign that Automattic is moving toward an “Intelligence First” editor. The real question now is how deeply you want AI integrated into your core stack, not whether to use it at all. If you’re on a Business or Commerce plan on WordPress.com, go to your settings and opt in. It’s a friction-free way to see where the platform is headed without breaking your staging environment.
