Try Agent Composer Without Installing WordPress: Our Browser-Based WordPress Playground

The problem with product demos

How do you evaluate governed AI drafting without setting up WordPress first?

WordPress is familiar once it is running. Reaching that point normally means choosing hosting or preparing a local environment, installing WordPress, configuring a database, selecting a theme, and adding the plugins needed for the workflow you want to evaluate.

That setup is reasonable for a real project. It is unnecessary when the immediate question is much narrower: what does Agent Composer do with a real WordPress draft, how does Agent Canvas shape the result, and where do the Site Contract, Configuration Set, Blueprint, and validation become visible?

• A hosted showcase can display a finished interface, but it rarely lets every visitor run a fresh agent task.
• A video can explain the workflow, but it cannot prove how the active contract accepts a valid draft or rejects an invalid operation.
• A local installation gives control, but asks the visitor to do infrastructure work before evaluating the products.

The Agent Composer Playground removes that setup step. You choose a prepared Canvas preset, connect your own compatible agent, request a preset-specific draft, and inspect the governed result inside the same temporary session.

The browser becomes the runtime

How can a complete WordPress environment run inside one browser tab?

WordPress Playground can run WordPress in the browser without a conventional server, using WebAssembly-based PHP and a browser-contained filesystem and database. A temporary instance can disappear when the session ends, which makes it a practical foundation for an open, disposable product demonstration.

Our playground assembles more than an empty WordPress installation. It loads Agent Composer, Agent Canvas, a preset-specific content model, and one of four authored mini-sites. Each preset lets you explore Canvas as a working design system before asking the agent for a draft. SaaS Launch is the broadest demonstration and includes every Canvas component available in the playground.

• The browser runs a real WordPress and Gutenberg environment rather than a visual simulation.
• The selected preset supplies its own Canvas presentation, content examples, Site Contract, Configuration Set, and Blueprints.
• Every visitor begins from a known state and can discard the complete session afterward.

The WordPress Playground handbook documents browser-based WordPress without a server at https://developer.wordpress.org/playground/handbook/web-instance/ and the WordPress Developer Blog explains WebAssembly as the technology behind the runtime at https://developer.wordpress.org/news/2024/04/introduction-to-playground-running-wordpress-in-the-browser/.

What you are testing

A transparent drafting workflow, not a site-building promise

The bridge to a browser-only site

How can ChatGPT or Codex operate WordPress that is not publicly reachable?

The WordPress instance lives inside the visitor’s browser tab. It is not a hosted WordPress site with a public server endpoint, so an external agent cannot connect to it directly. That isolation is useful for a disposable playground, but it creates a transport problem.

The playground solves it with a short-lived MCP relay. The browser opens a session connection to the relay. When the connected agent calls an approved tool, the relay forwards that request to the active browser session; the browser invokes the local Composer ability against WordPress and returns the structured result along the same path. The relay does not turn the sandbox into a public WordPress site.

• Your compatible agent connects to the session-specific MCP endpoint.
• The relay carries the request to the paired browser tab rather than connecting inbound to WordPress.
• Composer applies the active permissions, draft ownership, Site Contract, Blueprint constraints, and validation before WordPress changes.

OpenAI describes MCP as a way to connect ChatGPT or Codex to tools and context, including remote Streamable HTTP servers: https://learn.chatgpt.com/docs/extend/mcp. In the playground, MCP is the transport; Composer remains the governed WordPress execution boundary.

What you can inspect

What happens after you choose a preset?

Start with SaaS Launch, Knowledge Hub, Service Studio, or Editorial Journal. Each is a complete mini-site with a distinct Canvas design system and a preset-specific drafting context. You can browse the site and its components before deciding which governed task to try.

After the disposable session starts, connect ChatGPT, Codex, or another compatible MCP client. Ask it to inspect the environment first, then request a normal page draft or content for the preset’s dedicated content type. The result remains a reviewable Gutenberg draft.

• Inspect the active Configuration Set, Site Contract, available Blueprints, fields, and editorial boundaries.
• See which Canvas patterns and components the selected preset makes available to the draft.
• Review the generated blocks, validation result, preview, and session audit, or try a deliberate contract violation and see it rejected without changing content.

The same Agent Composer and Agent Canvas can govern persistent WordPress projects outside the playground. The upcoming Agent Starter will make it faster to assemble a starting site from these preset ideas or from a mapped existing site. That is a separate product workflow; the playground remains the focused, disposable demonstration.