Tag Archives: summary

Jeffrey Paul 1:58 am on 16 April 2026
Tags: , summary   

AI Contributor Weekly Summary – 15 April 2026

This week’s AI contributor meeting focused on the AI 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. release cycle, MCP clientMCP Client AI agents, IDEs, or assistants that connect to MCP servers to access capabilities. progress, connector-related issues, and contributor onboarding topics. Discussions also covered strategies for improving AI blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. recognition and processing Elementor feedback into actionable issues.

Announcements

  • Testing feedback from @illuminea is available and should be reviewed. Contributors are encouraged to create issues in the relevant repositories based on findings. @justlevine is helping generate issues based on comment discussions in the document. Larger themes such as rate limits and fallback behavior may be addressed asynchronously.
  • AI 0.7.0 was released last week. Feedback is encouraged, with emphasis on fixing bugs and improving existing features ahead of upcoming releases.

Abilities

AI plugin

  • 0.8.0 is targeted for release next week.
  • At least one additional major releaseMajor Release A set of releases or versions having the same major version number may be collectively referred to as “X.Y” -- for example version 5.2.x to refer to versions 5.2, 5.2.1, and all other versions in the 5.2. (five dot two dot) branch of that software. Major Releases often are the introduction of new major features and functionality. is expected ahead of the eventual WordPress 7.0 release.
  • Current focus remains on stabilizing existing features rather than introducing large new functionality.

PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/preface.php / WP AI Client

MCP

  • MCP Client 0.5.0 was scheduled for release immediately following the meeting.
  • Contributors discussed converting the MCP client from a Composer package into a WordPress plugin to avoid dependency conflicts.
  • @ovidiu-galatan will initiate a public discussion in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. AI channel regarding reversing the original decision to ship as a Composer package.
  • @justlevine can assist with technical aspects of submitting the MCP client as a plugin to WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/.

AI Block Recognition Strategies

  • Contributors discussed challenges converting HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. into WordPress blocks due to missing backend creation mechanisms. Proposed approach:
    • Provide agents with a list of available blocks.
    • Use 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/ or WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ tools to expose block metadata.
    • Prefer source-code-driven context over traditional documentation references.
  • @euthelup is preparing to open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. a Claude-based block dictionary tool.

Contributor Support Topics

  • New contributors were encouraged to focus on areas aligned with their experience: AI client, Agent skills, Abilities, MCP development, AI plugin
  • @mikeyarce reported being stuck in a verification loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop while submitting the Minimax provider plugin.
    • Recommendation: request assistance in the Plugins team 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/ channel.
    • AI team members offered to help escalate if needed.
  • Additional provider plugin work is ongoing, including development of connectors for services such as Kimi or Moonshot AI.

Next Steps

  • Generate GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ issues from Miriam’s feedback documentation.
  • Merge approved Abilities and llm-off-switch PRs.
  • Release MCP Client 0.5.0.
  • Continue testing connector-related changes.
  • Advance preparation for AI plugin 0.8.0 release.

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 Office Hours Slack discussion is scheduled for 16 April 2026.
  • The next weekly AI Contributor weekly Google Meet video call is scheduled for 22 April 2026.

Props to @neel33 for pre-publish review.

#core-ai, #summary

neillmcshea 1:47 pm on 9 April 2026
Tags: , summary   

AI Contributor Weekly Summary – 8 April 2026

The AI Contributor group met on Wednesday, April 8, 2026, to discuss the upcoming WordPress 7.0 release, the evolution of the AI Handbook, and coordination for 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://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/ activities.

Highlights

  • Leadership Transition: @jason_the_adams has officially stepped into the role of Director of AI at Automattic. He shared insights on his shifting capacity and how the team can support CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. AI efforts during this transition.
  • AI 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. Release: Version 0.7.0 of the AI plugin is scheduled for release tomorrow, featuring a modernized settings UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing..
  • AI Handbook Push: There is a renewed focus on building out non-technical documentation to explain WordPress’s AI philosophy and provide user-facing guides.
  • Contributor Day Coordination: Plans were finalized for both in-person and digital participation in upcoming contributor events, specifically targeting documentation and testing.

Organizational Update: Jason’s Role & Key Priorities

