DocsWP — WordPress Help

AI Contributor Weekly Summary – 11 February 2026

This week’s AI contributor meeting centered on the proposed WP AI Client inclusion for WordPress 7.0, with significant discussion around review velocity, third-party dependencies, and how to build broader confidence within coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. The group also reviewed Abilities progress, discussed a naming question around namespaces, and touched on AI literacy and knowledge sharing across the project.

WP AI Client and WordPress 7.0

A large portion of the meeting focused on feedback from recent core discussions regarding the WP AI Client merge proposal.

Key themes included:

  • Code review and confidence building: Contributors emphasized the need for broad, visible code review to ensure the proposal reflects consensus beyond the immediate AI working group. Building public confidence in maturity and technical rigor was seen as essential.
  • Third-party dependencies: Questions raised in devchat centered on precedent for bundling third-party dependencies in core. Updates to reduce footprint and address CI/CD concerns have already been made, but deeper review of implementation details is still needed.
  • Core vs. pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. debate: Some concerns raised suggested that rapid iteration could continue through a canonical plugin dependency rather than core inclusion. In response, contributors discussed the practical benefits of core inclusion, including accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility), clearer defaults for users, and avoiding long-term maintenance stacks.
  • Timeline pressure: With WordPress 7.0 Beta 1 approaching (Thursday, February 19th), several contributors noted the short review window. While there has not yet been outright rejection of core inclusion, observers are still evaluating the proposal, and more discussion is expected.

Contributors were encouraged to:

  • Test the PR using one of the providerProvider An AI service offering models for generation, embeddings, or other capabilities (e.g., Anthropic, Google, OpenAI). plugins (Anthropic, Google, OpenAI).
  • Leave concrete, experience-based feedback directly on the PR.
  • Help surface real-world use cases to demonstrate stability and utility.

@jason_the_adams will meet with the 7.0 Release LeadRelease Lead The community member ultimately responsible for the Release., @matveb, to better understand expectations and next steps, and will report back so the team can adjust accordingly.

Abilities Update

@jorgefilipecosta provided an update on Abilities work targeting 7.0:

  • The get settings abilityAbility A registered, self-documenting unit of WordPress functionality that can be discovered and invoked through multiple contexts (REST API, Command Palette, MCP). Includes authorization and input/output specifications. has been merged (though naming may change depending on namespace decisions).
  • The update settings ability is in progress and represents the first write-capable ability, marking a significant milestone.
  • The more complex post ability is still under development. Given its scope and the introduction of new query capabilities beyond what the REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”)
    https://developer.wordpress.org/rest-api/     currently exposes, contributors agreed it is likely a 7.1 target rather than 7.0.

Ability Namespaces Discussion

A request was raised to revert the current nested namespace approach (e.g., core/settings/get). The discussion centered on:

  • WordPress precedent, which generally avoids nested namespace structures.
  • Discoverability for LLMs and agent-based usage, where nested naming may provide clearer contextual signals.
  • The importance of getting naming right early, as it affects all future abilities.

No final decision was made, but contributors agreed further discussion is needed before renaming existing merged abilities.

AI Experiments PluginAI Experiments Plugin WordPress’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.

@jeffpaul shared a brief update:

  • AI Experiments 0.3.0 has been released, along with an announcement and a Call for Testing post.
  • Development toward 0.4.0 is purposely slowed until after the 7.0 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 process.
  • Contributors are encouraged to review the Call for Testing post and provide community feedback before roadmap features are pulled into active milestones.

AI Literacy and Shared Practices

The group discussed a broader challenge: how to improve AI literacy across contributors and leadership as the landscape evolves rapidly.

Suggestions included:

  • Blogging experiments and learnings publicly to create durable knowledge.
  • Contributing to a shared handbook or lexicon on Make sites.
  • Adding a lightweight “Show and Tell” section to weekly meetings to share experiments, confusing articles, or lessons learned.
  • Avoiding absolute language when discussing AI capabilities, given the pace of change.

@neel33 volunteered to explore existing handbook structures to identify where shared AI practices could live.

WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They’re one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Asia Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/

@isotropic will arrive after Contributor Day, so the team requested volunteers to lead the AI table.

@raftaar1191 volunteered to help lead the AI table at WordCamp Asia Contributor Day. Additional volunteers are welcome and encouraged.

Next steps

  • Broader testing and review of the WP AI Client PR to support core discussion ahead of 7.0.
  • Continued discussion on ability naming conventions.
  • Progressing update settings toward merge for 7.0 consideration.
  • Publishing and amplifying learnings through Make posts and handbook contributions.
  • Preparing materials and coordination for the WordCamp Asia AI table.

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 Chat SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ discussion is scheduled for 19 February 2026.
  • The next weekly AI Contributor weekly Google Meet video call is scheduled for 18 February 2026.

Props to @jason_the_adams for pre-publish review.

#core-ai, #summary