An AI coding agent working on a WordPress plugin or theme is going to make changes you didn’t ask for, run a migration that goes wrong, or generate a whole block theme you’ll throw half of away. None of that is a problem on a local site you can rebuild in seconds. It’s a serious problem on a shared staging server or, worse, production. This lesson sets up Studio, Automattic’s free local WordPress development app, as the disposable environment every other lesson in this course assumes you have running.
A macOS, Windows, or Linux machine with enough disk space for a WordPress install and a browser. No prior local environment tooling required, and specifically no Docker.
Step 1: understand what Studio is (and isn’t)
Studio is a free desktop app from Automattic, downloadable at developer.wordpress.com/studio. It’s built on the same WebAssembly PHP engine that powers WordPress Playground, which is why it spins up a working WordPress site in seconds rather than the minute-plus you’d wait for a Docker-based stack to pull images and boot containers.
A different company makes a similarly-purposed local WordPress app called “Local by WP Engine.” It’s a real, separate product from a different vendor. This lesson is specifically about Studio, made by Automattic.
As of this writing, Studio’s download page offers builds for macOS, Windows, and Linux. Platform support for local development tools does shift over time, so confirm what’s currently offered on the download page itself before you commit to it as your only environment.
Step 2: install Studio and create a site
# Context: there's no CLI step here, Studio is a desktop app,
# this is just the shape of what you now have running locally
Site name: ai-agent-sandbox
Local URL: http://localhost:8887 (port varies per site)
wp-admin: http://localhost:8887/wp-adminEvery Studio site gets its own local URL and its own isolated WordPress install, files included, so you can run several sandboxes side by side without them touching each other.
Step 3: why this matters more when an agent is doing the editing
A human developer making a risky change usually pauses, at least a little, before
running a destructive migration or overwriting a theme file. An AI coding agent
doesn’t have that instinct built in unless you build it in. It will happily generate
and apply a database schema change, register a custom table, or rewrite a theme’s
functions.php in one pass, because you asked it to move fast.
That’s fine, as long as “fine” includes an environment where undoing it costs nothing. Studio sites are disposable by design: delete one and recreate it from scratch in under a minute. Treat that speed as a feature you actively rely on, not just a nice side effect. If an agent’s change makes the site unusable, the right response is usually “delete this site and start the last Blueprint again,” not “spend twenty minutes manually reverting.”
Step 4: capture a reproducible starting point with a Blueprint
Studio supports Blueprints, a way to bundle a theme, a set of plugins, demo content, and site settings into a single reusable definition. Instead of manually reinstalling the same three plugins and re-creating the same test content every time an AI agent’s changes leave a site in a state you don’t want to keep, spin up a fresh site from the Blueprint instead.
// File: my-agent-sandbox-blueprint.json
{
"landingPage": "/wp-admin/",
"preferredVersions": {
"php": "8.3",
"wp": "latest"
},
"features": {
"networking": true
},
"steps": [
{ "step": "login", "username": "admin", "password": "password" },
{ "step": "installTheme", "themeZipFile": { "resource": "wordpress.org/themes", "slug": "twentytwentyfive" } }
]
}This is illustrative of a Blueprint’s shape (Blueprints are a WordPress Playground concept Studio builds on), the exact steps you’ll want depend on your own baseline plugin set. The point isn’t memorizing this schema, it’s having any one-command way back to a known-good starting point, so an agent’s mistake is never more than a recreate away from undone.
Step 5: test it
Confirm your sandbox actually behaves like a real WordPress install before you point an AI agent at it.
Studio can push or pull changes between a local site and a connected WordPress.com or Pressable production site. That’s a genuinely useful feature for a human developer promoting finished work. It is not something you want an AI agent doing on your behalf mid-task. Treat sync as a manual, human-initiated action you run yourself after reviewing what changed, never a step you describe to an agent as part of its workflow.
Recap
Studio gives you a fast, disposable, Docker-free local WordPress environment built on the WordPress Playground engine, exactly the kind of environment an AI coding agent needs since it will make changes faster and more casually than a human would. Blueprints turn “start over” into a one-step operation, and Studio’s sync-to-production feature stays a manual, human-only action, never something an agent runs itself. With a sandbox running, the next lesson connects Claude Code, Cursor, and Claude Cowork to it.
Resources & further reading
- WordPress Studio, developer.wordpress.com
- WordPress Playground documentation, wordpress.github.io
- Blueprints reference, wordpress.github.io