@jason_the_adams shared that he has transitioned into the role of Director of AI at Automattic (with @isotropic also moving to Head of AI at Automattic). While he is currently re-calibrating his hands-on capacity, he identified two specific areas he is personally committed to watching closely to ensure they do not lose momentum during this shift:

  1. The AI Client: This remains the top priority for the WordPress 7.0 cycle. Jason emphasized the need for high responsiveness to bugs and feedback as plugin developers begin to ramp up their usage of the client.
  2. The Connectors Page: Jason highlighted this as a critical strategic piece. He noted that while the AI team is the primary consumer now, it is not strictly an “AI feature” and is part of a broader vision for WordPress. He suggested that maintenance should eventually transition to the Core or Plugins teams to ensure it isn’t “pigeonholed” as AI-only.

Delegation & Communication Path: To augment Jason’s focus, the team established the following contact protocol:

  • Primary Technical Contacts: @gziolo has been brought on specifically to focus on Core AI contributions. He and @jorgefilipecosta will handle bug fixes, providerProvider An AI service offering models for generation, embeddings, or other capabilities (e.g., Anthropic, Google, OpenAI). updates (OpenAI, Google, etc.), and standard PR reviews.
  • Escalations: Jason should be pinged specifically for architectural redirections, new model types (like embeddings), or significant pivots in the AI Client’s scope.

Core AI and Plugin Development

The team discussed the trajectory for the AI plugin as it aligns with the WordPress 7.0 cycle.

  • V1.0 Roadmap: @jeffpaul proposed jumping to a version 1.0 soon to signal stability and encourage broader adoption before the final WP 7.0 release.
  • UI Modernization: @jorgefilipecosta provided an update on the new settings UI, which uses a data-form structure to allow for automatic generation of sub-settings without regressing user experience.

Documentation and the AI Handbook

A significant portion of the meeting focused on the “optics” of AI in WordPress and the need for a robust Handbook.

  • Philosophy over Code: @jason_the_adams noted that the handbook should move beyond technical docs to address user concerns, (e.g Jason used a hospital website as an example: because the AI Client is flexible, a developer can choose a HIPAA-compliant provider to handle sensitive data securely of the use of the “off switch” a specific constant that users can set to completely disable AI features).
  • Contribution Guides: @neel33 and @jeffpaul are working on adding a “Contribute with Docs” section to help new contributors get started with documentation. As a first step we should all feel comfortable drafting in a Google Doc and sharing in the channel – getting it published should be a low barrier to entry and we should adopt a YOLO method of, publishing first – assuming it was drafted and given some level of review, and feeling ok about iterating and polishing later.

Model Context Protocol (MCP)

Updates on the MCP adapterMCP Adapter Translates WordPress abilities into Model Context Protocol format, allowing AI assistants like Claude and ChatGPT to discover and invoke WordPress capabilities as tools, resources, and prompts. and its distribution:

  • Version 0.5.0: A release is expected this week once final testing is completed by @ovidiu-galatan.
  • Distribution Strategy: The team continues to debate the best way to package the MCP adapter whether as a composer package, a standalone plugin, or a bundled zip to make it accessible for non-technical users. @isotropic @flixos90 we likely will need Team RepTeam Rep A 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. discussion+decision on the approach here.

Call for Design: AI Landing Page

The team discussed the need for a dedicated AI marketing page on WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ to better communicate available features to non-technical users.

  • The Need: Currently, no central landing page exists to showcase WordPress AI features/experiments for non-technical site owners and more detailed technical capabilities to developers, agencies, and hosts.
  • The Request: @jeffpaul issued a call for designers within the community to help identify what content should be featured and how to lay it out.
  • The Goal: Create a single point of reference that highlights “Capital F” Features and “Capital E” Experiments, making AI in WordPress more accessible to the broader public.

The Connectors Page

Clarification was provided regarding the naming of the “Connectors” page in WordPress core.

  • Broader Scope: The page is deliberately not named “AI Connectors” because it is intended to host credentials for various third-party APIs, including non-AI services like Akismet, WooCommerce, or Mailchimp.
  • Unified Interface: The goal is to provide a single, standardized location for all third-party connections within the WordPress dashboard.

Next Steps

  • Open good-first-issues for AI plugin ahead of Contributor Day
  • Release of AI Plugin 0.7.0.
  • Release 0.5.0 MCP
  • Ongoing: Drafting handbook guides on AI concepts and opt-out instructions.

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 16 April 2026.
  • The next weekly AI Contributor weekly Google Meet video call is scheduled for 15 April 2026.

Props to @jeffpaul for the pre-publish review.

#core-ai, #summary

Jeffrey Paul 12:13 am on 6 March 2026
Tags: , summary   

AI Contributor Weekly Summary – 4 March 2026

