WordPress contributors are developing ways to make AI-related capabilities easier to spot in the Plugin Directory. In a weekly update published November 11, the AI team said an ability scanner can identify registered abilities and store that information as plugin metadata, but the implementation still needs work before it can move forward.
What site owners and plugin developers need to know: WordPress AI plugin discovery is being explored, not launched. The scanner has received an initial review from the Meta team, and a separate Trac ticket will explore how to identify plugins that use the PHP AI Client. The update gives no launch date or confirmed directory changes.
WordPress AI plugin discovery is still in development
The [AI team’s November 11 update](https://make.wordpress.org/ai/2026/11/11/ai-contributor-weekly-summary-11-november-2026/) describes two related lines of work. First, an ability scanner developed after WordCamp Contributor Day discussions can identify registered abilities and save that information as plugin metadata. Second, a Trac ticket will explore identifying plugins that consume the PHP AI Client.
The goal, as described by the team, is to help people find plugins that support AI connectors or offer AI-powered functionality. That could make it easier to understand which plugins fit into broader WordPress AI workflows. The post does not say when users will see these details in the directory, or what the final directory display will look like.
That distinction matters. A scanner that collects metadata is an early step, not a finished search or filtering feature. The team said the implementation had received an initial Meta team review and needed additional cleanup before progressing.
Why plugin metadata matters for AI features
WordPress plugins can provide different kinds of AI-related functionality. The update points to registered abilities and PHP AI Client use as signals the directory work may help identify. Better visibility into those capabilities could help users compare plugins and developers understand how their tools connect with the wider ecosystem.
For now, this is a development direction rather than a promise of new directory filters. The update identifies neither a release date nor a specific way that plugin information will be presented. Site owners choosing plugins should not assume that the planned scanner is already available.
A shared abilities package is also moving forward
The discovery work sits alongside a separate effort to make WordPress abilities easier to share across projects. Contributors agreed to move a proposed shared abilities package into the WordPress GitHub organization. It is intended to let projects use reusable abilities as a Composer dependency instead of maintaining separate implementations.
The update names the AI plugin and MCP Adapter as projects with proof-of-concept integrations. It also says the approach could let projects such as WooCommerce use shared abilities without requiring the full AI plugin. The repository name and some implementation details remain undecided, and the team still needs to establish how abilities move from experimental work toward stable functionality.
Maintenance is an open question, too. One contributor volunteered to coordinate the initial migration and maintainership, with another offering support. The update says the group wants to broaden maintainership over time, rather than leave the package dependent on one person.
AI plugin 1.6.0 has a late-November target
The team’s update says AI plugin 1.6.0 is targeted for the end of November and is expected to be the last regularly scheduled major plugin release before WordPress 7.2. Its main focus is an evolving AI Workspace concept that brings site-agent and Command Palette work into a more unified WordPress experience.
The initial version is described as a chat-based agent inside WordPress, using models available through configured AI connectors. The team distinguishes that work from the broader WordPress 7.3 vision for connecting external agents and tools through MCP. It also hopes to include the shared abilities package in 1.6.0, while about a dozen abilities pull requests remain open and could move into the package.
These are plans reported by contributors, not a final release specification. The update says additional abilities can continue to be developed and released independently as the package and its integration workflows mature.
What developers and site owners can do now
There is no new directory feature to enable based on this update. Plugin developers interested in the effort can follow the scanner and related WordPress.org Meta work, while contributors can review the AI team’s call for feedback on abilities and documentation.
For site owners, the practical next step is to keep evaluating plugins by the capabilities and documentation they currently provide. Treat directory-level AI capability discovery as upcoming work, not as an available way to verify whether a plugin supports a particular connector or workflow.
FAQ
Has WordPress launched AI plugin discovery in the Plugin Directory?
No. The November 11 update describes work in progress. The scanner had received an initial review and still needed additional cleanup before moving forward.
What will the ability scanner identify?
The update says it can identify registered abilities and store that information as plugin metadata. It does not describe a finished directory interface or say when users will see the metadata.
When is AI plugin 1.6.0 expected?
The team targeted the end of November for AI plugin 1.6.0 in its November 11 update. That is a target, not confirmation of a release date. Check the AI team’s next update for changes to the plan.