WordPress Studio Ships Standalone Studio CLI on npm and Built‑in phpMyAdmin
WordPress Studio adds a standalone Studio CLI (npm package wp-studio) and built-in phpMyAdmin in the Overview tab, streamlining local WordPress development.
WordPress Studio has rolled out two practical updates aimed at reducing friction for developers and site builders working locally: a standalone Studio CLI available on npm, and integrated phpMyAdmin access inside the desktop app’s Overview tab. Together the changes make it easier to manage local WordPress sites from the terminal or the app without reaching for third‑party tools, and they keep the command‑line and graphical workflows in sync.
Studio CLI is now an npm package
The most visible change for terminal users is that Studio’s command‑line interface is available as a standalone npm module under the package name wp-studio. That means developers who prefer working in the shell can install the tool globally with npm install -g wp-studio or invoke it once with npx wp-studio, avoiding the need to rely on the desktop GUI.
For users who already run the Studio desktop app, the CLI capability is also exposed there: a Preferences setting labeled Studio CLI for terminal makes the same command‑line surface available without an additional global install. The vendor frames the CLI and the desktop application as complementary tools rather than replacements; both remain usable and stay synchronized with one another.
What the Studio CLI supports today
Out of the box, the CLI provides the key functions needed for local development workflows: authenticating with WordPress.com, creating and managing local sites, previewing sites in a browser, and executing WP‑CLI commands. Those features aim to let developers script common actions and integrate site spawns into automated processes without leaving the terminal.
The team behind Studio also indicates ongoing work on additional sync and migration features: sync with WordPress.com and Pressable, as well as import and export capabilities, are noted as coming soon. The release positions the CLI for use in contexts where command‑line automation is already in place — the announcement specifically calls out automated test runs, deployment scripts, and AI coding agent workflows as natural fits.
Installing and enabling the CLI
There are two straightforward ways to use the Studio CLI:
- If you prefer a temporary run: npx wp-studio will launch the CLI for a one‑off session without a global install.
- If you want the command permanently: npm install -g wp-studio installs the CLI system‑wide.
If the Studio desktop application is already installed, toggling the Studio CLI for terminal option in Preferences enables the same terminal commands without separate installation. The desktop app itself continues to be supported and remains part of the recommended toolkit.
Built‑in phpMyAdmin in the Overview tab
On the desktop side, Studio now embeds phpMyAdmin directly in the app’s Overview tab. That integration gives a visual interface for interacting with a site’s local database without opening an external database client or performing additional configuration.
From the Overview tab, users can open phpMyAdmin with a single click to inspect and edit tables, run queries, verify data, and diagnose schema issues. The addition is aimed at simplifying common debugging and data inspection tasks that previously required launching a separate database tool and going through connection or setup steps.
Small but notable usability refinements
The release also highlights user interface polish available through the desktop app. The Preferences area exposes appearance settings — including a newly available dark mode — and the CLI toggle mentioned above. Those small refinements are part of the broader push to reduce the number of separate tools and windows developers must juggle during local development.
How these updates fit into developer workflows
The two changes address distinct pain points that often interrupt focused development work. The standalone CLI removes GUI dependency for users whose workflows are centered in the shell or in automated environments; it enables scripting of site creation and lifecycle tasks and can be included in repeatable processes. The embedded phpMyAdmin removes the friction of switching applications whenever database inspection or quick edits are needed.
By making both terminal and graphical paths available and synchronizing their state, the product aims to serve a range of users: developers who want tight terminal integration, designers or content editors who rely on a graphical interface for database inspection, and teams that mix both approaches.
Implications for automation and AI‑assisted development
The announcement explicitly calls out automated test runs, deployment scripts, and AI coding agent workflows as scenarios where the CLI is particularly useful. That framing suggests the team envisions the CLI being incorporated into scripted pipelines and tooling chains that already operate in the terminal. Because the CLI can run WP‑CLI commands and manage local sites, it can be plugged into existing automation patterns without forcing a GUI step.
At the same time, the built‑in phpMyAdmin keeps a visual, low‑friction path available for ad hoc diagnosis and data fixes that are often awkward to perform through the command line alone. Together the features lower the cognitive and tool‑switching costs for tasks that mix mechanical automation and human inspection.
Who benefits from these updates
- Command‑line centric developers gain a direct, npm‑installable interface for standing up and controlling local WordPress instances, suitable for scripting and CI‑adjacent use.
- Developers and site maintainers who prefer a graphical interface can now open phpMyAdmin from the Overview tab without launching or configuring a separate database client.
- Teams that combine automated tooling and manual debugging can keep both flows aligned because the CLI and desktop app are designed to remain in sync.
- Users who already run the desktop app get immediate access to the CLI through the Preferences toggle; those who do not can add the CLI via npm.
Limitations and current scope
The released functionality is focused on local development convenience: authentication with WordPress.com, site creation and management, browser preview, and WP‑CLI execution are available now. Features explicitly described as forthcoming include synchronization with WordPress.com and Pressable plus import and export capabilities. The desktop app remains supported and continues to provide graphical workflows alongside the CLI.
Developer and business considerations
For teams building developer tooling, the availability of a standalone, npm‑distributed CLI for a mainstream platform like WordPress Studio signals lower integration cost for including Studio workflows in larger toolchains. The ability to script site creation and to run WP‑CLI from the same interface can simplify local test harnesses and developer environment orchestration.
From a business and operational perspective, embedded database access in the desktop app shortens the feedback loop for diagnosing content or schema issues in local environments. That can reduce the time developers spend context‑switching and speed iterations during debugging sessions.
Feedback and contribution path
The Studio team has opened a public channel for feedback and issue reporting on GitHub. Users can submit bugs, feature requests, and pull requests through the project’s repository to share input and track progress on planned enhancements.
Practical next steps for users
If you already use the Studio desktop app, check Preferences to enable the Studio CLI for terminal and experiment with running WP‑CLI commands or previewing sites from the shell. If you prefer not to install the desktop app, the npm package wp-studio can be installed globally or invoked with npx for ad hoc use. Desktop users who need to inspect or edit local databases can now do so directly from the Overview tab via the integrated phpMyAdmin interface.
The release invites users to evaluate both paths — terminal and GUI — and to move between them, since the tools are intended to remain synchronized. If you want to report issues or request features such as the announced sync and import/export capabilities, the project’s GitHub repository is the designated place for that feedback.
Looking ahead, the combination of a separately distributable CLI and embedded database tooling points to a smaller set of friction points for local WordPress development: fewer external dependencies, more scriptable site management, and faster database inspection. As announced additions such as WordPress.com and Pressable sync, and import/export features arrive, those capabilities are likely to extend the range of workflows the Studio tooling can cover while still keeping the desktop application as a supported option.