This week’s AI contributor meeting focused on progress toward WordPress 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. 3, updates across the 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., the WordPress AI Client ecosystem, and next steps for the MCP adapterMCP Adapter Translates WordPress abilities into Model Context Protocol format, allowing AI assistants like Claude and ChatGPT to discover and invoke WordPress capabilities as tools, resources, and prompts. project. Contributors also discussed upcoming testing needs around the connectors interface and early feedback on “Try AI” onboarding flows.

WordPress 7.0 Timeline

WordPress 7.0 Beta 3 is scheduled for release tomorrow. Contributors noted that the upcoming beta milestone continues to shape priorities across several AI-related efforts, particularly testing and stabilization work tied to the AI Client ecosystem and related plugins.

AI Experiments Plugin

@jeffpaul shared updates on the AI Experiments plugin roadmap:

  • Version 0.4.0 is nearing release, with only a couple of remaining PRs left to finalize. The goal is to publish the release tomorrow.
  • Version 0.5.0 planning has begun and will focus on aligning the 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. with the WordPress AI Client version in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
  • Planned changes for the next milestone include dropping WordPress 6.9 support, introducing an image editing feature, and adding onboarding flows that guide users toward AI connectors and features after installing or upgrading to WordPress 7.0.

These changes aim to help the plugin evolve from experimentation toward practical demonstrations of AI functionality built on the core client architecture.

PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/preface.php AI Client and ProviderProvider An AI service offering models for generation, embeddings, or other capabilities (e.g., Anthropic, Google, OpenAI). Plugins

@flixos90 shared updates on the broader AI Client ecosystem.

  • Three official provider plugins are now available on WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ to enable connections to supported AI providers (Anthropic, Google, OpenAI).
  • Work is underway to introduce additional providers beyond the initial set.
  • A new provider plugin for Ollama is being prepared for submission to WordPress.org, providing a local-model alternative to the current hosted providers and enabling additional testing scenarios in the Connectors interface.

The goal is to keep WordPress core provider-agnosticProvider-Agnostic Software design that works with multiple service providers without being tied to one. Recommended for WordPress AI integrations. while allowing provider support to evolve independently through plugins.

MCP Adapter Progress

@neel33 provided an update on the MCP adapter project. The current focus is restarting progress toward the next milestone by:

  1. Completing the outstanding pull requests needed for version 0.5.0
  2. Merging the 0.5.0 milestone into the trunk of the adapter repository
  3. Conducting a dedicated testing phase
  4. Continuing with remaining feature and integration work

Contributors were encouraged to review the open MCP PRs to help move the milestone forward.

Documentation and Community Coordination

Two additional coordination topics were raised during the meeting:

These efforts aim to broaden participation and make AI-related contribution areas easier for new contributors to engage with.

Next Steps

  • Finalize and release AI Experiments 0.4.0.
  • Continue development toward AI Experiments 0.5.0, including onboarding and image editing features.
  • Advance MCP adapter work toward the 0.5.0 milestone through additional reviews and testing.
  • Continue expanding AI provider plugin support on WordPress.org.
  • Gather feedback on connectors testing and the “Try AI” onboarding experience.

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 Office Hours 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 5 March 2026.
  • The next weekly AI Contributor weekly Google Meet video call is scheduled for 11 March 2026.

Props to @neel33 for pre-publish review.

#core-ai, #summary

neillmcshea 3:35 pm on 2 March 2026
Tags: , , , summary   

AI Contributor Weekly Summary: 25 February 2026

The AI Contributor Group met on Wednesday, February 25, 2026, at 23:00 UTC. The meeting focused on the upcoming WordPress 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. 2 release, the development of the new Connector screen, and initial planning for 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’s 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://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/.

🚀 WordPress 7.0 & CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. AI Updates

Beta 2 and Abilities APIAbilities API A core WordPress API (introduced in 6.9) that creates a central registry of capabilities, making WordPress functions discoverable and accessible to AI agents, automation tools, and developers. Transforms WordPress from isolated functions into a unified system.

Beta 2 is on track for Feb 26th . The team discussed the status of several core tracks:

  • Nested Namespaces: These are now officially in Beta, resolving previous concerns about track thread inactivity.
  • Abilities on Hold: Work on new core abilities is currently paused as the team shifts focus toward the Connector screen and the AI client to meet RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. (Release CandidateRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge.) deadlines.
  • Timeline: While most priority items are on track for 7.0, deeper exploration of 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. shapes will likely resume after the current release cycle stabilizes.

The New Connector Screen

