Tag Archives: core-ai

Jason Adams 7:58 pm on 4 December 2025
Tags: core-ai   

AI for WordPress Hosts

For AI to succeed in WordPress, it will require the adoption of the WordPress hosting ecosystem. If you work for a hosting company that provides managed hosting for WordPress, then this article is for you. Check out the AI Building Blocks for WordPress post if you need an introduction to the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. AI efforts.

The ProviderProvider An AI service offering models for generation, embeddings, or other capabilities (e.g., Anthropic, Google, OpenAI). onboarding problem

Imagine if WordPress hosting was BYOD (Bring Your Own Database). The host is willing to provide the filesystem and WordPress instance, but for it to really work you need to somehow hook up your own database. Plugins likely each come up with their own way of helping users find and connect a database. At the very least, a significant percentage of the market would be lost. Putting this kind of technical requirement on users to figure out adds significant friction to virtually every non-technical user.

The same problem exists for AI. There are a number of AI plugins for WordPress right now. They all have their own way of helping the user to find an AI provider, generate 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, and copy-paste it in the WordPress settings. To many of this this doesnโ€™t sound too bad, but such 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 authors have shared that this remains the most significant barrier to entry for users.

If AI is to be considered a fundamental component of WordPress, the same way databases are, our project depends onย  hosts taking ownership of this step and including it in their offerings.

Why itโ€™s worth it

This of course means the cost of developing a way to provide AI in hosting as well as the ongoing token cost from AI usage. Itโ€™s not an inconsequential undertaking. But it is worth it, and hereโ€™s why:

The Internet has transformed and is transforming in real time, starting in just the past two years. Offerings like Lovable used to be far too quirky to be usable a couple years ago, and now the prospect of AI building a decent website is real. The reality is that itโ€™s not one WordPress host, one WordPress product, or one WordPress company versus these prolific solutions, itโ€™s all of WordPress. All WordPress ships must rise with the tide of AI, so everyone has a part to play.

This sounds a bit existential, and to an extent it is, but itโ€™s also an incredible opportunity. An AI-powered WordPress has the potential to compete with everyone of these solutions. The reason being the same as to why WordPress powers over 40% of the Internet right now: It grows at the rate of its ecosystemโ€™s innovations. As one of the largest open-source projects in the world, no one can keep up with the multitudes of people making it better every day. Armed with AI, there is a real chance to see WordPressโ€™ market share take yet another major jump. When this happens everyone wins.

Once hosts begin including AI in their hosting, the AI-powered features developed by plugin authors will simply work. No extra user steps, just features that feel like magic and wouldโ€™ve taken a long time to build. Hosts can also make use of things like MCP Servers in WordPress to create site dashboards that are vastly more capable. As plugins improve their AI integrations, much of this is accessible on a hosting level, allowing for host-level features.

Business opportunities

There are a lot of opportunities to differentiate in this new landscape. Many hosts are likely to go the route of providing a Provider as a proxy to someone like Anthropic, taking advantage of purchasing tokens at volume. This, in turn, can allow different hosts to provide varying levels of AI requests within different plans. Wanting more AI requests can mean upselling to a higher plan or purchasing an AI add-on. Others may explore usage-based billing, instead.

Another opportunity is to explore how developers can be provided with access to the hosted AI Provider to test their plugins on hostsโ€™ specific systems. This ensures that the AI-powered features within plugins work optimally on hostsโ€™ systems.

With this, some hosts may decide to experiment with an in-house model to tentatively drive down costs, or simply handle a specific prompt modality (e.g. text-to-text). This can then be used to provide further differential in cost. Others may want to go the more expensive route and try to provide the best output without trying to be the cheapest.

The point being, standing out as a WordPress host that enables incredible AI-powered features, literally just by being on that host, is a significant competitive advantage. This adds a new dimension in standing out.

Registering the hosted provider

AI integration will work through the WP AI Client, which is proposed to go into WordPress 7.0. Connecting your AI model using this is pretty simple. On a high level, itโ€™s the following steps:

  1. Create a Provider, which contains and informs the system of your models
  2. Create one or more Models, including your model capabilities (e.g. can it generate images)
  3. Connect your Model to your Provider
  4. Register your Provider with the AI_Client

Authentication is supported to keep your AI API secured, and there are helpers for Providers/Models that communicate over HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands.. If you run into any issues during integration, please make an Issue in the repository or reach out on #core-ai in the Make WordPress channel on 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/..

More documentation and examples will be provided over the coming weeks!

Wrapping up

This is an exciting time for WordPress and an exciting opportunity for hosts. For hosts that are the first to bundle AI in their services WordPress will simply have AI-powered features that appear only within those hosts. While most products and SaaS services out there are chasing similar AI features to include in their products and services, WordPress has the opportunity to leapfrog the market and be the first AI-powered CMS.

Props to @annezazu, @jeffpaul, and @isotropic for the pre-publish review!

neillmcshea 2:42 am on 25 October 2025
Tags: , core-ai, ,   

