AI Contributor Weekly Summary – 18 February 2026


The AI Contributor group met on February 18, 2026, to discuss the upcoming WordPress 7.0 release, the evolution of the AI Client, and architectural decisions regarding Abilities.

WordPress 7.0 and the AI Client

The meeting opened with a heavy focus on the uncertainty surrounding the inclusion of the AI Client in WordPress 7.0. @isotropic shared insights from a recent conversation with @matt, noting a shift in focus toward how credentials and API keys are managed globally in WordPress, rather than just for AI.

  • Credential Management: There is interest from leadership in a unified “Connectors” screen in core for various services (AI, Google Maps, etc.).
  • Release Timing: With the Beta 1 deadline looming, the team expressed concern that there is insufficient time to implement a complex credential system. If clarity isn’t reached immediately, the AI Client may be pushed to 7.1 or remain a canonical plugin for the time being.
  • Developer Impact: The team discussed the friction of making the AI Client a plugin dependency versus a core feature, noting that core inclusion is vital for widespread developer adoption and a seamless “under-the-hood” experience.

Abilities: Deciding on Nested Namespaces

A significant portion of the technical discussion centered on how Abilities (aka, tools that AI can call) should be named and registered (see #64596).

  • The Decision: The team reached a consensus to support nested namespaces (e.g., core/settings/get or core/post-type/update).
  • Rationale: @justlevine and @jorgefilipecosta argued that nesting is an existing WordPress pattern (similar to REST API) and allows for better progressive disclosure and organization as the number of available abilities grows into the hundreds or thousands.
  • Path Forward: Existing single-level abilities (like get_settings) may be reverted or updated to follow the new nested convention to maintain consistency.

Experiments and MCP Updates

  • AI Experiments Plugin: Version 0.3.1 was released today with a fix for image generation. Plans for 0.4.0 are underway, though some features (like DataViews) are on hold until the core AI Client direction is finalized.
  • Model Context Protocol (MCP): @neillmcshea will be diving back into MCP support next week to coordinate with ongoing PRs from the community.

Evolution of Bi-Weekly AI Team Chat (aka Slack Meeting)

The nature of the bi-weekly Thursday Slack meetings is shifting toward a more community-centric, interactive format. Moving away from rigid agendas, these sessions will now serve as an “Office Hours” and “Show-and-Tell” space.

The goal is to foster a dynamic environment where:

  • Community Experiments: Developers can highlight local experiments, like the recently mentioned “Abilities Scout” or MCP integrations, to get immediate feedback.
  • Visual Demos: Contributors are encouraged to share videos or screenshots of AI implementations that might otherwise stay hidden on X (formerly Twitter) or private repositories.
  • Low-Barrier Entry: By removing the formal meeting structure, the group aims to make it easier for new contributors to join the conversation, ask questions, and understand the “building blocks” of the project in real-time.

Upcoming Events: WordCamp Asia and Contributor Day

The team is preparing for WordCamp Asia in March.

  • @raftaar1191 (in-person) and @justlevine (virtually) will lead AI table efforts.
  • The group aims to overhaul the AI Contributor Handbook by the end of March to provide a lower barrier to entry for new contributors.

Next Steps

  • Community Discussion: All contributors are encouraged to share their thoughts on the Merge Proposal for the AI Client to ensure diverse voices are heard by leadership.
  • Bi-Weekly Slack Meeting: Tomorrow’s Slack chat will pivot toward an “Office Hours” format, focusing on community show-and-tell and engagement rather than a formal agenda.
  • Handbook Audit: Volunteers are needed to review and update specific sections of the AI handbook.

Upcoming meetings

Folks are welcome to join on Wednesday’s at 1700 UTC via Google Meet with in-meeting notes captured in a Slack Canvas and then paired with Gemini meeting notes to help generate this meeting summary post. All team meetings are published to https://make.wordpress.org/meetings/#ai.

  • The next bi-weekly AI Team Slack discussion is scheduled for 19 February 2026.
  • The next weekly AI Contributor weekly Google Meet video call is scheduled for 25 February 2026.

Props to @jeffpaul for pre-publish review.

#check-in, #core-ai, #meeting, #summary