@jorgecosta provided a status update on the new UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. requested to simplify AI providerProvider An AI service offering models for generation, embeddings, or other capabilities (e.g., Anthropic, Google, OpenAI). connections:

  • Scope: The goal is a simplified interface to install and connect the three main providers (Google, OpenAI, and Anthropic/Claude) with a single button and an APIAPI An 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.
  • Experimental API: There is ongoing debate regarding how extensibleExtensible This is the ability to add additional functionality to the code. Plugins extend the WordPress core software. this screen should be. For Beta 2, the screen will likely include an experimental API allowing third-party providers to register their own connectors, preventing a fragmented settings experience across the ecosystem.
  • Review: The development is moving quickly in the Gutenberg repository. Contributors are encouraged to test against the latest trunk to ensure no fatal errors occur during provider instantiation.

🧪 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. & Client

@dkotter raised concerns regarding the “double testing” currently required because the Experiments 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. often pulls in older versions of the AI client compared to what is now in Core.

  • Dependency Management: A new PR is up to update the Experiments plugin to the latest WordPress AI client. This serves as a “stop-gap” to maintain compatibility for users on WordPress 6.9 while preparing for 7.0 to become the new minimum version.
  • Image Editing: Current providers in the Experiments plugin do not yet support image editing. Upstream changes to the PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/preface.php AI client will be required to enable this “impressive feature” target.
  • Backwards Compatibility: @jasonadams confirmed he is working on a core prompt function update to the AI client to ensure a graceful rollover to 7.0 without breaking existing third-party implementations.

🔗 Model Context Protocol (MCP) Update

  • Progress: @neillmcshea noted that movement on MCP has been slow over the last three weeks due to contributor availability.
  • Milestones: Questions remain regarding the milestones for version 0.5.0. The team will continue to push for clarity on these open requests to ensure MCP remains a priority for upcoming sprints.

🌏 WordCamp Asia Contributor Day

The team began discussing logistics for the AI table at WordCamp Asia (April 9, 2026).

  • Task Identification: The group agreed that the priority should be defining actionable tasks (testing, handbook updates, and adapter development) rather than just badge distribution. @neillmcshea will create an async doc that we can use to begin planning for WC Asia
  • Handbook Updates: An action item was set to create a “Contributor Day” section in the handbook to empower new contributors to get started without high-touch onboarding.
  • Remote Support: @justlevine will provide remote comms support from 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/ to assist @deepakgupta and others physically present at the table.

📚 Documentation & Knowledge Sharing

  • Glossary & Lexicon: A proposal is under review to standardize AI terminology within the WordPress ecosystem.
  • Knowledge Base: The team is moving toward a regular “call for experiments” to encourage community members to share what they are building with the new Core primitives.

👥 Team Logistics & Availability

  • Contributor Time: @justlevine announced that starting March 1st, his sponsored contribution time will double from 5 to 10 hours per week.
  • Absences: @jasonadams will be largely unavailable during March due to travel and speaking engagements. @jorgecosta and @gziolo will be the primary points of contact for technical reviews during this period.

📅 Next Steps

Next Meeting: Wednesday, March 4, 2026, at 23:00 UTC in the #core-ai Slack channel.

#check-in, #meeting, #summary

neillmcshea 9:09 pm on 18 February 2026
Tags: , , , summary   

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 APIAPI An 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. keys are managed globally in WordPress, rather than just for AI.

  • Credential Management: There is interest from leadership in a unified “Connectors” screen in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. for various services (AI, Google Maps, etc.).
  • Release Timing: With the 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 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 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. 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 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/) 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 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.: 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 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/ 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: 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 and 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://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-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

Jeffrey Paul 3:57 pm on 12 February 2026
Tags: , summary   

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://2017.us.wordcamp.org/contributor-day/ 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

Jeffrey Paul 6:12 pm on 6 February 2026
Tags: , summary   

AI Contributor Weekly Summary – 4 February 2026

This week’s AI contributor meeting focused heavily on final preparation for the WordPress AI Client merge proposal, including providerProvider An AI service offering models for generation, embeddings, or other capabilities (e.g., Anthropic, Google, OpenAI). separation, coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. integration strategy, and controls for disabling AI functionality. The group also reviewed progress across Abilities, MCP, and the 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., with an eye toward unblocking work ahead of the WordPress 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 milestone on February 19.

WP AI Client Merge Proposal