Core-AI Contributor Check-in โ€“ Oct 22nd, 2025

The CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. AI team celebrated a major milestone this week: 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. successfully merged into the WordPress 6.9 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. release. This achievement marks the culmination of intense, last-minute work, and the team recognized the extraordinary effort required to meet the core feature freeze deadline.

With the foundational server-side 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. now in core, the teamโ€™s focus is immediately shifting to the future, specifically managing the client-side (JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a userโ€™s browser. https://www.javascript.com/.) portion of the Abilities API and planning the next phases for 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.. A major decision surfaced regarding the destination of the client-side code, with a consensus leaning toward moving it into the 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/ repository to leverage existing infrastructure and streamline future development.

The team is also cleaning up post-merge tasks, including resolving follow-up issues in 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 starting to define long-term maintenance and communication strategies for the new components now living in the WordPress core.

Key Highlights

๐Ÿš€ Abilities API Shipped in WordPress 6.9 Beta

The server-side implementation of the Abilities API has successfully landed in the core WordPress beta, marking the projectโ€™s most significant milestone to date.

  • Core Integration Complete: The underlying server-side code for registering and retrieving abilities is now part of the WordPress 6.9 beta.
  • Team Recognition: The team gave a huge shout-out to Greg Ziรณล‚kowski for his โ€œunyielding effortsโ€ in finalizing the merge before the code freeze deadline.
  • Post-Merge Cleanup: Several related issues and documentation tasks in the Abilities API repository are being closed or moved, as the source of truth for the API now resides in the core WordPress develop repository.

๐Ÿ’ป Client-Side Abilities and Future Development

The front-end portion of the Abilities API did not make the 6.9 beta deadline, prompting a major strategic discussion on its future home.

  • Client-Side Deferred: The JavaScript client-side code for abilities did not ship with 6.9, primarily due to the tight deadline and complexity, confirming that none of the client-side registration made it into the beta.
  • Strategic Move to Gutenberg: There is a strong consensus among the team and core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. to move the client-side code to the Gutenberg repository.
    • Reasoning: This location offers the best โ€œtesting groundโ€ and development environment, simplifying integration with the 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. Editor and command palette, and aligns with the strategy of centralizing JavaScript development.
  • Repo Fate: The long-term plan is to archive the original Abilities API repository once the feature stabilizes in core, officially making the WordPress develop repository the source of truth for the server-side API.
  • Maintaining Compatibility: The team will continue to explore methods (like Composer packages) to ship polyfills for WordPress 6.8 and older, ensuring continuity for developers who need to support previous versions.

๐Ÿงช AI Experiments Plugin Progress

Development is continuing on 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 designed to host experimental AI features.

  • Unblocking Contributors: The team is focused on merging final scaffolding PRs to unblock more contributors who are eager to start building experimental features.
  • Design North Star: A preliminary design discussion considered using a card format for enabling/disabling features (similar to the Add Plugin screen) to provide a familiar user interface.
  • Prioritizing Credentials: The most immediate need is the basic service providerProvider An AI service offering models for generation, embeddings, or other capabilities (e.g., Anthropic, Google, OpenAI). settings screen to allow users to enter API credentials and start experimenting.
  • Design Contribution: Product design work and mockups are being pulled from Fueled resources to initiate discussions and provide a conceptual starting point, inviting broader community feedback on the Needs Design tasks.

๐Ÿ“ฆ 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. Client and MCP Adapter Milestones

Work is progressing on the core developer tools that power the AI features.

  • PHP AI Client (0.2) Released: The core PHP client SDK had its 0.2 version released.
  • Native API Support De-prioritized: Work to use native provider APIs (e.g., for Google Gemini) was deemed not urgent, as the current OpenAI-centric API format is sufficient for initial experimentation.
  • MCP Adapter Major Merge: The significant Major Refactor PR (#48) in the MCP Adapter has been merged, though the resulting codebase requires immediate follow-up testing and small fixes before it can be tagged as version 0.3.
  • MCP Follow-up: Ovidiu Galatan is currently tackling several small, technical follow-up issues stemming from the large merge, with a plan to prioritize and organize them for community pickup before he goes on vacation.

๐Ÿš€ Testing and Next Steps

The team emphasized the need for immediate, widespread testing to flush out bugs during the beta phase.

  • External Testing Commitment: David Levine plans to actively engage external parties, including the Elementor team, for migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. and testing next week to provide a crucial influx of real-world feedback.
  • Real-World Validation: The successful independent integration of 11 abilities into the GatherPress plugin provides valuable evidence of the APIโ€™s immediate utility.
  • Process Documentation: The current process of moving features from a feature repository into core is noted as a necessary step, and the team plans to document this handover process to create a clear path for future feature incubation.

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

Jonathan Bossenger 9:46 am on 21 October 2025
Tags: core-ai, ,   

AI Chat Summary โ€“ 16 October 2025

Location: #core-ai Slack Channelย 

The bi-weekly CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. AI meeting was held on October 16th, 2025:

  • 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. Progress and Inclusion in WordPress 6.9
    • @isotropic and @jason_the_adams led a discussion focused on the urgent need to finalize the Abilities API for inclusion in the upcoming WordPress 6.9 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. release, scheduled for the following week.
  • Abilities API HooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. and Extensibility
    • @jason_the_adams raised a discussion around the hooks needed to maintain an Abilities API 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 that can provide more bleeding edge features between core releases. @justlevine and @jason_the_adams agreed the current MVPMinimum Viable Product "A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development." - WikiPedia hooks, like the *_args 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. and unshaped 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., should allow for experimentation and future improvements.
  • Abilities API Categories and Filtering
    • @isotropic discussed the need for robust filtering of abilities, particularly for AI agents, but the group concluded the current categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. and meta system provides sufficient flexibility for now, with the responsibility of filtering abilities falling more on systems like 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. rather than the core Abilities API.
  • Abilities API and AI Experiments
    • @isotropic and @justlevine highlighted the need for abilities to support AI use cases, such as handling dates and inserting blocks, and encouraged @jmarx75 to create issues in the AI Experiments repo to propose new abilities. The group agreed these could start in experiments before potentially flowing into core.
  • Abilities API Documentation and Terminology
    • @karmatosed suggested adding a terms/glossary section to the Abilities API handbook to help provide clarity, and @justlevine referenced Tanstackโ€™s โ€œPhilosophyโ€ approach as a potential model for documenting the projectโ€™s beliefs and principles.

#core-ai, #meeting, #summary

neillmcshea 2:49 pm on 16 October 2025
Tags: core-ai, ,   

Core-AI Contributor Check-in โ€“ Oct 16th, 2025

This weekโ€™s meeting was characterized by an urgent focus on hitting the Friday milestone for 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. to ensure inclusion in the upcoming WordPress 6.9 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. release (scheduled for the following week). The team quickly made a decision to formally extend the internal milestone deadline to Friday to allow time for critical reviews and merges.

The discussion revolved around which in-progress features (like categories, coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. abilities, and filtering) could realistically be finalized without introducing complexity or technical debt. The team prioritized confirming that the core functionalityโ€”registering and retrieving abilitiesโ€”was done, while tabling or deferring more complex โ€œicing on the cakeโ€ features like filtering. Jason Adams was tasked with raising an immediate decision point to leadership on whether to pull an in-progress feature if it could not be finalized quickly.

Finally, the team received exciting external validation as Jeff Marx shared that he had successfully implemented 11 abilities using the Abilities API in the GatherPress 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, demonstrating the 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.โ€™s readiness for real-world plugin development.

Key Highlights

๐Ÿ—“๏ธ Abilities API Deadline and Scope

The team established a firm internal deadline to complete all necessary work for the Abilities API to make it into the core WordPress 6.9 beta.

  • Milestone Reset: The internal milestone deadline was formally moved from Thursday to Friday to allow critical work to be completed without unnecessary panic.
  • Core Deadline: The target for core integration is tied to the WordPress 6.9 Beta 1 release, which is scheduled for the beginning of the following week (the 21st).
  • Core Functionality Complete: The essential goal for 6.9โ€”the 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. to register and retrieve abilitiesโ€”is already complete.
  • Focus on Core, Defer โ€œIcingโ€: The team prioritized shipping the core API and deferring optional features like filtering to avoid introducing complexity or missing the deadline. Filtering was deemed non-essential, as developers can always retrieve all abilities and 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. them manually.
  • Urgent Decision Point (Cherry on the Cake):
    • An in-progress feature (the โ€œhalf cherry,โ€ likely a complex required field like categories) was noted as partially merged on 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. side but lacking JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a userโ€™s browser. https://www.javascript.com/./client-side completion.
    • Action: Jason Adams was tasked with getting an immediate decision from core leadership (James and Greg) by end of play the following day (Friday) on whether to pull the unfinished feature entirely or push for its completion by the new deadline.

Abilities API Core Features Status

The team reviewed the status of key features intended for the 6.9 core merge:

  • Categories (Grouping Mechanism):
    • Status: Work is in progress and is now required due to a prior decision.
    • Plan: Ovidiu Galatan committed to completing the implementation and aligning 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. with the required categories today, provided the filtering work is paused.
  • Core Abilities:
    • Status: A draft PR exists but is unlikely to be fully reviewed, approved, and merged in time.
    • Decision: The team decided to defer most initial built-in core abilities (excluding the ability fetching ability) for now to avoid slowing down the overall 6.9 timeline.
  • Filtering:
    • Status: Work is in progress but is highly complex.
    • Decision: The team agreed to pause/punt the formal filtering feature as it is not a blocker for using the Abilities API.

Client and Experiments Update

The focus shifts to completing client tools now that the Abilities API is nearing its core deadline.

  • PHP AI Client (0.2): Jason Adams is finalizing PRs to prepare for the 0.2 release of the PHP client.
    • New Feature: A preferred model feature is being added, allowing developers to provide a prioritized list of models, with the client automatically falling back to the next available model that fits the prompt criteria.
  • WordPress AI Client (0.1): Development will ramp up on the WordPress AI client wrapper (0.1 release) in the coming weeks, especially once Jason Adams shifts to full-time work on the project.
  • Experiments Plugin: Work is continuing on design mockups and product definition for future features (V2/V3). The pluginโ€™s release is not coupled to the WordPress 6.9 release, allowing the team to iterate on it until December 2nd and beyond.

External Validation and Testing

The project received positive external validation for the Abilities API.

  • GatherPress Integration: Jeff Marx reported successfully implementing 11 abilities in the GatherPress plugin over the weekend, demonstrating the APIโ€™s effectiveness for managing events and venues.
  • Actionable Feedback: David Levine offered to review Jeffโ€™s code and potentially create a demo video, ensuring the new code serves as valuable prior art for future API refinement before the 6.9 core deadline.

MCP Adapter Status

Focus is shifting back to the adapter now that Abilities API is nearing completion.

  • Major Refactor PR: The largest outstanding piece of work, Oviโ€™s Major Refactor PR, needs final review.
  • Next Steps: Ovi will align the adapterโ€™s code with the newly required categories from the Abilities API. Once this is done and reviews are complete, the team plans to merge the PR and bump the version to the next major iteration (e.g., 0.3) to move past this stalled point.
  • Issue Cleanup: The team closed an old, ambiguous issue related to version numbering (issue 40) to reduce confusion.

#core-ai, #meeting, #summary

neillmcshea 3:52 am on 9 October 2025
Tags: core-ai, ,   

Core-AI Contributor Check-in โ€“ Oct 8th, 2025

This weekโ€™s meeting focused on updating the team on various component progress, including 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., 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., and 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./WordPress AI Clients. A major announcement was the deployment of 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. on WordPress.comWordPress.com An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https://wordpress.com/, marking a significant step in dogfooding the new technology.

The primary discussion points centered on scope and definitions for the Abilities API, particularly what constitutes a required vs. optional parameter, and how to define โ€œ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..โ€ The team also had an in-depth conversation about the user experience for AI settings, specifically managing providerProvider An AI service offering models for generation, embeddings, or other capabilities (e.g., Anthropic, Google, OpenAI). credentials and feature toggles, acknowledging the high friction point this represents for users.

Key Highlights

Announcements & Overall Progress

  • MCP Adapter on WordPress.com: The MCP (Modular Capabilities Package) adapter has been deployedDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. and is actively being used on WordPress.com, confirming its real-world application.
  • Roadmap Review: Tammie Lister proposed wrapping up the roadmap discussion issue to maintain flow and actionability.
  • Abilities Repo Health: The Abilities Repository has 11 PRs and 1 draft, with five issues in the current milestone, signaling good progress.
  • MCP Repo Structure: Neill McShea and David Levine have scheduled a meeting to clarify and structure the MCP repository information, allowing for more detailed updates in the future.

Abilities API & Scope Management

  • Categories Requirement: The team agreed that a grouping mechanism (like โ€œcategoriesโ€) needs to be a required parameter from the first iteration of the Abilities API.
    • Reasoning: This is crucial for future-proofing, ensuring order in a potential โ€œwild westโ€ of abilities, and allowing for filtering when there are thousands of tools in WordPress.
  • Meta vs. Root-Level Arguments: A long discussion was held to define a clear boundary for placing arguments in the meta object versus at the root level of an 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..
    • Proposed Definition: Root-level arguments should be for anything required to execute the action (e.g., input/output schema, callback functions). Meta should be for anything descriptive, optional, or speculative/experimental that is not required for execution (e.g., annotations, show in REST, show in MCP).
    • Action: Jason Adams will work on a clear, concrete definition to be documented.
  • Scope Concern: David Levine raised a concern about โ€œscope creepโ€ and โ€œshipping tech debt,โ€ urging the team to confirm that currently planned speculative features (like annotations) are truly necessary for the first release, given that CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. does not easily remove features once they ship.

AI Client Updates

  • PHP AI Client (0.2): Felix Arntz is prioritizing the release of a 0.2 version of the PHP AI Client, with most work already complete and just a few outstanding PRs.
  • WordPress AI Client (Wrapper): The team needs to make a decision on whether the client wrapper should adjust for WordPress coding standardsWordPress Coding Standards The Accessibility, PHP, JavaScript, CSS, HTML, etc. coding standards as published in the WordPress Coding Standards Handbook. May also refer to The collection of PHP_CodeSniffer rules (sniffs) used to format and validate PHP code developed for WordPress according to the PHP coding standards. (e.g., snake_case functions and returning WP_Error) instead of strictly adhering to PHPโ€™s best practices (camelCase functions and throwing exceptions).

AI Experiments Plugin

  • Issues and Mockups: Jeff Paul reported new issues opened, aligning with the roadmap, including the need to wrap up product definition and design mockups for future versions (V0.2 and V0.3).
  • Engineering Starts: Engineering work from the Fueled side is scheduled to begin within the next week or so.
  • Abilities Integration: The key question remains: which Abilities API features (those that will land in 6.9) will be exposed and built upon within the AI Experiments plugin?

Basic Admin Setting Screen UXUX UX is an acronym for User Experience - the way the user uses the UI. Think โ€˜what they are doingโ€™ and less about how they do it.

  • Two Settings Concerns: There are two main concerns for the settings screen: 1) Provider Credentials and 2) Feature Toggles (enabling/disabling specific AI experiments).
  • Centralized Provider Settings: The ideal approach is to have a single, central screen to configure one or more AI providers, which all AI plugins (both Core and third-party) could then leverage. This prevents users from having to enter the same credentials multiple times.
  • Component-Based 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.: The team discussed the need for reusable UI components that allow individual feature settings pages to either select a pre-configured provider or offer a graceful flow (e.g., a modal) to add a new one without forcing the user to bounce out to the main settings page.
  • Friction Point: Tammy Lister and Jeff Paul emphasized that provider setup is the highest friction point for user adoption, requiring an emphasis on clear, informative design, especially regarding token usage and potential costs.

