Short answer: WordPress Studio’s new agentic desktop experience is now available as a public beta. It combines your local WordPress sites, a chat with the Studio Code AI agent, and a live site preview in one window. New users see the experience by default; existing users can enable Studio → Beta Features → New Studio Experience. Studio Code is currently free during beta, but a WordPress.com login and a payment method are required for the hosted AI access.[1][5]
Quick caution: Build and test locally first. Treat every AI-generated plugin, theme, database change, and deployment as untrusted until you review it, back it up, and verify it on staging.
WordPress Studio agentic beta: quick setup
- Download WordPress Studio for macOS, Windows, or Linux from the official Studio page.[2]
- Install the app and create or open a local WordPress site.
- Sign in with a WordPress.com account.
- Existing users: open Studio → Beta Features and enable New Studio Experience. New users should see the new interface automatically.[1]
- Add a payment method to your WordPress.com account. WordPress says it is required to prevent abuse and that Studio Code is currently free in beta.[5]
- Open your site, start a fresh Studio Code chat, and give the agent one small, testable task.
- Review the live preview and files before asking for the next change.
What changed in the new WordPress Studio experience?
The redesigned desktop app places three panels side by side: your sites, a Studio Code conversation, and a live WordPress preview. The agent can work on a real local installation rather than returning a detached code snippet.[1]
According to the official Studio Code documentation, the agent can create and edit files, run commands and WP-CLI operations, take screenshots, deploy previews, and publish a site when instructed.[5] That makes it useful, but it also means vague prompts or premature deployment instructions can have real consequences.
Existing Studio users do not need to re-import their local sites when switching to the new experience; WordPress says current local sites carry over automatically.[1]
A safe first-project prompt you can copy
Use a controlled prompt like this instead of asking the agent to “redesign everything”:
Work only on this local WordPress site. Before changing anything, list the files, plugins, theme, and WordPress version that may be affected. Create a simple homepage hero using native blocks. Do not install packages, change users, touch credentials, run destructive database commands, sync, deploy, or publish. After the change, show the files changed, explain each change, and check the mobile and desktop preview. Stop and ask for approval before any additional action.
This prompt is not a security boundary, but it creates a clearer task scope and a review point.
Practical workflow: brief, build, inspect, verify
1. Start with a narrow brief
Specify the page, desired result, existing constraints, and actions the agent must not take. A good first task is one block pattern, one template adjustment, or one small plugin fix—not an entire production migration.
2. Ask for discovery before edits
Have Studio Code identify the active theme, relevant plugins, likely files, and current behavior. If it cannot explain what it plans to touch, the task is not ready to run.
3. Keep production out of the first loop
Studio is designed for local WordPress development. The official docs say you can later sync with eligible WordPress.com or Pressable sites, export work, or share a temporary preview, but permanent publication still requires an appropriate hosting path.[3][4]
4. Review more than the visual preview
A page can look correct while introducing poor HTML, inaccessible controls, slow scripts, insecure code, or brittle CSS. Check:
- changed files and generated code
- mobile, tablet, and desktop layouts
- keyboard navigation and form labels
- browser console and PHP/debug logs
- page title, one clear H1, canonical behavior, and indexability
- plugin/theme conflicts
- backups and rollback steps
5. Deploy only after a staging pass
Take a fresh backup, push to staging, clear relevant caches, test critical forms and user flows, and compare the result with production. Do not let the first AI-generated version become the production version by default.
What can Studio Code do?
The official product and documentation pages describe Studio Code as an agent for building WordPress blocks, themes, plugins, and complete sites using natural-language instructions.[2][5] Its documented workflows include:
- reading and writing files in the site directory
- running commands and WP-CLI
- taking screenshots to inspect its work
- using visual annotations for targeted changes
- creating previews
- working in the desktop app or terminal
- using WordPress-focused tools and context
The Studio product page also describes Studio Sync, cloud-hosted previews, reusable Blueprints, and integrations that can give external coding agents WordPress context.[2]
Cost, account and usage limits
Studio itself is presented as a free local WordPress development tool.[3] Studio Code is currently free in beta, but the official documentation says a payment method is required for the default WordPress.com-backed AI access, and features, capabilities, and usage limits may change.[5]
A WordPress.com account is required for Studio Code’s default hosted access because WordPress.com infrastructure generates responses and manages access.[4][5] The terminal version also documents an option to use your own Anthropic API key, which would create separate provider costs and data-handling considerations.[5]
Do not budget a production workflow around today’s beta limits. Confirm the current terms and limits in the app before committing a client project.
Desktop app versus CLI
Choose the desktop app if you want the three-panel workflow, visual preview, and easier annotation. Choose the CLI if you are comfortable reviewing terminal actions and want a scriptable workflow.
The official Studio page provides desktop downloads for macOS, Windows, and Linux, including Intel/AMD and ARM options where listed.[2] The Studio Code documentation provides terminal options through the Studio CLI or npx wp-studio@latest code.[5]
Safety checklist before every agentic WordPress task
- Use a local copy or staging environment, not the only production copy.
- Take a backup before imports, syncs, database work, plugin updates, or deployment.
- Never paste production passwords, application passwords, private API keys, customer records, or payment data into a prompt.
- Ask the agent to show its plan and affected files before editing.
- Prohibit destructive database commands unless explicitly required and reviewed.
- Review generated PHP, JavaScript, permissions, REST routes, nonce checks, sanitization, and escaping.
- Test forms, checkout, login, search, multilingual pages, redirects, schema, and caching where relevant.
- Keep a rollback path and verify it before publishing.
- Recheck current beta pricing, limits, privacy terms, and model/provider settings.
- Record what the agent changed so a human can maintain it later.
Who should try it now?
The beta is most useful for WordPress developers, agencies, technical marketers, and site builders who already understand local development and can review generated changes. It may also help less-technical users prototype a site, but the ability to run commands and publish means human review is still essential.
For a client or revenue-critical site, use it as an accelerated implementation assistant—not as an unsupervised replacement for backups, staging, code review, security testing, accessibility checks, or production QA.
Frequently asked questions
Is WordPress Studio’s agentic experience available now?
Yes. WordPress announced the redesigned experience as a beta available for everyone to try on August 24, 2026.[1]
Is WordPress Studio Code free?
It is currently free during the beta. WordPress says a payment method is required for abuse prevention and that usage limits and capabilities may change.[5]
Do I need a WordPress.com account?
You can use Studio for local development, but the default Studio Code access requires signing in to WordPress.com. Account-connected features also include previews and supported sync workflows.[3][4][5]
Will enabling the new interface delete my existing local sites?
WordPress says existing local sites carry over automatically when an existing user switches on the new experience.[1]
Can Studio Code publish directly to a live site?
Its documented capabilities include previews, deployment, and publishing workflows, but the available route depends on your host and connection. WordPress.com and Pressable have supported sync paths; other hosts may require an export/import workflow.[3][4][5]
Should I use it directly on a production website?
The safer approach is to build locally, review the changes, test on staging, back up the target, and deploy only after verification. Beta software and AI-generated changes should not bypass normal WordPress release controls.
Sources
[1] WordPress Studio Is Now Agentic — Try the Beta
[2] WordPress Studio
[3] WordPress Studio documentation
[4] WordPress Studio: Frequently asked questions
[5] WordPress Studio Code documentation