I have set up local WordPress environments more times than I can count: download the stack, configure the database, import the site, fix the URLs that broke in the move — friction every single time, before a single pixel moved. So when WordPress.com announced a rebuilt WordPress Studio workspace on November 4, 2026, with an AI agent sitting at the centre of the whole thing, I paid attention. This is not another AI demo. It is the tool WordPress itself ships for building sites on your own machine, and it now works the way a growing number of us actually want to work: you describe the site, and it builds a first version while you watch.
What actually shipped on November 4
WordPress Studio is the free desktop app from WordPress.com for running WordPress locally — macOS, Windows and Linux. Before this release, it was mostly a convenient local environment: spin up a site, build it, push it live. The new workspace reorganises the app around a chat with an AI agent. You describe the site you want, the agent builds a first version, and you watch it change in a live preview sitting next to the conversation.
The agent itself is not brand new. It arrived in Studio as a beta back in August 2026. What changed on November 4 is the app around it: sites and chats now live in one sidebar, there is a single Settings window, and you get considerably more control over how the agent works and where its changes go.
It is a free download from developer.wordpress.com/studio; updating an existing install gets you the new workspace.
Starting a site from a conversation
The flow is deliberately simple, and it is the part I think most people will actually use. Ask for a site and Studio shows you four looks to choose from, then four layouts in the style you picked. If you describe the design in your first message — the colours, the mood, the kind of business — it skips those questions and gets on with it.
The detail that matters most is what happens to those design choices afterwards. Studio saves them to a file called DESIGN.md in the site folder, and later chats follow it. That is a small thing with a big consequence: the agent keeps to the same design system as you keep working, instead of reinventing the header on every third prompt.
Behind the chat is something called WordPress Studio Code, which the announcement describes as "the WordPress harness behind the conversation". In practice that means the agent is not just writing HTML into a void: it checks the blocks it creates against the block editor, and it reviews its own work with screenshots before showing it to you.
Annotate: the feature that fixes bad prompting
If you have ever tried to direct an AI by typing "make the second button bigger" into a chat box, you know the problem: words are a clumsy way to point at things. Studio's answer is a feature called Annotate. It lets you pin notes directly onto elements in the preview and send them to the agent together. You click the thing, write the note on the thing, and the agent knows exactly what you mean.
It is the same idea as the Annotate mode in the WordPress.com AI Editor, brought into the local app. I think this is the most useful feature in the whole release, precisely because it is unglamorous. The hardest part of working with AI builders has never been the generation — it has been the correction loop, the five rounds of "no, the other button". Pointing instead of describing collapses that loop, and it maps onto how people actually talk about design.
Choosing a model — or bringing your own key
If you use WordPress.com AI credits, you choose between three levels: Fast for everyday edits, Balanced for more careful reasoning, and Strong for complex, multi-step builds. Balanced and Strong now run on newer models. You can also use your own Anthropic API key and pick the model directly, and WordPress.com says support for other providers is on the way.
Two honest caveats here. First, the app is free, but the announcement does not say how many AI credits each level uses or what they cost — so check that before you lean on Strong for a big build, or you may find the meter running faster than you expected. Second, bring-your-own-key matters: if you already pay for Claude, you can use the model you trust on your own bill, instead of buying into a second credit system.
Under Settings, then Instructions, you can add custom instructions that apply to every new chat — house rules like "use British English" or "never add a plugin without asking". Set it once, and every chat inherits it.
Publishing: push from local, or edit the live site
Studio could already pull a connected WordPress.com or Pressable site down to your computer and push changes back up. The agent can now work either way: it can build locally and push when you are happy, or you can point it at your live site and let it make changes there directly.
The second option is convenient, and I would be careful with it. Changes landing on a live site without a local check first is exactly the kind of thing that feels fine until the one time it is not. For anything that matters, the safer habit is unchanged: build locally, or on a staging site, review it, and push.
Preview links still let you share a local site with someone for feedback before it goes live — send the link, get the notes, fix them in the chat.
Using Claude Code, Codex or Cursor instead
If you already have an AI coding tool you like, Studio does not force you to switch. It lets you connect Claude Code, Codex or Cursor through the Model Context Protocol (MCP), with the setup steps under Settings, then MCP, and a support page for MCP on Studio.
There is also a command line interface. Install it, then run studio code to chat with the agent in your terminal, or studio ui to open the full workspace in a browser. The terminal option is the one I would reach for when I am already deep in a project and do not want another window.
Smaller things round out the release: you can pin sites and resume recent chats from the sidebar, press Command-K (or Ctrl-K on Windows and Linux) for the command palette, and the appearance settings offer light and dark themes, an accent colour, tint intensity and contrast.
What this means if you build with Elementor
Here is the honest part, and it matters for readers of this site. WordPress Studio's agent builds with the block editor. It checks its blocks against the block editor. Elementor is not in that loop. If your workflow is Elementor-first — and for many of us it is — Studio's agent is not going to lay out your Elementor pages for you.
But that does not make it useless to Elementor builders. It makes it a different tool in the chain. Here is how I would actually use it: for the fast first draft. A client call ends, and instead of a blank local install, I have a working WordPress site with the structure, the pages and the content shape in place within minutes. Then the real build — the Elementor layouts, the theme builder templates, the custom styling — happens on top of a site that already exists, instead of starting from zero. The agent handles the scaffolding; I handle the craft.
It is also genuinely useful for the parts of a project that are not page design at all: spinning up a local copy of a client's live site to test a plugin update, trying a content structure before committing to it, or giving a junior developer or a non-technical client a way to start a site without first learning what a local environment is.
WordPress is moving the same way in core: the AI Team's proposal for version 7.3 would make WordPress natively compatible with AI agents, with an OAuth sign-in flow instead of manual setup. Studio's new workspace is the local-development half of that same story: the agent is becoming a normal part of how WordPress sites get made, not an add-on.
The limits I would not skip
A few things to keep in mind before you rearrange your workflow around this. First, the agent is only as good as its model and its instructions — the DESIGN.md file helps, but a long build will still drift, and you will still need to review. Second, the credit costs are unstated, so a heavy week of Strong builds could surprise you; check pricing before you commit a client project to it. Third, the live-site editing mode is a loaded gun: convenient, fast, and exactly wrong for anything you cannot afford to break in public. And fourth, this is a block-editor workflow. If your deliverable is an Elementor build, Studio gets you to the starting line faster — it does not run the race for you.
None of that is a reason not to try it. It is a reason to try it on a practice site first, with a small brief, and see where it helps and where it gets in the way.
Conclusion
The new WordPress Studio workspace is not a revolution, and it does not pretend to be one. It is something more useful: the local WordPress workflow, rebuilt around the way AI-assisted building actually works now — chat first, live preview beside it, a design file that keeps the agent honest, annotation instead of vague prompts, and a straight path from your machine to the live site. It is free, runs on every major desktop platform, and meets you in the chat window, the terminal, or your existing Claude Code setup.
For WordPress developers and freelancers, the question is not whether AI is coming to local development — it is already here, inside the official tool. The question is how you use it: as scaffolding that gets you to the real work faster, with your judgement firmly in charge. Download it, point it at a small brief, and see what it hands you back. Then do what you do best: make it properly good.
FAQ
Is WordPress Studio really free?
Yes — a free download from developer.wordpress.com/studio for macOS, Windows and Linux. The AI features use WordPress.com AI credits or your own Anthropic API key, so the app costs nothing but the AI usage may. Check the per-level credit cost before a big build; the announcement does not state it.
What changed versus the August agent beta?
The November 4, 2026 release rebuilds the app around the agent: sites and chats in one sidebar, one Settings window, a DESIGN.md file for design consistency, the Annotate feature, and more control over models and where changes go.
Can the agent build my site with Elementor?
No — it works with the block editor. Elementor builders can still use Studio for fast scaffolding, local copies of live sites, and testing, then do the finished design in Elementor.
What is the DESIGN.md file?
Studio saves your design choices to a DESIGN.md file in the site folder. Later chats read it and follow the same design system, so the agent stays consistent instead of restyling things on every prompt.
Can I use Claude Code, Codex or Cursor with Studio?
Yes, through the Model Context Protocol (MCP) under Settings, then MCP. There is also a CLI: studio code chats in the terminal, studio ui opens the workspace in a browser.
Is it safe to let the agent edit my live site?
It can, but I would not. Build locally or on staging, review the result, and push when you are happy.