@jason_the_adams shared a detailed update on the WordPress AI Client merge proposal and next steps toward core inclusion.

  • The WordPress AI Client will be fully provider- and model-agnostic when proposed for core.
  • Embedded providers are being removed from the PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/preface.php AI Client, with OpenAI, Google, and Anthropic providers moving into separate 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. repositories on WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/.
  • @jason_the_adams plans to submit the core work as multiple PRs rather than a single all-or-nothing proposal, starting with the PHP AI Client, WordPress AI Client, and prompt builder.
  • Integration of the PHP AI Client into core remains the largest open question due to Composer dependencies and build considerations. The group discussed approaches similar to GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/’s sync/build process, and @jason_the_adams plans to follow up with @youknowriad for guidance.

There was consensus that publishing a technical PR soon is critical to allow meaningful core review before Beta 1.

Disabling and Controlling AI Functionality

The group discussed approaches for disabling or restricting AI usage in WordPress.

  • @jason_the_adams introduced an initial filterFilter Filters 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.-based approach that allows site owners to disable AI entirely or restrict usage to certain capabilities.
  • @justlevine raised concerns that filters alone are insufficient, as they can be overridden by plugins, and suggested introducing a constant to represent an explicit site-level decision.
  • @jason_the_adams agreed to add a constant-based control mechanism, while the group aligned that adding UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing.-level “kill switches” would be premature at this stage.

The goal is to make it easy for sites to opt out without introducing unnecessary UI or policy complexity.

AI Experiments Plugin

@jeffpaul shared updates on the AI Experiments plugin and near-term priorities.

  • Work is wrapping up on Featured ImageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. Generation, Content Summarization, and Alt Text Generation in preparation for a 0.3.0 release.
  • Data Views and Data Forms UI work is being deferred until after the 7.0 Beta 1 window to keep focus on the AI Client merge proposal.
  • A Call for Testing post covering several experimental features has been published, and the team will track feedback before deciding whether any of those concepts should be milestone candidates.
  • Markdown-related work will remain in the experiments plugin for now to gather feedback and usage data before considering core or Gutenberg integration.

Abilities Update

@jorgefilipecosta provided a status update on Abilities work:

  • A PR allowing deeper nesting of abilities namespaces has been approved.
  • Updates to settings abilities and a new user 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. (without metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. support) are nearing readiness.
  • A revised post-finding ability that works across post types is in progress and may require additional discussion.
  • The group expressed optimism that settings and user abilities could land in WordPress 7.0.

This work also helps reduce immediate pressure around formal versioning by allowing namespacing patterns to evolve organically.WordPress well-positioned for future developments such as embedded models or host-managed AI offerings.

MCP (Model Context Protocol)

@jason_the_adams requested review on the final PR in a six-part MCP adapterMCP Adapter Translates WordPress abilities into Model Context Protocol format, allowing AI assistants like Claude and ChatGPT to discover and invoke WordPress capabilities as tools, resources, and prompts. update.

  • The work introduces a generated PHP schema layer derived directly from the MCP JSONJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. schema.
  • The update decouples component registration from abilities, allowing MCP components that do not need to exist as abilities.
  • @jorgefilipecosta offered to review the remaining PR to help move the adapter forward.

Provider Discovery, Documentation, and Guidelines

Several forward-looking topics were discussed:

  • Provider discovery and validation: The group discussed how AI provider plugins should be discoverable without overwhelming users, including possible use of tags and compatibility checks rather than curated lists.
  • Documentation: Two documentation tracks were identified as necessary—one for plugin developers using the AI Client and prompt builder, and another for provider and host integrations.
  • Guidelines and disclosure: Contributors were encouraged to review @isotropic’s draft disclosure statement for agent skills as early prior art for applying the newly published AI Guidelines.

Next steps

  • @jason_the_adams will submit core PRs for the PHP AI Client and WordPress AI Client and add a constant-based mechanism for disabling AI.
  • @jeffpaul will continue coordinating the AI Experiments 0.3.0 release and track feedback from the testing call.
  • @jorgefilipecosta will review the remaining MCP adapter PR and continue advancing Abilities work.
  • Contributors are encouraged to review the MCP PRs and provide feedback on the agent skills disclosure draft.
  • Follow-up discussions on documentation, WP Bench, and provider discovery will continue in 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/.

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 Slack discussion is scheduled for 5 February 2026.
  • The next weekly AI Contributor weekly Google Meet video call is scheduled for 11 February 2026.

Props to @psykro for pre-publish review.

#core-ai, #summary

Jeffrey Paul 6:11 pm on 6 February 2026
Tags: , summary   

