A local WordPress workspace with AI agents built in

Building themes and plugins usually means juggling a local server, a database client, an editor and a terminal. DevWorkspace Pro puts them in one window. It spots a WordPress folder from wp-config.php, creates new sites with DDEV or WP-CLI, and gives DDEV sites a database card, logs, Xdebug and a PHP runner that boots WordPress.

Whatever the setup, every site also gets the editor, Git, GitHub, AI sessions and the terminal.

Core features every project gets

• Files editor with PHP IntelliSense, ⌘+P and project search
• Git Changes, GitHub issues and Actions, and Send to AI
• AI sessions with resume, terminal tabs and Focus Pad
• The ⌘+K project switcher, uptime monitoring and Remote SSH

Extras for WordPress

A typical day with a WordPress site

Create or import

Click New Project and select WordPress. DDEV is the default in step 2, where the Web and Database tabs let you set the PHP version, web server, database type and version, and TLD. Choose Local PHP or Docker Compose instead and the app runs wp core download.

For a site you already have, drag the folder onto the window. If it contains .ddev/config.yaml, it comes in as a DDEV project.

Run

In a DDEV site, click Start. The Overview tab then gives you:

• Open Website and Open Mailpit
• Open phpMyAdmin, when that service exists
• A Database card with the host, port, user and password, each with a copy button

On Local PHP, the Run card starts php -S localhost:8000.

Work with an AI agent

Press ⌘+J and type the task, for example "Add a custom post type for events with a REST endpoint". Claude Code, Codex or OpenCode starts in the site folder. Quit the app mid-task and the session waits for you in Resume the next time you open it.

Fix a bug report and ship

Open the report in Git › Issues and click Send to AI. The prompt carries the issue, its description and every comment. When the agent is done, review the result in Git › Changes, commit and push from the terminal tab. Git › Actions shows your deploy or test workflow with its logs.

WordPress features

Scratchpad inside your booted site (DDEV)

Run PHP with the whole of WordPress loaded, so get_posts(), get_option() and the rest work as they do in your theme. The summary bar shows run time, peak memory and the number of database queries, and it flags a Possible N+1. In sites without DDEV, the Scratchpad tab is a notes pad.

Database tools (DDEV)

Copy the connection details into your database client, or create an additional MySQL or MariaDB database with one click. You can also switch the database type: the app exports, reconfigures and imports for you.

Recipes

DDEV sites get Addons, Cloudflare Tunnel, Additional Database, Rector, Prettier PHP and Laravel Pint in the Recipes panel. NPM Dependencies appears when the theme or plugin has a package.json. Support for the PHP recipes outside DDEV is in progress.

Dependency security

Health › Security reads composer.lock and your npm, pnpm, Yarn or Bun lockfile. On a Bedrock-style site that manages plugins with Composer, those plugins get checked too. Plugins installed from wp-admin are not in a lockfile, so the scan does not cover them.

Xdebug and uptime

• Xdebug (DDEV): the On / Off button runs ddev xdebug toggle, and the menu writes a VS Code configuration on port 9003.
• Uptime: add the live site's public URL in Health › Uptime. Our servers check it every 5 minutes by default and email you when it goes down.

Uses what is already on your machine

DevWorkspace Pro runs the DDEV, Docker, PHP and WP-CLI installed on your computer, and sites DDEV already knows about appear the first time you open the app. Theme build tools run from the Run card or the terminal, and IDE opens the site in your usual editor. Need the server? Remote SSH reads the hosts in your ~/.ssh/config and opens a shell from its own tab.

If you also build with Drupal or plain PHP, see /for/drupal and /for/php. Docs: DDEV Projects, Database, Scratchpad, Dependency Security.