DocsWP — WordPress Help

Playground Meetings Summaries – February 2026

This post covers the two Playground meetings held in February 2026. These are bi-weekly chats where contributors to WordPress Playground gather to discuss updates, ongoing work, and plans for current and future releases. All are welcome to join.

Meeting 1 – February 13, 2026

Facilitator: Fellyph Cintra

Announcements

Three posts worth highlighting from the past weeks:

  • wp-env now runs WordPress with Playground runtime — WordPress Playground is now available in wp-env as an alternative to Docker.
  • What’s new for developers? (February 2026) — A roundup of developer-focused updates from the beginning of the year, including several Playground highlights.
  • WordPress Studio 1.7.0 received substantial CLI updates — nearly every feature is now controllable from the command line, improving compatibility with AI-assisted development tools such as Claude Code and Cursor.

Documentation

Three documentation pull requests landed since the last meeting:

  • #3188 — Refreshes screenshots and rewrites content for the web instance page to reflect the latest UI.
  • #3242 — Updates the “Host Your Own Playground” self-hosting page with current instructions and improved clarity.
  • #3103 — Adds a new beginner-friendly “Playground for Everyone” guide explaining what WordPress Playground is and how anyone can use it.

Translations

New translations were added for Bengali and Japanese. Thank you to @noruzzaman and @shimomura tomoki for their contributions.

  • #3177 — Updates translations.md for multiple languages.
  • #3249, #3230, #3229, #3231 — Bengali translations for several guides and documentation pages.
  • #3228 — Japanese translations for developer architecture, PHP, and browser-concepts pages.

Other notable changes

  • Website — A new URL route enables deep-linking directly to the Blueprint Gallery overlay using the ?overlay=blueprints parameter.
  • CLI — A new --phpmyadmin flag spins up a phpMyAdmin instance for inspecting and managing the SQLite database from the command line.
  • Blueprints — Removed an unnecessary dependency on @php-wasm/web from the blueprints package, reducing bundle size and decoupling the two packages.
  • Safari — Multiple improvements shipped following community feedback shared on X.

In total, 32 pull requests were merged since the last meeting.

Updates from contributors

  • Fellyph Cintra — Researching the migration of Playground documentation to the .org Handbook, documenting the process of integrating Playground with code agents, and submitting a new skill for block pattern creation to the WordPress repository.
  • Brandon Payton — Continuing work on making multi-worker mode non-experimental in the Playground CLI, with expanded test coverage now running on Windows, macOS, and Linux.
  • Jan Jakes (@janjakes) — Added phpMyAdmin support to the Playground CLI. Try it with npx @wp-playground/cli@latest server --phpmyadmin. An overview post on the SQLite side is also coming soon.
  • Adam Zieliński — Working on importing WordPress sites between hosts, which will enable moving sites between Playground instances and hosted environments.

Open floor

Fellyph shared a demo of WordPress Playground used together with Claude Code and the DevTools MCP server, highlighting how Claude Code decides whether to fix code directly or use the Site Editor to fulfill requests. The team is curious to hear from the community: are you using Playground with code agents, and what has your experience been like?

If you are interested in contributing to the documentation migration to the .org Handbook, reach out to Fellyph directly via Slack DM.

Meeting 2 – February 27, 2026

Facilitator: Fellyph Cintra

Announcements

The team is currently investigating stability issues affecting WordPress Playground with WordPress 7.0 Beta and Gutenberg v22.6.0. Two related pull requests are in progress:

  • #3312 — Avoids cross-origin policy errors in the editor.
  • #3301 — Fixes a blank /wp-admin page caused by responses crossing the Comlink worker boundary.

Thanks to everyone who reported issues — your feedback helped with the investigation. More fixes are expected in the coming days.

Two posts were published this week:

WordPress 7.0 Beta 2 is now available for testing on WordPress Playground. If you encounter any issues, please report them on GitHub.

Project updates

22 pull requests have been merged since the last meeting. New feature work was paused to focus on WordPress 7.0 stability investigations.

CLI

  • #3288 — Removes a duplicated “Playground CLI Ready” log line to keep startup output clean.
  • #3238 — Detects “port already in use” errors and returns a clear, actionable message.
  • #3150 — Fixes Windows native file-locking issues in the multi-threaded CLI architecture.

PHP.wasm

  • #3287 — Adds PHP function names and refactors the test suite to improve coverage and maintainability.
  • #3234 — Adds a cp (copy) method to Universal PHP for file duplication via the PHP.wasm filesystem API.

Translations

New translations were added for Bengali and Japanese. Thank you to @noruzzaman and @shimomura tomoki for their continued contributions.

Documentation

Updates from contributors

  • Fellyph Cintra — Migrating the documentation to the .org Handbook, working on the Agent Skill guide and the two CLI posts. Started testing Playground with Claude Code and Gemini Hooks; a post about it is coming soon.
  • Jan Jakes (@janjakes) — Improving the agentic experience and setup for Playground and SQLite integration, and investigating performance and memory consumption.
  • Yannick Decat — Compiling PHP.wasm with MAIN_MODULE=2 to reduce .wasm and .js file sizes, and implementing path mappings and path skipping in Xdebug 3.5. Also experimenting with Xdebug in the browser.
  • Bero — Working on an MCP server for the Playground website, including WebMCP support.
  • Adam Zieliński — The WordPress site migrator is working. Next steps include URL rewriting for cross-domain moves and Playground integration.

Open floor

The team discussed what tools would be most useful in an MCP server for Playground. If you have ideas, share them in the comments below or on the relevant GitHub pull requests.

The next Playground chat will be on March 10th in the #playground Slack channel. All are welcome to join.