AI Contributor Weekly Summary – 28 January 2026

This week’s AI contributor meeting focused on progress toward a proposed WordPress AI Client merge for WordPress 7.0, contributor capacity ahead of the February 19 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 milestone, and a live demonstration of an AI-powered GatherPress workflow built on the Abilities APIAbilities API A core WordPress API (introduced in 6.9) that creates a central registry of capabilities, making WordPress functions discoverable and accessible to AI agents, automation tools, and developers. Transforms WordPress from isolated functions into a unified system. and WP AI Client. The group also discussed tradeoffs between different AI integration approaches and where contributors can most effectively help in the coming weeks.

WP AI Client and 7.0 Timeline

The group revisited the status of the WordPress AI Client and the urgency of moving the work forward ahead of the mid-February Beta 1 deadline.

  • @jeffpaul confirmed that the WP AI Client is being proposed for inclusion in WordPress 7.0, with the understanding that LLM providers will live outside of coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. as separate packages or plugins.
  • @justlevine emphasized the importance of shipping a strong technical implementation early to avoid unnecessary scrutiny and technical debt.
  • While a Make/Core proposal draft exists, the group agreed that publishing a concrete technical PR to wordpress-develop is the most important next step.
  • Contributors agreed to check in with @flixos90 and @jason_the_adams in the Core AI channel to identify immediate gaps where help is needed.

There was alignment that, while 7.0 remains the goal, deferring to 7.1 is acceptable if more iteration time is required.

GatherPress AI Assistant Demo

@jmarx75 shared a live demonstration of an AI assistant built into GatherPress, a WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ project intended to replace MeetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area.-style functionality for WordPress events.

The demo showcased:

  • Creating events and venues using natural language prompts
  • Date calculation handled via a dedicated 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.
  • Stateful conversations that allow follow-up updates (e.g., refining event descriptions)
  • Direct use of the Abilities API mapped to PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/preface.php functions exposed via REST

@jmarx75 noted that the implementation currently prioritizes functionality over polish and highlighted areas for future improvement, including UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. refinement, link handling, and prompt cost optimization. The group agreed the demo was a strong real-world example of how the Abilities API and WP AI Client can be used to build embedded, task-focused AI experiences within WordPress.

WPAI Client vs. MCP AdapterMCP Adapter Translates WordPress abilities into Model Context Protocol format, allowing AI assistants like Claude and ChatGPT to discover and invoke WordPress capabilities as tools, resources, and prompts. Discussion

A detailed discussion followed comparing approaches for building AI-powered workflows:

  • @raftaar1191 suggested using the MCP adapter with external AI tools to reduce implementation complexity.
  • @justlevine and others noted that while MCP can be useful in some scenarios, using the WP AI Client and Abilities API offers better control over context, multi-step workflows, and future compatibility with embedded or host-provided models.
  • @jmarx75 clarified that GatherPress requires AI functionality embedded directly in the WordPress admin experience, making the WP AI Client approach the best fit for current goals.

The group agreed there is no single “correct” approach, and that experimentation across both models is valuable as the ecosystem evolves.

Cost, Providers, and Future Flexibility

Cost and 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) considerations were also discussed:

  • @jmarx75 raised concerns about token costs for casual users and the complexity of managing APIAPI An 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. keys.
  • Contributors suggested using smaller or cheaper models where possible and noted that MCP-based approaches may be cost-effective for users on flat-rate subscriptions.
  • @jeffpaul reiterated that providerProvider An AI service offering models for generation, embeddings, or other capabilities (e.g., Anthropic, Google, OpenAI). integrations will not ship in core and will instead be distributed separately, allowing flexibility without coupling WordPress core to specific vendors, and that open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. and free models are ones he hopes to most strongly advocate for.

There was general agreement that the current direction keeps WordPress well-positioned for future developments such as embedded models or host-managed AI offerings.

Next steps

  • Contributors will ask @flixos90 and @jason_the_adams in the Core AI channel where immediate help is needed on the WP AI Client.
  • @jmarx75 will continue refining the GatherPress AI assistant and address feedback from the demo.
  • Contributors are encouraged to help push the WP AI Client technical PR forward to allow meaningful review ahead of the February 19 Beta 1 deadline.

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 5 February 2026.
  • The next weekly AI Contributor weekly Google Meet video call is scheduled for 4 February 2026.

Props to @psykro for pre-publish review.

#core-ai, #summary

Jeffrey Paul 3:57 pm on 27 January 2026
Tags: , summary   

