I’ve spent over a decade wrestling with local development environments. From the early days of XAMPP and MAMP to the Docker-heavy setups of Lando and Local, the friction has always been there—usually when you’re trying to quickly verify a bug or test a snippet. That’s why the latest updates to WordPress Studio caught my attention. This tool, powered by WordPress Playground, is finally bridging the gap between GUI convenience and the terminal power that senior developers actually need.
Automattic recently shipped two major updates for WordPress Studio: a standalone CLI module on npm and direct phpMyAdmin access. If you’ve been avoiding Studio because you didn’t want another desktop app cluttering your workflow, it’s time to reconsider.
Studio CLI on npm: Goodbye GUI, Hello Automation
For those of us who live in the terminal, forcing a GUI into our workflow feels like a bottleneck. The new standalone CLI changes that. You can now install it globally via npm and skip the desktop interface entirely. This isn’t just about personal preference; it’s about environment parity and automation.
Because it’s an npm package, you can integrate it into your deployment scripts or CI/CD pipelines. Imagine spinning up a fresh local instance for an automated test run without ever touching a mouse. Furthermore, if you’re using AI coding agents, you can now give them direct access to manage your local environments via these commands.
# 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, you don’t need a separate install. Just head to your Preferences and enable the “Studio CLI for terminal” toggle. It’s also worth noting that they’ve added a Dark Mode—a small detail, but we all know it’s a requirement for late-night refactoring sessions.
Direct phpMyAdmin Access for Database Management
We’ve all had those moments where a transient gets stuck or a plugin’s custom table is acting up, and you need to see the raw data. Reaching for a separate database tool, configuring the port, and hunting for credentials is a waste of time. WordPress Studio now includes phpMyAdmin access directly from the Overview tab.
This integration is specifically useful for debugging schema issues or running quick SQL queries without the overhead of a heavy external client. It’s a pragmatist’s dream: one click and you’re inside the database. This workflow is highly efficient compared to the old-school method of exporting SQL dumps just to inspect a single row.
If you’re interested in how this technology is evolving, I previously discussed how WordPress Playground is changing local development. These updates are a direct result of that shift toward lighter, browser-based execution environments.
Refactoring Your Workflow
The CLI and the desktop app are companions, not competitors. They stay in sync, meaning you can create a site in the terminal and then open it in the GUI if you need a visual preview. In my experience, this hybrid approach is where most of us will land. We use the CLI for the heavy lifting and automation, and the GUI for quick checks and phpMyAdmin access.
Consequently, the barrier to entry for contributing to Core or testing community plugins has never been lower. You can find the full package details on the official npm page or report issues directly on GitHub.
Look, if this WordPress Studio stuff is eating up your dev hours, let me handle it. I’ve been wrestling with WordPress since the 4.x days.
The Bottom Line
These updates push Studio into “must-have” territory for professional developers. By removing the GUI requirement and embedding database tools, the team has addressed the two biggest complaints about local dev tools: bloat and friction. If you haven’t checked out my recent deep dive on Studio CLI automation, I recommend starting there to see the full potential of these updates.
“},excerpt:{raw:
