Felix Arntz @flixos90 (co-Team RepTeam RepA Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts.) – Vercel
James LePage @isotropic (co-Team Rep) – Automattic
Over the past few weeks, we’ve been experimenting with a handful of AI-powered concepts in the AI Experiments pluginAI Experiments PluginWordPress's AI laboratory bringing all building blocks together. Serves as both a user tool and developer reference implementation. First release (v0.1.0) includes Title Generation experiment.. These concepts are intentionally exploratory. Some are rough, some may not stick, and all of them need feedback from folks actually using WordPress in the real world.
This post is a Call for Testing, with less interest in “is this perfect?” and more interested in:
Does this feel useful or confusing?
Would you expect this to exist where it does?
What would you change about the UXUXUX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. or flow?
Does it behave as expected in your testing?
Below you’ll find a set of user-facing experiments, developer-focused tools, and one hybrid feature that cuts across both. Each section includes a short description, steps to test and a screencast example, a WordPress Playground link to utilize for testing, and a link back to the PR for feedback.
Please test what you’re curious about. You don’t need to try everything.
User-Facing Experiments
These experiments focus on AI features that surface directly in the WordPress admin or content workflows.
Type Ahead Suggestions
This experiment explores AI-powered type-ahead suggestions while writing. The goal is to understand whether inline suggestions help with flow and clarity, or whether they feel distracting or overly prescriptive.
We’re especially interested in feedback on:
Does the timing of suggestions feel right?
Do suggestions feel helpful or noisy?
Where would you expect controls or settings for this to live?
Navigate to Settings > AI Credentials and add an APIAPIAn API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. key to one of the AI clients listed, then click Save Changes
Navigate to Settings > AI Experiments, check Enable Experiments, click Save Changes, check Type-ahead Text, and click Save Changes
Navigate to Posts > All Posts and either edit the Hello world! post or click Add Post to open the post editor
Start typing content and observe type-ahead suggestions
Press Tab to accept or Escape to dismiss suggestions
This experiment explores using AI to assist with comment moderation. Rather than fully automating decisions, the focus is on providing helpful context or signals to moderators.
We’re especially interested in feedback on:
How do you feel about the AI Reply and Analyze with AI functionality?
This experiment looks at consuming and working with Markdown-based feeds using AI. The goal is to explore new content ingestion workflows and how AI might help interpret or transform structured text.
Navigate to Settings > AI Experiments, check Enable Experiments, click Save Changes, check Markdown Feeds, and click Save Changes
Navigate to Posts > All Posts and view the Hello world! post
Change the end of the URLURLA specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org to /hello-world.md and confirm text/markdown output
Note additional testing options:
Visit /?feed=markdown and confirm text/markdown output
Request a post with Accept: text/markdown and confirm Markdown output
Optional: use the new section filters to inject custom fields into output: npm run test:php -- --filter Markdown_Feeds
This experiment expands the set of available AI providers, making it easier to test and compare different models and services.
We’re especially interested in feedback on:
Is the providerProviderAn AI service offering models for generation, embeddings, or other capabilities (e.g., Anthropic, Google, OpenAI). selection UX understandable?
Do the abstractions make sense from a user point of view?
What information would help you choose between providers?
This experiment explores MCP (Model Context Protocol) support, aiming to improve how context is shared and managed across AI interactions.
We’re especially interested in feedback on:
Does the MCP integration function as you would expect?
Is this solving a real pain point for you?
What documentation or examples would help adoption?
How to test:
Launch using this WordPress Playground link
Open the WP Admin dashboard
Navigate to Settings > AI Experiments, check Enable Experiments, click Save Changes, check MCP, and click Save Changes
Navigate to the top level MCP menu item and view the MCP screen to ensure that Enable MCP and Enable Server are toggled on and that the server shows as 🟢 Running
Toggle the Expose via MCP item for various abilities to test
Use the Test connection feature in the Connection test section to verify endpoint
Copy a Client configuration and test in Claude Desktop or Cursor
This experiment adds logging for AI requests (provider, model, tokens, duration, cost estimate) that can be viewed from the Admin Dashboard as well as configurable retention period and automatic cleanup to help with debugging, cost tracking, and usage analysis.
We’re especially interested in feedback on:
Is the level of detail appropriate?
Who do you think this is for: site owners, developers, or both?
How should this data be surfaced or stored?
How would you want to filterFilterFilters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output., hide, or export this data?
How to test:
Launch using this WordPress Playground link
Open the WP Admin dashboard
Navigate to Settings > AI Experiments, check Enable Experiments, click Save Changes, check AI Request Logging, and click Save Changes
Enable other Experiments (and necessary, related AI Client Credentials via Settings > AI Credentials) and perform actions that trigger AI requests (e.g. Title Generation, ExcerptExcerptAn excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox. Generation)
Navigate to Settings > AI Request Logs and view the AI Request Logs screen showing requests, tokens, and other data
Review logged requests and metadata
Test filtering by provider, status, and date range
Verify “Purge logs” clears all entries
Disable the experiment and confirm no new logs appear
Feedback directly on the PRs is ideal, but broad impressions are also valuable (e.g. as comments on this post, messages in #core-ai). You don’t need to review code to participate, high-level product, UX, and architectural feedback is just as valuable here. If you’re short on time, even answers to one or two of these questions help:
Would you use this if it shipped tomorrow?
What’s the first thing you’d change?
Where does this feel surprising, in a good or bad way?
These experiments are about learning in public. Your perspective can help us decide what to refine, what to pause, and what to drop entirely. Thanks for helping shape what AI in WordPress could become.
Props to @dkotter for helping with content for this post and @justlevine for pre-publish review.
