Location: #core-ai Slack Channel
Agenda: AI Chat Agenda – 26 June 2025
Project Administration
- @isotropic outlined GitHub project setup to coordinate WordPress AI efforts.
- Introduced the new php-ai-client GitHub repository.
- Plans for related repos for other “building block” focuses such as MCP and unified tool registry.
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 extensible 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 migration 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 core 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 Plugin 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 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 API parity.
- @jason_the_adams committed to raising topics as GitHub issues.
Props to @jeffpaul for review.