Tammie Lister 9:40 pm on 26 June 2025
Tags: , , ,   

AI Chat Summary – 26 June 2025

Location: #core-ai Slack Channel

Agenda: AI Chat Agenda – 26 June 2025

Project Administration

  • @isotropic outlined 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/ project setup to coordinate WordPress AI efforts.
  • Introduced the new php-ai-client GitHub repository.
  • Plans for related repos for other “building 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.” focuses such as MCP and unified tool registry.

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 SDK

TL;DR: The php-ai-client SDK will be a vendor-neutral PHP foundation, extended by a WordPress-specific layer.

  • @flixos90 described the php-ai-client as:
    • A platform-agnostic PHP SDK for connecting to AI models.
    • Designed to be extensibleExtensible This is the ability to add additional functionality to the code. Plugins extend the WordPress core software. and vendor-neutral.
  • @isotropic noted a WordPress-specific layer would build on this foundation.
  • @dan2k3k4 mentioned external contributions from amazee.ai aiming to integrate AI provider support.

Provider Inclusion, Structure, and Extensibility

TL;DR: Provider support will be modular and extensible, starting with initially identified vendors. Proxy architecture and advanced features like cost management are key priorities.

  • @flixos90 introduced provider inclusion strategies:
    • No providers bundled (all external).
    • All providers bundled (with strict criteria).
    • Selective bundling based on clear criteria.
    • Highlighted difficulty of setting unbiased, verifiable inclusion rules.
    • Suggested a stakeholder approval process for new providers.
    • Recommended starting with “big 3” providers (OpenAI, Anthropic, Google) in separate branches.
    • Preferred eventual migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. of providers to separate repositories.
  • @isotropic favored:
    • Bundling widely adopted providers with stable APIs.
    • Documenting unofficial provider modules with potential promotion based on usage.
  • @jason_the_adams and others discussed monorepo versus multiple repositories for managing provider modules.
  • Proxy provider and hosting integration emphasized by @jason_the_adams and @isotropic, with @flixos90 adding SDK architectural support for proxying.
  • Advanced feature support discussed by@zhendershot and @flixos90 including cost management, model routing handled at WordPress-specific layer with extensibility.
  • @jeffpaul referenced WordPress’s OEmbed provider process as a precedent: WordPress Core Trac Ticket #58840
  • Roadmap outlined for integrating AI features into WordPress with no near-term coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. merge planned.

Proxy Providers and Hosting

TL;DR: Hosting providers may bundle AI capabilities via proxies. Integration with hosts like amazee.ai is underway to drive adoption.

  • @jason_the_adams detailed proxy use cases where hosts bundle AI credits and monitor usage.
  • @isotropic and @flixos90 discussed:
    • Host registration of providers versus proxying.
    • SDK’s capability to route requests via proxy endpoints.
  • @dan2k3k4 shared amazee.ai’s intent to be a provider and collaboration efforts with WordPress agencies.
  • @jason_the_adams emphasized hosting adoption is key for WordPress AI success.

Repository Architecture

TL;DR: Monorepo favored for adaptability, but some prefer modular repos for clearer issue and project management.

  • @jason_the_adams advocated for monorepo structure for flexibility and version management.
  • @karmatosed preferred separate repositories for better project and issue management.
  • @isotropic supported monorepo approach for adaptability and hosting flexibility.

Roadmap and Core Integration

TL;DR: Project will roll out as a Canonical/Feature PluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. first, with no immediate plans to merge into WordPress core.

  • @sirlouen asked whether the project aligns more with a Feature Plugin than Core at this stage.
  • @flixos90 and @isotropic agreed:
    • Phased approach with separate packages.
    • No immediate core merge planned.
    • WordPress-specific code expected to ship initially as a Feature Plugin.

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/. Handling

TL;DR: REST API specs may live in the SDK repo, but broader design and GraphQL parity are being considered. Further discussion will continue on GitHub.

  • @jason_the_adams expressed enthusiasm for REST API specification residing in the php-ai-client repo: REQUIREMENTS.md in php-ai-client
  • @flixos90 agreed:
    • It’s a good idea worthy of further discussion.
    • Leans pragmatic but sees broader specification’s scalability benefits.
    • Encouraged ongoing discussions in php-ai-client GitHub repository
  • @justlevine hopes:
    • REST handling remains outside core SDK.
    • WPGraphQL aims to offer 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. parity.
  • @jason_the_adams committed to raising topics as GitHub issues.

Props to @jeffpaul for review.

#core-ai, #docs, #meeting, #summary