AI Contributor Weekly Summary – 21 January 2026

The formerly named “CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-AI Contributor Check-in” from 2025 reconvened today as the “AI Contributor weekly meeting” in 2026 as a weekly video chat for contributors to discuss progress and milestones across the projects maintained by the WordPress AI team. 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.

This week’s AI Contributor meeting focused on follow-through after the AI Experiments 0.2.0 release, progress on Abilities work targeting core consideration, and the need to tighten coordination ahead of the WordPress 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 milestone on February 19. The group also discussed review bandwidth, documentation gaps, and upcoming decision points for the broader AI community chat.

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.

The AI Experiments plugin v0.2.0 was released earlier this week.

  • The release announcement post is ready and awaiting a final +1 before publishing.
  • The current iteration of the Abilities Explorer is included in v0.2.0.
  • Looking ahead to v0.3.0, the group discussed refactoring the Abilities Explorer to TypeScript and exploring tighter integration with Data Views and Forms.
  • @dkotter noted that several experiment UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. items planned for v0.3.0 are awaiting review feedback from @jason_the_adams.

There was shared agreement that the 0.2.0 cycle took longer than intended, and that improving release cadence and review velocity remains a priority.

Abilities Work

@jorgefilipecosta provided an update on Abilities work targeting WordPress core:

  • Feedback and reviews on the Settings are nearly complete, and the work is close to being ready for merge.
  • Feedback and reviews on the Core Post Management Abilities PR is still underway.
  • After wrapping that effort, @jorgefilipecosta plans to propose a follow-up PR to continue expanding the Abilities surface area.
  • There was continued discussion around structuring abilities in a more granular way, including per–post type abilities, to allow greater flexibility and extensibility.

The group also reaffirmed the importance of clearly positioning Abilities as part of the AI component in core, to ensure related tickets are visible to the AI team and triaged appropriately.

PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/preface.php AI Client and WordPress AI Client

@jason_the_adams shared that the PHP AI Client v0.4.0 has been released.

Next steps include:

  • Introducing integration tests in the PHP AI Client to catch issues earlier, informed by recent bug reports.
  • Shifting focus to upcoming WordPress AI Client updates.
  • Continuing preparation for publishing the AI client merge proposal and associated PRs, to allow sufficient discussion within core ahead of the Beta 1 deadline.

There was consensus that these proposals need to land soon to avoid being blocked by the February 19 timeline.

MCP (Model Context Protocol)

@ovidiu-galatan shared updates on MCP-related work:

  • Several PRs are open on the MCP AdapterMCP Adapter Translates WordPress abilities into Model Context Protocol format, allowing AI assistants like Claude and ChatGPT to discover and invoke WordPress capabilities as tools, resources, and prompts. to implement the PHP MCP schema.
  • While the work is progressing, review bandwidth remains the primary bottleneck.
  • Contributors were encouraged to help review where possible to move the adapter forward.

The group reiterated that the MCP Adapter is expected to remain a canonical 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., separate from the WordPress AI Client being considered for core.

Tooling, Documentation, and Upcoming Decision Points

Additional topics discussed included:

  • WP Bench: @raftaar1191 successfully tested WP Bench using Ollama Cloud, noting that while results were poor compared to hosted providers, the tool functioned as expected. The group agreed this would be a good topic for the next 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/-based AI community chat.
  • Meeting timing: There is ongoing confusion around whether weekly and bi-weekly calls occur at 1600 or 1700 UTC. @jeffpaul will confirm and update the calendar to resolve this.
  • Documentation gaps: @jeffpaul committed to reviewing the AI component and TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. handbook pages to ensure Abilities are clearly documented as part of the AI component, helping core triagers route issues correctly.

Next steps

  • @jeffpaul will publish the AI Experiments v0.2.0 announcement post and outstanding meeting summaries.
  • @jorgefilipecosta will finalize testing on the Core Post Management Abilities PR, notify @justlevine when ready for another review pass, and prepare a follow-up abilities PR.
  • @jason_the_adams and @flixos90 will continue coordinating on AI client releases and the core merge proposal.
  • @jeffpaul will confirm and update the correct meeting times for weekly and bi-weekly calls.
  • Contributors are encouraged to review MCP Adapter PRs and help test available drafts.
  • WP Bench and the February 19 Beta 1 milestone will be key topics for the upcoming community Slack chat.

Upcoming meetings

Reminder that all team meetings are published to https://make.wordpress.org/meetings/#ai.

  • The next bi-weekly AI Team Chat Slack discussion is scheduled for 5 February 2026.
  • The next weekly AI Contributor weekly Google Meet video call is scheduled for 28 January 2026.