#core-ai, #meeting, #summary

neillmcshea 1:29 am on 2 October 2025
Tags: core-ai, ,   

Core-AI Contributor Check-in โ€“ Oct 1st, 2025

High-Level Call Summary

The meeting focused primarily on progressing 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 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. for the upcoming 6.9 release, establishing clear next steps, and making key decisions to keep momentum. A spirit of urgency and a commitment to an iterative, โ€œalphaโ€ approach to early development were evident, particularly for the MCP Adapter, to avoid accruing technical debt and to accelerate testing. Key outcomes included narrowing the scope for abilities included in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 6.9 (focusing on the 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. itself and a few small, stable tools), agreeing to introduce categories as a required part 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. registration, and setting a plan to merge the major refactor of the MCP Adapter to enable wider testing. The team also celebrated a key personnel announcement regarding a transition to an AI-related engineering leadership role at Automatic.

Topics and Supporting Highlights

Abilities API Update & Milestones

The team reviewed the status of the Abilities API, which is a key focus for the upcoming release. A strong emphasis was placed on making necessary decisions quickly, with a general consensus that decisions could be made asynchronously due to high engagement.

  • The team is aiming for an optimistic release plan of one milestone, but pessimistically planning for a pre-6.9 and a 6.9 milestone.
  • There are several issues currently without milestones that need to be prioritized.
  • The project has 10 open Pull Requests (PRs), with 3 failing tests and 7 needing approval before they can be shipped or slated for a release.
  • A decision on issue #30 related to tooling over repos was postponed to prioritize 6.9 tasks.
  • Decisions regarding milestones were mostly made asynchronously due to team members jumping in and adding comments.

