I have spent over a decade wrestling with local development environments. XAMPP and MAMP first, then the Docker-heavy setups of Lando and Local, and the friction was always there. It usually showed up when I only wanted to confirm a bug or test a snippet. That is why the recent updates to WordPress Studio caught my attention. Studio runs on WordPress Playground, and it is finally closing the gap between GUI convenience and having the terminal available.
Automattic shipped two updates for WordPress Studio: a standalone CLI module on npm and direct phpMyAdmin access. If you skipped Studio because you did not want another desktop app in the way, it is worth another look.
Studio CLI on npm
If you work mostly in the terminal, being pushed back into a GUI is a bottleneck. The standalone CLI removes it. Install it globally with npm and you can skip the desktop interface entirely. That is about more than preference: it buys you environment parity and something you can script.
Because it ships as an npm package, it drops into deployment scripts or a CI pipeline. You can spin up a fresh local instance for an automated test run without touching a mouse. And if you run AI coding agents, they can call these commands to manage local environments themselves.
# Install WordPress Studio CLI globally
npm install -g wp-studio
# Or run it once without installation
npx wp-studio site createIf you already have the desktop app, there is no second install to do. Open Preferences and flip the “Studio CLI for terminal” toggle. They also added a dark mode. Small thing, but a welcome one during a late-night refactor.
phpMyAdmin, built into the app
Everyone has had a transient get stuck, or a plugin’s custom table start behaving oddly, and needed to look at the raw rows. Opening a separate database client, sorting out the port, hunting for credentials: that is time gone. WordPress Studio now opens phpMyAdmin straight from the Overview tab.
It earns its place when you are debugging a schema issue or running a one-off SQL query and do not want to load a heavy external client. One click and you are in the database. Compare that to exporting a SQL dump so you can read a single row.
I wrote earlier about how WordPress Playground is changing local development. These updates come out of that same move toward lighter, browser-based execution environments.
Where each one fits
The CLI and the desktop app work together rather than replacing each other. They stay in sync, so you can create a site in the terminal and then open it in the GUI when you want a visual preview. Most of us will end up splitting the work that way: the CLI for the heavy lifting and the automation, the GUI for quick checks and phpMyAdmin.
That also lowers the cost of spinning up an environment to patch Core or test a community plugin. Full package details are on the official npm page, and bugs go on GitHub.
If this Studio setup is eating your dev hours, I can take it off your hands. I have been working with WordPress since the 4.x days.
Worth the install
Dropping the GUI requirement and putting the database tools inside the app deals with the two things people complained about most: bloat and friction. That is enough to put Studio back on my shortlist for local work. For more on the command set itself, start with my earlier post on Studio CLI automation.