Props to @justlevine for pre-publish review.

#core-ai, #summary

Jeffrey Paul 3:55 pm on 27 January 2026
Tags: , summary   

AI Contributor Weekly Summary – 14 January 2026

The formerly named “CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-AI Contributor Check-in” from 2025 reconvened today as the “AI Contributor weekly meeting” in 2026 as a weekly video chat for contributors to discuss progress and milestones across the projects maintained by the WordPress AI team. 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.

This week’s AI contributor meeting focused on wrapping up the AI Experiments plugin 0.2.0 milestone, unblocking progress on Abilities work, and continuing coordination toward potential AI client inclusion in WordPress 7.0. The group also discussed improving review velocity and establishing a more predictable release cadence going forward.

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. (v0.2.0)

@jeffpaul and @dkotter reviewed the remaining items in the 0.2.0 milestone earlier this week. Several PRs have already been merged, with a small number of stragglers being wrapped up or deferred to 0.3.0.

  • @jeffpaul is preparing the 0.2.0 release with the goal of shipping imminently.
  • A Make/AI post announcing the release and highlighting new experiments is planned shortly after.
  • Once 0.2.0 ships, the team will move into the next milestone, including deferred items and additional targeted experiments.
  • There was agreement that release cadence needs to improve; @jeffpaul and @dkotter will likely establish a recurring UAT, merge, and release rhythm (potentially UAT bi-weekly, release monthly) to prevent future milestones from dragging on.

Abilities and Abilities Explorer

Abilities work remains an active area of focus, with several parallel threads:

  • The Abilities Explorer PR, originally authored by @karmatosed, is close to ready but has been stalled due to review bandwidth.
  • @justlevine has been leading updates but has been dealing with illness; @dkotter offered to review and test the Abilities Explorer once he finishes remaining 0.2.0 work.
  • @jorgefilipecosta shared a proposal and PR for Core Post Management Abilities, intended both as a concrete feature and as an example of how third-party plugins could implement richer, schema-driven abilities.
  • The group discussed versioning and deprecation strategies for abilities, with @jason_the_adams encouraging contributors to engage on the existing track ticket and align on a forward-compatible approach.

There was also discussion around polymorphic abilities versus post-type-specific abilities, with interest in a layered approach that supports both generic, low-level abilities and more specialized ones where appropriate.

PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/preface.php AI Client and WordPress AI Client

@jason_the_adams shared updates on the AI client work:

  • The PHP AI client v0.4.0 is expected to ship soon, followed by a new release of the WordPress AI client.
  • @flixos90 will research and outline a proposal for bringing the WordPress AI client (and its PHP dependency) into core, potentially bundling the PHP client similarly to the Requests library.
  • The WordPress AI client will likely be broken into smaller, focused PRs for core (for example, prompt building and settings handled separately).
  • Streaming support will be removed from the PHP client for now due to technical and hosting constraints.
  • Providers will not ship in core initially; instead, they will live in separate plugins, with a “kill switch” filterFilter Filters 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. planned to allow sites to disable AI functionality entirely or conditionally.

@isotropic offered to draft the Make/Core proposal post to support the core inclusion effort and help manage review load.

MCP (Model Context Protocol)

@jason_the_adams shared updates on MCP-related work:

  • @ovidiu-galatan has opened a series of PRs updating the MCP adapterMCP Adapter Translates WordPress abilities into Model Context Protocol format, allowing AI assistants like Claude and ChatGPT to discover and invoke WordPress capabilities as tools, resources, and prompts., including schema-to-PHP class generation.
  • Several PRs remain open and are in need of review to move the effort forward.

Next steps

  • @jeffpaul will finalize and ship the AI Experiments plugin 0.2.0 release and publish a Make/AI announcement post.
  • @dkotter will review and test the Abilities Explorer after finishing remaining 0.2.0 reviews.
  • @jason_the_adams will post an update on abilities versioning and deprecation and continue coordinating AI client releases with @flixos90.
  • @isotropic will draft the Make/Core proposal post for AI client inclusion.
  • Contributors are encouraged to help review MCP PRs and test the latest Experiments 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. ahead of upcoming core discussions.

Upcoming meetings

Reminder that 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 22 January 2026.
  • The next weekly AI Contributor weekly Google Meet video call is scheduled for 22 January 2026.

Props to @justlevine for pre-publish review.

#core-ai, #summary