Abilities API: Core Inclusion & Roadmap

A major discussion point centered on the scope of abilities to include in the core 6.9 release, ultimately favoring a limited approach.

  • The Abilities API itself is the primary achievement for 6.9.
  • The decision was made to ship only one or two very small, stable tools with the core Abilities API in 6.9.
  • Gregโ€™s proposed site info was highlighted as a good candidate for a core ability, as itโ€™s a base unit of WordPress with useful information.
  • The longer list of proposed abilities (Issue #52) will be moved to 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 to allow for broader testing and exploration of different implementation approaches (e.g., naming conventions).
  • The roadmap for the Abilities API will be updated and shipped following the decision to limit core tools.

Abilities API: Categories Decision

A critical feature for organizing and exposing abilities to the AI was discussed and agreed upon.

  • The team agreed that categories should be a required part of registering an ability in the API.
  • This feature is necessary for the MCP Adapter to present an โ€œapproachable, discoverable set of abilitiesโ€ to the AI, rather than โ€œthrowing every single abilityโ€ at it.
  • Ovi is committed to owning the Pull Request (PR) to implement categories in both the Abilities API and the MCP Adapter repos.
  • It was clarified that a way to register a categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. separately will be needed since a category must have a description.

MCP Adapter Update and Stability

The discussion around the MCP Adapter focused on accelerating its release and addressing community concerns about the stability of the protocol itself.

  • The major refactor (0.3/third iteration) is considered a โ€œdeveloper versionโ€ or โ€œalphaโ€ and should be merged and released as soon as possible to allow for testing.
  • The team agreed to not worry about technical debt or deprecation warnings at this early, experimental stage, and to simply remove deprecated code in the current PR.
  • The goal is to have the 0.3 version available during the WordPress 6.9 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. period as the officially linked version in announcement posts.
  • Community concern about MCPโ€™s stability was addressed by reiterating that the adapter approach was specifically chosen to future-proof the Abilities API; if the MCP protocol changes or another standard emerges (like โ€œTypeCPโ€), the Abilities API remains reusable with a new adapter.
  • A plan was made to publish a blog post or strong communication before 6.9 to clarify the adaptive nature of the Abilities API and address these stability concerns.
  • James and (possibly) Jonathan will โ€œtag teamโ€ a post to encourage the 70 Core AI contributors to go test the new adapter release.

Action Items & Next Steps for the Week

This heading focuses on the immediate, assigned tasks and plans discussed to be completed before the next check-in.

  • Ship the MCP Adapter: The primary action is for Ovidiu and James to proceed with merging and releasing the major refactor (0.3) of the MCP Adapter after final review, despite its โ€œalphaโ€ state.
  • Write Testing/Announcement Post: James and Jonathan will collaborate on a post (likely a blog post or 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/. announcement) to encourage testing of the newly released MCP Adapter, setting clear boundaries and opportunities for community engagement.
  • Implement Categories PR: Ovidiu committed to creating the Pull Requests for the Abilities API and the MCP Adapter to implement categories as a required field for registering an ability.
  • Update and Publish Roadmaps: Tammy will finalize updates to the Abilities API roadmap (Issue #83) and the Experiments roadmap based on the decisions made (e.g., scoping the number of core abilities).
  • Check on Built-in Abilities: James will confirm with Greg (or another team member) the creation of the two basic, built-in abilities for 6.9 core (e.g., site info).

Contribution & Workflow Reminders

This section pulls out a specific process reminder about crediting contributors and mentions general developer exploration.

  • Co-Author Credit for PRs: Jeff reminded the team to be mindful of using the generated co-author-by text on PR comments when merging commits to ensure proper, liberal credit is given to all contributors (filtering out simple โ€œ+1, great ideaโ€ comments).
  • Modular Architecture Focus: A general architectural desire was restated to keep all features modular to easily pull features in and out, avoiding complex dependencies.
  • Future Ability Exploration: James noted an interest in doing personal exploration (not assigned work) using tools like GPT-5 Pro to test various ability naming conventions (e.g., verb naming) to see which is most effective for different AI models.
  • Potential for Non-AI Adapters: The idea was briefly resurfaced that the Abilities API could potentially be used to create adapters for non-AI contexts, like a command line (CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress.) or REST interface, providing โ€œfreeโ€ functionality for simple plugins.

Contribution & Workflow Reminders

The team addressed internal best practices and forward-looking architectural ideas, focusing on how contributions are credited and the potential future uses of the Abilities API structure.

  • Potential for Non-AI Adapters: The idea was briefly resurfaced that the Abilities API could potentially be used to create adapters for non-AI contexts, like a command line (CLI) or REST interface, providing โ€œfreeโ€ functionality for simple plugins.
  • Future Ability Exploration: James noted an interest in doing personal exploration (not assigned work) using tools like GPT-5 Pro to test various ability naming conventions (e.g., verb naming) to see which is most effective for different AI models.
  • Co-Author Credit for PRs: Jeff reminded the team to be mindful of using the generated co-author-by text on PR comments when merging commits to ensure proper, liberal credit is given to all contributors (filtering out simple โ€œ+1, great ideaโ€ comments).

Community Feedback & Strategic Communication

Proactive communication is planned to address community concerns regarding technical decisions and highlight the strategic approach being taken.

  • Plan Proactive Announcement: A commitment was made to publish a clear, strategic announcement (likely a blog post before 6.9) to explain the decoupled adapter architecture and celebrate its future-proofing advantage.
  • Defend the Adapter Approach: The response emphasizes that the Abilities APIโ€™s decoupled adapter architecture is the precise solution to community questions about the stability of the MCP protocol, allowing the core to remain stable regardless of external protocol changes.
  • Address MCP Stability Concerns: The team acknowledged the recurring community question about the stability of the MCP protocol and the risk of it being superseded by a better standard.

Action Items & Next Steps for the Week

The team established a short list of immediate, assigned tasks to be completed to maintain momentum toward the 6.9 release.

  • Check on Built-in Abilities: James will confirm with Greg (or another team member) the creation of the two basic, built-in abilities for 6.9 core (e.g., site info).
  • Update and Publish Roadmaps: Tammy will finalize updates to the Abilities API roadmap (Issue #83) and the Experiments roadmap based on the decisions made (e.g., scoping the number of core abilities).
  • Implement Categories PR: Ovidiu committed to creating the Pull Requests for the Abilities API and the MCP Adapter to implement categories as a required field for registering an ability.
  • Write Testing/Announcement Post: James and Jonathan will collaborate on a post (likely a blog post or Slack announcement) to encourage testing of the newly released MCP Adapter, setting clear boundaries and opportunities for community engagement.
  • Ship the MCP Adapter: The primary action is for Ovidiu and James to proceed with merging and releasing the major refactor (0.3) of the MCP Adapter after final review, despite its โ€œalphaโ€ state.

#core-ai, #meeting, #summary

Jonathan Bossenger 6:47 am on 26 September 2025
Tags: core-ai, ,   

AI Chat Summary โ€“ 18 September 2025

Location: #core-ai Slack Channelย 

Agenda: No formal agenda this week

The bi-weekly CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. AI meeting was held on September 18th, 2025:

Key discussion points:

  • WordPress 6.9 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: A reminder that the beta is scheduled for October 21st and when the first iteration of 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. will be merged into core.
  • Changing Package Type: @justlevine raised a topic about changing the package type of the Abilities API from a library to wordpress-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. @isotropic agreed to the change as it doesnโ€™t impact existing plugins. However, he suggests itโ€™s important to note in the docs and messaging that this is going core, and not intended to be a plugin. Currently the suggested way to use this pre 6.9 is using Composer to install it into the vendor directory. A good example of this is how WooCommerce has done it.
  • Composer Package Expectations: The team wants to define what they expect from a Composer package to align with architectural decisions.
  • Client-Side Abilities in 6.9: @isotropic expressed interest in including the client-side abilities in WordPress 6.9, noting that the relevant PRs are in a good state. However, the method of inclusion and the specific abilities to ship need to be determined.
  • Number of Abilities in Core: There was a consensus to include a minimal number of โ€œsparklyโ€ (i.e., impactful) abilities in 6.9, with the option to add more later. @flixos90 cited 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/. as an example of 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. shipped with few initial endpoints that were later expanded.
  • โ€œDiscover Abilitiesโ€ as a First 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.: @justlevine suggested making โ€œdiscovering abilitiesโ€ the first ability, referencing ChatGPTโ€™s initial connector specification.
  • 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. 0.2.0 Release: @psykro requested a 0.2.0 version of the MCP adapter, as only 0.1.0 is currently available on Packagist. This would allow for easier access to the latest code for demos. @ovidiu-galatan has a large pull request that could be considered for this release, despite its size, to avoid delaying needed functionality.

Decisions and Next Steps:

  • @isotropic and @gziolo will drive the conversation in the issues next week to decide on client inclusion and what abilities will ship in 6.9, aiming for a decision by mid-next week.
  • A release discussion issue will be created to set up a milestone for the MCP adapter 0.2.0 release.

#core-ai, #meeting, #summary

neillmcshea 9:22 pm on 25 September 2025
Tags: , core-ai,   

Core-AI Contributor Check-in September, 24 2025

Attendees:

  • Jason Adams
  • Jeff Paul
  • Grzegorz Ziรณล‚kowski
  • Ovidiu Galatan

Summary

Topics Covered & Recommendations

The discussion focused on defining the structure and scope of the WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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., particularly in preparation for the WordPress 6.9 release.

CRUD Operations for Abilities: The group discussed how to handle Create, Read, Update, and Delete (CRUD) operations for post types. It was recommended to move away from a single โ€œCRUDโ€ 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. for a given post type. Instead, the recommendation is to break operations into separate abilities to allow for clearer annotations (e.g., marking โ€œdeleteโ€ as destructive) and to improve how AI models interact with them. Jason noted that โ€œCreateโ€ and โ€œUpdateโ€ could be reliably combined into a single ability, where the presence of an ID parameter would indicate an update. It was recommended that โ€œReadโ€ and โ€œDeleteโ€ remain separate abilities.

Handling Different Post Types: A key topic was whether to create a single set of abilities that can operate on any post type via a parameter, or to create discrete abilities for each post type. The group leaned toward recommending the creation of discrete abilities for each post type (e.g., posts, pages). This approach would avoid confusing AI models with WordPress-specific data concepts and the terminology that can arise (e.g., a โ€œpostโ€ of type โ€œpostโ€).

Permissions and Security: Grzegorz highlighted the need to account for WordPressโ€™s granular, context-aware permission levels. The current system uses a permissions callback that receives request parameters to make contextual decisions. The group also discussed the idea of an โ€œability vetting checkโ€ to pre-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. abilities based on a userโ€™s role to avoid exposing tools they cannot use.

Ability Organization: Namespaces and Categories: The conversation covered methods for organizing a large number of abilities, especially for AI consumption via a layered tool approach.

Namespaces: It was discussed that namespaces should be used to indicate ownership and prevent naming conflicts.

Categories: It was proposed that categories would group abilities by function. For AI, this allows a model to first request a list of categories and then request the specific abilities within a chosen categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging., which prevents performance degradation as the number of abilities grows. It was recommended that categories be registered with their own descriptions so the AI can understand their purpose.

Nuances of WordPress Actions: The group noted that standard terms like โ€œdeleteโ€ have special meaning in WordPress, where an item is typically moved to the trashTrash Trash in WordPress is like the Recycle Bin on your PC or Trash in your Macintosh computer. Users with the proper permission level (administrators and editors) have the ability to delete a post, page, and/or comments. When you delete the item, it is moved to the trash folder where it will remain for 30 days. rather than being permanently deleted. The phrasing and description of abilities must be clear to explain these nuances to an AI.

Next Steps

The primary goal is to finalize the scope of the Abilities API for WordPress 6.9.

Finalize 6.9 Scope: The team needs to decide what a user should be able to accomplish with the 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. in the 6.9 release to create a cohesive and valuable system from the start. The main tangible use case driving development is the MCP (Multi-Content Platform) adapter.

Implement Core Features for 6.9: Based on the discussion, Grzegorz recommended prioritizing two key features for the next two weeks:

  1. Ability Filtering: Add the functionality to query for abilities based on criteria like namespace or category.
  2. 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/. Exposure Control: Implement a flag or property that allows developers to prevent an ability from being exposed via the REST API, for abilities intended for server-side use only.

Decide on Required Categories: A decision needs to be made on whether to require a category for every ability registration in version 6.9. Jason advocated for this to ensure the system scales well with a growing number of abilities , while Grzegorz raised the concern that users might just default to an โ€œuncategorizedโ€ option.

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

neillmcshea 3:47 pm on 10 September 2025
Tags: , core-ai,   

Core-AI Contributor Check-in โ€“ Sept 10th, 2025

Announcements (5 min)

Progress this week

Abilities update (@karmatosed )

Milestones:

  • Added a v0.1.2: which is next for pre 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. (more milestones to come)
  • Added an 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. board to monitor what is going on with project and include all milestones. https://github.com/orgs/WordPress/projects/252/views/1

Info:
Using board to surface:
https://github.com/orgs/WordPress/projects/252/views/2?sliceBy%5BcolumnId%5D=Milestone

Experiments Update (@jeffpaul)

Milestones:

  • TBD

Info:

  • Assembling additional issues with feature definition and mockups
  • Compiling overall Agenda issue to link out to various sub-issues for milestone releases ahead of WP 6.9
  • Synthesizing existing issue feedback to iterate on definition & mockups
  • Scaffold 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 & being building out features

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. Update (@jeffpaul)

Milestones:

  • TBD

Info:

  • Assembling additional issues with feature definition and mockups
  • Compiling overall Agenda issue to link out to various sub-issues for milestone releases ahead of WP 6.9
  • Synthesizing existing issue feedback to iterate on definition & mockups
  • Scaffold plugin & being building out features

Questions/Decision points (15 min)

Weekโ€™s goals (10 min)

  1. (Start) Roadmaps for all projects in 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 be the repository owner. https://github.com/
    1. Abilities โ€“ James, Tammie : get roadmap out or pass out trying
    2. MCP โ€“ Neill, James, Ovi (Neill did not make progress on this, last week ๐Ÿ™ )
    3. Experiments โ€“ Jeff
    4. Client JS Package: Jason, Felix

AI Generated Summary of the Call (Posted after the call)

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

Tammie Lister 10:31 am on 5 September 2025
Tags: core-ai,   

AI Chat Summary โ€“ 4 September 2025

Location: #core-ai Slack Channelย 

Agenda: No agenda this week

The bi-weekly CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. AI meeting was held on 4 September , 2025:

WCUS & 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/.

@jeffpaul highlighted the recent faceโ€‘toโ€‘face sessions on the Core AI table at 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.โ€ฏUS and thanked @justlevine for coordinating remote participation.

Handbook & Badge Development

@karmatosed facilitated work on refining the AI handbook and creating the WordPress AI badge. There are a number of new pages for the handbook including the Contributing badge page.

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 โ€“ 0.1.0 MVPMinimum Viable Product "A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development." - WikiPedia & Roadmap

@jason_the_adams announced the 0.1.0 MVP release for the PHP AI Client, with a demo shown on stage. The demo code is on 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 be the repository owner. https://github.com/:โ€ฏhttps://github.com/felixarntz/wp-ai-sdk-chatbot-demo
Roadmap items for versions 0.2.0โ€“0.4.0 are on the issue board:โ€ฏhttps://github.com/WordPress/php-ai-client/issues/8

Project Updates

WPโ€‘Specific Layer โ€“ WordPress AI Client

@flixos90 explained progress on wpโ€‘aiโ€‘client: the layer adapts the generic PHP SDK to WordPress, adds a settings screen for 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. credentials, and provides REST endpoints for clientโ€‘side usage. The project is in early workโ€‘inโ€‘progress; interested contributors can follow issue #1:โ€ฏhttps://github.com/WordPress/wp-ai-client/issues/1

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. & WPโ€ฏ6.9 Timeline

@jeffpaul noted that the Abilities API effort is the most urgent for the WPโ€ฏ6.9 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 release on Octoberโ€ฏ21. @karmatosed applied a milestone to the issue, giving the team a sense of time. @isotropic is working on the roadmap with @karmatosed for this weekโ€™s priority.

AI Experiments 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

@jeffpaul shared work is going on to create a GitHub issue that consolidates the roadmap and a highโ€‘level list of planned features. Feedback from Contributor Day is welcome, and a formal roadmap issue will be added next week.

Sharing

#core-ai, #meeting