PHP AI Client SDK - CourtneyR.dev's 2nd Brain

PHP AI Client SDK 🔗 **Source:** [PHP AI Client SDK](https://www.youtube.com/watch?v=lNAh5B0xh6I) > [!note]+ Document Notes > tags: [wordpress-ai, php-development, sdk-integration] > author: WordPress AI Team > source: YouTube > reference: https://www.youtube.com/watch?v=lNAh5B0xh6I > date created: 2025-01-17 14:30 > > # 🏷️ Title: PHP AI Client SDK - Connecting WordPress to External AI Models >  ## 🧰 Action Inbox - [H1] Set up proper API credentials configuration — troubleshooting authentication #wordpress-ai - [H2] Create working plugin demo with PHP AI Client SDK — development continuation #php-development - [H3] Test model integration with OpenAI and Anthropic — API validation #ai-integration ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - [PHP AI Client SDK Repository](https://github.com/WordPress/php-ai-client) - [WordPress AI Experiments Plugin](https://github.com/WordPress/ai-experiments) ## 📝 Summary - Live coding session exploring the PHP AI Client SDK for WordPress AI integration - Demonstrates provider-agnostic approach to connecting WordPress with external AI models - Shows the relationship between Abilities API, MCP adapter, and PHP AI SDK components - Encounters authentication challenges during plugin development and testing - Sets foundation for future AI-powered WordPress plugin development ## 📖 Main Content The PHP AI Client SDK provides shared infrastructure that allows WordPress plugins and PHP projects to integrate AI capabilities rapidly and flexibly. Similar to projects like the Vercel AI SDK, it offers a unified interface that works across AI providers from simple text generation to complex multimodal operations, streaming responses, and long-running tasks. The SDK addresses both user and developer needs through a provider-agnostic approach. Site administrators choose which provider and model they want to configure, providing API credentials in a single place that work automatically across all compatible plugins. Developers can focus on building AI features rather than AI infrastructure, using centralized plumbing instead of reinventing integration code. The architecture consists of modular components: the core PHP package provides the unified AI interface and is WordPress-agnostic, making it collaborative with the wider PHP community. A complementary WordPress-specific package adds features tied to WordPress, such as shared settings pages for AI API credentials and connection to the Abilities API. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/lNAh5B0xh6I?t=0) — [H1] Introduction to PHP AI Client SDK - Key idea: Exploring project that allows WordPress to connect to external AI models - Evidence: "PHP AI client SDK which basically allows any WordPress project to connect to external models" #### ⏱️ [02:15](https://youtu.be/lNAh5B0xh6I?t=135) — [H2] Architecture diagram explanation - Key idea: Three building blocks - Abilities API, MCP adapter, and PHP AI SDK - Evidence: "The abilities API is the layer that allows WordPress to publish the features it has so external agents can know what our WordPress can do" #### ⏱️ [04:30](https://youtu.be/lNAh5B0xh6I?t=270) — [H1] PHP AI SDK as proxy layer - Key idea: SDK serves as intermediate layer for communicating with external models - Evidence: "This is like a proxy is an intermediate layer that we can use to communicate with the outer space" #### ⏱️ [06:45](https://youtu.be/lNAh5B0xh6I?t=405) — [H2] Provider-agnostic unified interface - Key idea: Works across all AI providers with consistent API - Evidence: "It offers a unified interface that works across all AI providers from simple text generation to complex multimodel operations" #### ⏱️ [08:20](https://youtu.be/lNAh5B0xh6I?t=500) — [H2] Credential management system - Key idea: Users manage provider credentials in one centralized location - Evidence: "Users manage their provider credentials in one place. Those credentials then work automatically across all compatible plugins" #### ⏱️ [12:30](https://youtu.be/lNAh5B0xh6I?t=750) — [H2] Environment variables for API keys - Key idea: Credentials can be defined through environment variables for automatic detection - Evidence: "If I define a specific environment variables then the plugin automatically detects them" #### ⏱️ [15:45](https://youtu.be/lNAh5B0xh6I?t=945) — [H1] User-first provider-agnostic approach - Key idea: Site administrators choose providers while plugins just work - Evidence: "WordPress site administrators choose which provider and/or model they want to configure. Any plugins with AI features just work" #### ⏱️ [18:30](https://youtu.be/lNAh5B0xh6I?t=1110) — [H2] Developer benefits and focus - Key idea: Developers focus on AI features rather than infrastructure plumbing - Evidence: "Developers can focus on building AI features, not AI infrastructure. The SDK gives developers the central infrastructure to get started quickly" #### ⏱️ [22:15](https://youtu.be/lNAh5B0xh6I?t=1335) — [H2] Future browser-based AI anticipation - Key idea: Architecture designed to anticipate client-side AI capabilities - Evidence: "The architecture is designed with latest trends like multimodel first in mind and even anticipates future shifts like client side or browser based AI" #### ⏱️ [25:00](https://youtu.be/lNAh5B0xh6I?t=1500) — [H1] Modular architecture with two packages - Key idea: PHP-agnostic core package plus WordPress-specific additions - Evidence: "The underlying PHP package provides the unified AI interface and it is WordPress agnostic. It is a collaborative for with the wider PHP community" #### ⏱️ [30:45](https://youtu.be/lNAh5B0xh6I?t=1845) — [H2] Plugin development setup - Key idea: Installing SDK as Composer dependency in WordPress plugin - Evidence: "We install this as a dependency and then we just use the namespace so we can make calls to the specific methods" #### ⏱️ [45:30](https://youtu.be/lNAh5B0xh6I?t=2730) — [H2] Testing environment configuration - Key idea: Setting up development environment with symlinks and WP-CLI - Evidence: "I'm going to create a sim link to the project and use WP shell to test the functionality" #### ⏱️ [52:15](https://youtu.be/lNAh5B0xh6I?t=3135) — [H3] Authentication troubleshooting - Key idea: Encountering "no models found" errors despite proper API key setup - Evidence: "No models found that support text generation for this prompt. So the function is working properly but something is going on" #### ⏱️ [58:00](https://youtu.be/lNAh5B0xh6I?t=3480) — [H3] Stream conclusion and next steps - Key idea: Planning continuation in next session to resolve authentication issues - Evidence: "Next week I will do a second part of this because I want to really move forward with this and being able of calling this function successfully" ## 📚 References - [PHP AI Client SDK](https://github.com/WordPress/php-ai-client) - [WordPress AI Experiments Plugin](https://github.com/WordPress/ai-experiments) - [Vercel AI SDK](https://sdk.vercel.ai/) - [WP-CLI](https://wp-cli.org/) ## 🗣️ Paraphrase - The PHP AI Client SDK creates a unified way for WordPress plugins to connect with various AI providers without vendor lock-in, allowing site administrators to configure credentials once and developers to focus on features rather than integration complexity - The architecture includes three main components: an Abilities API for publishing WordPress capabilities, an MCP adapter for external communication, and the PHP AI SDK for outbound model connections - Despite thorough setup and valid API credentials, the demonstration encountered authentication issues that prevented successful model communication, highlighting the need for continued troubleshooting in future sessions ## 📰 Newsletter The WordPress AI ecosystem continues to mature with the PHP AI Client SDK, offering a provider-agnostic approach to AI integration that puts both users and developers first. This unified interface allows site administrators to configure AI credentials once while enabling plugins to work seamlessly across different providers like OpenAI, Google, and Anthropic. The modular architecture anticipates future trends including browser-based AI capabilities, making it a forward-thinking solution for the broader PHP community beyond just WordPress. Developers can leverage this centralized infrastructure to focus on building meaningful AI features rather than reinventing integration plumbing. While still in active development with some authentication challenges to resolve, this SDK represents a significant step toward democratizing AI capabilities across the WordPress ecosystem. Resources: [PHP AI Client SDK](https://github.com/WordPress/php-ai-client), [AI Experiments Plugin](https://github.com/WordPress/ai-experiments), [Developer Docs](https://developer.wordpress.org/) ## ✅ Action Items #### WordPress - Core AI: Resolve authentication flow for PHP AI Client SDK integration - Core Program Team: Document credential management best practices for AI providers - Documentation: Create comprehensive guides for PHP AI Client SDK implementation - Community: Develop training materials for AI-powered plugin development #### DevRel - Developer advocacy: Create tutorials and demos for PHP AI Client SDK usage - Education: Design workshops on provider-agnostic AI integration patterns - Developer experience: Improve SDK documentation and error messaging - Community management: Facilitate discussions on AI integration challenges ## 🧪 Hypotheses - Provider-agnostic AI SDKs reduce vendor lock-in and improve plugin ecosystem flexibility - Centralized credential management increases security and user experience consistency - Unified interfaces accelerate AI feature development across WordPress plugins - Modular architecture enables easier adaptation to emerging AI technologies ### 📊 Methodology - Live coding demonstrations to test SDK integration patterns - Comparative analysis with existing AI SDKs from other ecosystems - User experience testing for credential management workflows ### ❓ Questions - How can authentication flows be simplified for developer adoption? - What provider detection mechanisms work best for automatic model selection? - How should the SDK handle rate limiting and error recovery across providers? ### 🔮 Future Research - Browser-based AI integration patterns and implementation strategies - Performance benchmarking across different AI providers and model types - Security implications of centralized credential management systems ### 💡 Implications - Practice: Standardized AI integration patterns across WordPress plugin ecosystem - Policy: Need for clear guidelines on AI provider credential handling - Security: Centralized credential storage requires robust security measures - Education: Developer training needed for provider-agnostic AI development - Funding: Investment in AI infrastructure benefits entire PHP community ### 🧠 Learning Styles Assessment Reading level estimate: Grade 12-14 (technical documentation) #### 👀 Visual learners - Present: Architecture diagrams showing component relationships - Improve: API flow diagrams, credential management workflows #### 🔊 Aural learners - Present: Live coding commentary and explanation - Improve: Audio tutorials for SDK integration steps #### 🗣️ Verbal learners - Present: Clear explanations of technical concepts and provider relationships - Improve: Glossary of AI and SDK terminology #### 🧩 Kinesthetic learners - Present: Hands-on coding demonstration and plugin development - Improve: Step-by-step implementation guides with checkpoints #### 🧠 Logical learners - Present: Modular architecture explanation and component relationships - Improve: Decision trees for provider selection and error handling #### 🧑‍🤝‍🧑 Social learners - Present: Live streaming format with community interaction - Improve: Collaborative debugging sessions and peer review #### 🧘‍♀️ Solitary learners - Present: Individual coding exploration and experimentation - Improve: Self-paced tutorials and reflection exercises #### 🌿 Naturalistic learners - Present: Ecosystem thinking about WordPress AI components - Improve: Environmental impact discussions of AI provider choices ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Clear heading structure in documentation - Improve: Better alt text for architectural diagrams #### Keyboard navigation - Present: Standard web interface navigation - Improve: Keyboard shortcuts for development workflows #### Contrast and readability - Present: Standard code editor contrast - Improve: High contrast themes for coding demonstrations #### Text resizing and reflow - Present: Responsive documentation layout - Improve: Better mobile experience for code examples #### Media and captions - Present: Live video stream - Improve: Auto-generated captions and transcripts #### Forms and interactions - Present: Basic plugin configuration interface - Improve: Better error messaging and validation feedback ### 🌍 DEIB Assessment #### Cultural breadth - Present: English-language presentation - Improve: Multi-language documentation and examples #### Inclusive language - Present: Technical terminology without exclusionary language - Improve: Plain language explanations alongside technical terms #### Neurodiversity support - Present: Structured, step-by-step approach - Improve: Multiple learning modalities and pacing options #### Representation - Present: Technical focus without explicit representation - Improve: Diverse use cases and contributor acknowledgment #### Psychological safety - Present: Acknowledgment of challenges and learning from failures - Improve: Explicit encouragement for experimentation and mistakes ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Provider-agnostic architecture reduces vendor lock-in (architectural principles) - Inductive strength: Similar patterns successful in other ecosystems (Vercel AI SDK evidence) - Causal reasoning: Centralized credentials improve user experience (UX principles) - Analogical strength: WordPress ecosystem benefits mirror broader PHP community needs #### Fallacies - Appeal to authority: Referencing Vercel AI SDK success without detailed comparison analysis - Hasty generalization: Assuming authentication issues represent broader SDK problems #### Tone of voice - Overall tone: Exploratory and educational with honest acknowledgment of technical challenges ### 🛡️ DARVO Analysis - Deny: No denial patterns present - Attack: No attack patterns observed - Reverse victim/offender: No reversal patterns identified - Emotional cues and rhetoric: Collaborative, learning-focused approach with transparency about challenges ## 🎯 Conclusion The PHP AI Client SDK represents a significant advancement in WordPress AI integration, offering a provider-agnostic approach that benefits both developers and users. While technical challenges around authentication remain to be resolved, the modular architecture and unified interface design position it well for the evolving AI landscape. The next development session will focus on resolving credential management issues to demonstrate successful AI model integration. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad Purpose: Stage CEE units that become Literature notes. Split level: H3 ### [H1] PHP AI Client SDK provides unified AI interface > [!quote] [PHP AI Client SDK](https://youtu.be/lNAh5B0xh6I) by [[WordPress AI Team]] via [[YouTube]]. Published 2025-01-17. Accessed 2025-01-17. > "PHP AI client SDK which basically allows any WordPress project to connect to external models." Demonstrates provider-agnostic approach to AI integration in WordPress ecosystem. [view highlight](https://youtu.be/lNAh5B0xh6I?t=0#H1) #wordpress-ai #articleseed ID:rw_php_ai_sdk ### [H2] Centralized credential management reduces complexity > [!quote] [PHP AI Client SDK](https://youtu.be/lNAh5B0xh6I) > "Users manage their provider credentials in one place. Those credentials then work automatically across all compatible plugins." Shows how --- ## Full Transcript [04:36] Okay. Hello. Hi. [04:41] We're live and [04:44] we are going to [04:47] to explore a little bit this project [04:51] called PHP AI client SDK [04:56] which [04:57] basically [05:00] allows any WordPress project to [05:04] to connect to external models. [05:08] So [05:10] yeah, let's talk a little bit about that [05:11] and how it connects with all the [05:18] AI related projects in WordPress such as [05:23] uh [05:28] the abilities API, the MCP adapter, and [05:31] the AI experiments plug-in. [05:35] So I'm going to share this link here. [05:43] Um [05:45] so yeah let's start [05:48] let's start from a diagram that I have [05:51] uh somewhere. So let me [05:55] let me find it. [05:58] Where do I have it? [06:01] See if I can find it [06:05] in my [06:12] Oh, I have done some other [06:17] streams about AI and in one of them I [06:20] created a diagram. [06:24] I think it was this one. [06:28] Maybe this one. [06:32] This is the [06:41] No, this is not the one. [06:49] Sorry. [06:52] No, this is not the [06:55] the one I'm looking for. I think is this [06:57] one scaled. [07:03] Yeah, this isn't the diagram I was [07:06] looking for. So, we have here the [07:09] different building blocks which are the [07:14] abilities API, MCP adapter and PHP AI [07:18] SDK. [07:20] The abilities API is the [07:25] layer that allows purpose to [07:29] publish the features it has so [07:34] external agents can know what [07:38] our WordPress can do. [07:42] This is an API that can be used from [07:45] external agents but also from internal [07:48] plugins and from internal features such [07:51] as the the common for. [07:54] They can be [07:59] published or they can be [08:02] made public via an MCP adapter which [08:08] will [08:11] make that with an MCP agent. [08:15] We can communicate with our WordPress [08:19] and we can [08:21] al some of the tools our WordPress has [08:25] to offer and those tools will be the [08:29] abilities [08:30] um automatically converted into tools by [08:34] the MCB adapter. So this is [08:42] one angle [08:46] from which our WordPress can [08:50] use AI [08:53] or how LLM [08:56] um models can [09:01] LLM are large language models. how LLMs [09:05] can communicate with other workers um [09:09] via MCP and can run tools [09:14] defined as abilities [09:18] but also our workers can communicate [09:22] with external models. [09:24] This is it can [09:28] call models to perform actions. [09:33] For example, we can [09:36] summarize content. We can create images [09:38] from prompts. We can do all of that. We [09:40] can convert our [09:43] WordPress instance into a [09:49] into an AI agent that can do can do [09:53] stuff. [09:55] And in order to do that, we have this [09:58] layer which is the PHP AI SDK which is [10:02] what we are going to explore today. So [10:06] via this layer or this um plug-in [10:12] we this is like a a proxy is an [10:16] intermediate layer that we can use to [10:18] communicate with the [10:21] with the outer space. We can communicate [10:24] with models such as Gemini, [10:31] Sonnet. [10:33] We can [10:36] communicate with different models and we [10:37] can ask them to do things uh through [10:41] this [10:42] uh proxy and this will normalize the [10:46] typical actions. [10:51] So yeah, let's um [10:54] have a look at this uh repository. [11:09] Okay. So first we have this [11:13] presentation like the official [11:15] presentation of the project which was [11:18] done on like last summer July uh [11:25] 2025. [11:33] Okay. So let's uh let's read a little [11:35] bit about this. [11:40] So it says the PHP AI client SDK [11:47] provides shared infrastructure that lets [11:51] WordPress plugins and all the PHP [11:54] projects integrate AI capabilities [11:57] rapidly and flexibly. So what we will do [12:01] today is create a plugin that uses this [12:04] um [12:06] this thing that I think is [12:11] shared in the form of [12:13] a plugin. [12:16] Let me see. [12:22] Is this a plugin? [12:31] No, it's um it's a composer package. So, [12:36] we need to [12:40] we need to [12:44] create a plugin. [12:46] install this package as a dependency. [12:49] It's a composer dependency of our [12:51] plug-in and then we need to call it [12:53] using the name space WordPress AI [12:56] client. [13:01] Um, okay. [13:04] Let's continue [13:07] reading. [13:11] Similar to projects like the Bersel AI [13:14] SDK, it offers a unite interface that [13:18] works across all AI providers [13:23] from simple text generation to complex [13:26] multimodel operations, streaming [13:29] responses, and long running tasks. Okay. [13:33] Developers specify what AI capabilities [13:36] they need and users manage [13:40] their provider credentials in one place. [13:45] Those credentials then work [13:46] automatically across all compatible [13:49] plugins on the site. So one thing we [13:51] will need to do is to [13:55] introduce all credentials and this is [13:58] something that in theory this [14:01] plug-in h manages. [14:05] Let me open another version [14:11] of this. Um, [14:20] okay. [14:31] Um [14:34] I want to come here [14:38] from here say deep. [14:47] Let's ask questions like for example um [14:57] how do you how do I use this project in [15:01] a plug-in [15:03] and also [15:05] okay that [15:13] I guess it's by um yeah We [15:23] Okay, perfect. So, we install this as a [15:26] dependency and then we just um [15:31] use the name space so we can make calls [15:35] to the specific [15:39] specific uh methods. [15:43] Okay, it has two ways but then also um [15:49] okay the different providers [15:53] require [15:54] a specific API key. [15:58] How are these credentials [16:03] entered [16:05] if I use this package directly from a [16:10] plugin? [16:30] Okay. So if I define a specific [16:34] environment [16:36] variables [16:40] then the plug-in automatically [16:45] detects them. [16:53] Mhm. [16:56] Um [17:01] okay. [17:06] Or we can also depending on the we need [17:11] to use different providers and they can [17:14] be open AAI, Google provider, anthropic [17:17] provider. [17:20] For example, we [17:23] we're going to do some tests just with [17:26] one provider. So we can do um [17:34] registry [17:36] new provider registry [17:40] and then we [17:48] okay so I guess the easiest way is this [17:51] one [17:56] plugin implementation example here's how [17:58] to implement this in a WordPress plug-in [18:00] so we uh in your plug-in bootstrap file [18:04] we do is [18:07] we um set credential [18:12] from plug-in options or [18:16] okay from plug-in options alth config. [18:19] So yeah, so the idea is that in our [18:22] plug-in we create like a panel where the [18:25] the user can introduce the API key [18:30] and if uh that doesn't exist in our case [18:33] we directly um [18:37] define that. So we can simplify this in [18:40] our in our example just by saying this [18:45] you can check if a provider is [18:47] configured using is provider code [18:56] provider registry and model discovery. [19:07] interesting [19:11] but yeah let's continue with the [19:17] okay so the credentials [19:20] uh thing are clear and let's continue [19:23] the SDK addresses both user needs and [19:26] developer needs a provider agnostic [19:29] approach puts the user first [19:33] and the WordPress site administrators [19:35] choose which provider and or model they [19:38] want to configure and use. They can [19:39] provide API credentials in a single [19:41] place. Any plugins with AI features just [19:45] work. No more vendor locking. [19:52] Okay. [19:54] So the way it works is that there is a [19:56] panel where the credentials are [19:58] introduced and then the the the calls [20:02] that are done via this plug-in they just [20:05] work even if we change models and I [20:08] think it has some [20:10] we can check that later. I think it has [20:12] some logic to decide which model is the [20:19] um the best option depending on the [20:22] depending on the task to do. So yeah, [20:25] we'll check this later. [20:28] Developers can focus on building AI [20:30] features, not AI infrastructure. Instead [20:33] of trying to find an an official SDK for [20:36] a single provider or having to even [20:38] build it yourself, the SDK gives [20:41] developers the central infrastructure to [20:44] get started quickly and focus on the [20:46] user benefits rather than their own [20:48] plugins technical plumping. No more [20:50] reinventing the web. Yeah. [20:53] So this is like a central layer that um [20:58] provides all the plumbing. [21:03] So plug-in developers can directly use [21:06] AI features. They don't need to worry [21:07] about the specific calls that uh need to [21:11] be made to the final [21:14] uh model. [21:19] They can just do things like this like I [21:22] client prompt whatever. Okay. How it [21:24] works? The API adapts to different [21:26] developer needs. Some plug-in solutions [21:30] may require specific models [21:35] while others just need any text [21:37] complication capability. The PHP AI [21:40] client is the handles all the complexity [21:42] behind the scenes different [21:44] authentication methods, API formats, [21:46] streaming protocols and provider that [21:48] works all work through the same clean [21:51] interface. So here's a simple tentative [21:54] code example for generating text using a [21:58] specific mode. [22:04] Okay, but in the same example but [22:05] written in a model and provider agnostic [22:08] way [22:11] and this can use uh behind the curtains. [22:14] This can use like any model define [22:19] the problem it solves. Uh today every [22:22] WordPress plug-in with AI features [22:24] rebuilds the same infrastructure [22:26] provider integrations, API key [22:28] management, response normalization, [22:31] error handling. Users enter the same [22:34] credentials multiple times and deal with [22:36] inconsistent experiences. [22:40] When providers change their APIs, every [22:42] plug-in breaks separately. It is worth [22:45] highlighting that these problems not [22:48] only exist in WordPress, but in more or [22:50] less every PHP project that aims to use [22:53] AI in a provider agnostic way. The only [22:57] truly provider agnostic SDKs that exist [23:01] today are for other tech stacks that are [23:05] not interoperable with general PHP [23:08] projects. either different serverside [23:12] languages like the burcell versel AI SDK [23:16] for nodes or a specific platforms like [23:19] Drupal's AI module. [23:22] So the PHPI client SDK centralizes this [23:26] complexity for the PHP ecosystem and in [23:29] WordPress WordPress specifically one [23:33] integration point handle all providers [23:37] one credential system serves all plugins [23:43] providers update or new ones emerge. The [23:46] changes happen once and benefit [23:47] everyone. The architecture is designed [23:49] with latest trends like multimodel first [23:52] in mind and even anticipates future [23:54] shifts like client side or browser based [23:58] AI. Yeah, I'm really interested in this. [24:02] Uh I think right now this is not [24:06] this is not um [24:15] it's not implemented. Um, let's talk a [24:18] little bit about this. [24:22] So, [24:33] okay. [24:36] So, for example, there are browsers like [24:39] Chrome. [24:51] So there are browsers like Chrome that [24:58] they provide a built-in AI capabilities [25:02] AI [25:06] internal models at least they provide [25:09] specific features that [25:12] run um [25:17] with AI internally like they have [25:20] different APIs, summarizer, [25:24] grader, proof reader, translator API, [25:27] prompt API [25:31] and [25:36] this is interesting because [25:39] this architecture is designed uh [25:42] anticipating future ships like client [25:44] side or browser based AI. [25:51] But I think right now this is not [25:54] possible because the current [25:58] implementations that we have are only [26:00] for these uh three providers [26:04] which means we can only [26:06] um communicate right now with uh models [26:10] of these companies. [26:13] But I guess that the idea is that we can [26:16] define our own providers or we can [26:18] submit a pull request with a new [26:20] provider that um [26:26] would enable the communication with a [26:29] browserbased AI. That would be an [26:32] interesting [26:34] an interesting future. [26:37] Okay. Build together. So the PHP AI [26:40] client SDK technically consists of two [26:43] composer packages. [26:46] The underlying PHP package provides the [26:49] unified AI interface and it is WordPress [26:52] agnostic. [26:54] It is a collaborative for with the wider [26:56] PHP community. [27:14] So I think that it refers to Yeah, [27:17] that's why it's called PHP AI client [27:20] because it's not really a specific to [27:23] WordPress is a provider agnostic PHP AI [27:28] client SDK to communicate with any [27:30] generative AI models of various [27:33] capabilities using a uniform API. So [27:36] this is not a specific for WordPress. [27:39] This is something [27:42] that can be used in any PHP project. [27:46] We have here a provider agnostic uh PHP [27:51] AI client SDK to communicate with [27:55] yeah [27:59] but can be can be installed as a [28:01] composer package and in a plug-in [28:06] WordPress in a WordPress plugin [28:12] but it's not a plug-in itself. Okay. [28:17] While this project is stewarded by the [28:20] WordPress AI team members and [28:21] contributors, it is technically [28:23] WordPress agnostic. The gap the project [28:26] addresses is relevant for not only the [28:28] WordPress ecosystem but overall PHP [28:31] ecosystem. So any PHP project could [28:35] benefit from it. There's also no [28:37] technical reason to scop it to WordPress [28:39] as communicating with AI models and [28:42] their providers is independent of [28:44] WordPress built in APIs and par [28:49] paradigms. [28:53] Okay. Nice. Nice. This is uh more clear [28:57] to me now. [29:01] But this package that's why there are [29:04] like a building blocks. we have like [29:06] different uh [29:09] ports. This is complemented by another [29:12] WordPress specific package that adds [29:15] features technically tied to WordPress [29:20] such as the shared settings page for AI [29:23] API credentials, [29:25] connection to the abilities API and the [29:28] rest API endpoints to use AI [29:30] capabilities in JavaScript as well. [29:34] Um, okay. So I understand this part. [29:38] This is [29:42] completely [29:44] this project but [29:51] um [29:53] I'm not sure about this part. [29:59] So the PHP maybe this has evolved [30:03] because this was [30:07] this was the intention in July last year [30:10] and maybe this has evolved in some other [30:13] thing. Um [30:22] but yeah, let's uh read a bit more [30:28] to see. Um [30:38] let's ask uh Deep Wiki about this. [30:42] Um, [30:49] let's ask deep wiki about this. [30:54] Um, [30:56] are there any references in the [31:00] repository about this other [31:04] package that is more specific to [31:08] WordPress? [31:18] Let's see. [31:36] So [31:38] yeah, maybe this refers to the [31:42] I think this may be the AI experiments [31:45] plugin. This one. [32:00] Um, this uh project is the WordPress. [32:07] I think it's this one. [32:16] I think it's this one [32:20] because this provides a [32:25] live demo. Let's try this. I think this [32:28] provides a specific um dashboard to [32:33] enter the [32:37] the [32:39] credentials. [32:41] EI experiments. [32:48] Okay. Most experiments require the valid [32:52] AI credentials to function properly. To [32:54] ensure those work properly, you need to [32:56] have one or more AI credentials set [32:58] here. [33:01] So this is an example of how we can [33:04] introduce these uh credentials, this API [33:08] key. [33:11] control whether AI experiments are [33:13] enabled for your site disabled all [33:16] experiments. Okay. And then [33:20] once we have the credentials, we can [33:23] enable experiments. And the experiments [33:27] can be any of these ones that um [33:35] they [33:37] use this um [33:41] package. [33:43] In fact, if we go here to composer.json, [33:46] application. We should see [33:49] somewhere. Yeah, here it is. [33:54] WordPress wpai [33:57] client. This is the one. [34:02] Go to composer.json. [34:04] Yeah, WordPress PHP AI client. [34:10] And then let's also check [34:17] Let's also check this WordPress AI [34:21] client [34:26] AI clients. [34:32] So includes abilities image. [34:37] Okay. I think this has evolved. This has [34:40] changed. Maybe [34:43] the name space now is this one [34:48] with underscore. [34:54] Um, okay. This is [34:58] um [35:05] yeah, I think there are some [35:06] inconsistencies here because the spaces [35:11] in different but yeah um it confirms [35:15] what we suspected. It uses the this SDK. [35:29] Okay. So I would say that this um is the [35:38] um [35:46] I'm going to [35:51] we can copy this. [36:02] So here [36:08] this um [36:22] this refers to the [36:28] PHP AI client. [36:37] PHP AI client. [36:47] And this [36:54] refers to [36:58] the um [37:05] WordPress AI. [37:15] WordPress AI [37:18] which is the [37:22] WordPress AI [37:24] um experiments. [37:32] This is this is my understanding at [37:34] least. So [37:36] um [37:41] WordPress AI experiments [37:45] and then this is like the PHP AI client [37:50] SDK. I like this name. [37:56] I like this thing. [38:08] Um [38:12] well this is not exactly true. I think [38:15] what I think is the initially the idea [38:17] was to create two composer [38:23] packages [38:25] but this is actually a plug-in [38:29] right yeah AI PHP [38:36] so I think the second part has evolved [38:42] yeah plugin [38:44] The second part [38:48] has evolved as a plugin. [38:52] I'm going to add here um [38:56] this has evolved [39:00] as a plugin. [39:09] Um, [39:13] I'm going to put here [39:17] plugin [39:21] and [39:28] the background want to be here. This [39:34] and [39:39] This I want it to be here. This. [39:47] Okay. [39:49] So, this is a plugin [39:56] and this is a [39:59] composer [40:01] package. [40:15] Mhm. [40:25] composer package and [40:32] well this has evolved as a plug. [40:43] Okay, I'm clarifying this because it [40:46] says here that [40:49] um [40:58] because it said here that it consists on [41:01] two composer packages. I think I [41:05] initially that was the idea but um [41:09] this has evolved in different things. [41:15] Okay, [41:18] let's continue reading here. [41:25] This modular approach means when any [41:27] community adds a provider or improves [41:30] performance, everyone benefits while [41:32] each platform maintains its unique [41:34] experience. For WordPress developers, [41:37] this architecture offers flexibility. [41:40] Use the WordPress package for the full [41:44] experience with admin UI or the [41:47] underlying [41:49] PHP package for lower lower level [41:53] projects such as um WPCLI integration. [42:01] While also available as a plug-in for [42:03] testing, these composter packages are [42:05] the official adoption path. So does this [42:10] uh includes a composer package [42:14] composer.json. [42:23] Ah so this is also a WordPress package [42:25] and AI experiments and capabilities for [42:28] WordPress. [42:35] Okay. So maybe [42:37] I need to [42:41] see an example of [42:45] Okay. [42:48] So So yeah, maybe this is also um a [42:52] composer um [42:56] package. [43:02] So instead of um [43:07] went to [43:10] also available [43:16] as a plugin. [43:20] So what I'm going to do here is [43:31] compose a package. [43:34] I need to check this. [43:39] I need to check [43:45] if this can be used only as a composer [43:47] package. But yeah, we can use definitely [43:50] this as a plug-in the experiments that [43:52] internally it uh uses this um AI client [43:58] as a composer package. [44:04] Okay. So, let's uh let's try this. [44:08] Let's create some code. [44:13] I'm going to [44:19] I'm going to create a new project [44:23] under um [44:33] um projects [44:38] um 2026 [44:41] um [44:43] PHP [44:45] PHP AI [44:48] client demo [44:50] string. [44:52] What this uh doesn't exist. [44:56] So what I need to do [45:00] is um [45:06] take this will create this project and [45:10] will take me the PHP AI client SDK [45:16] no uh demo [45:19] stream. [45:21] Okay. [45:23] And now um let's open cursor [45:32] um and let's um [45:37] open the console. [45:43] And what we can do is maybe open clo so [45:47] it can generate [45:55] So it can generate. So we can maybe do [45:57] plot [46:01] and I can say [46:06] I can say [46:10] PHP AI client. Okay. [46:15] I can say scaffold a very basic [46:18] structure of a WordPress plug-in. I want [46:22] to [46:25] test this [46:27] composer package with some [46:31] basic code to connect to external models [46:37] from my WordPress instance. [47:09] Okay. So we have this here [47:17] um [47:19] okay it's with um [47:24] was another key [47:34] and this is what I said [47:38] scaffold [47:43] Okay. So, I just wanted to maybe create [47:46] a composer.json [47:48] and [47:51] um [47:57] Okay. What I want you to do [48:03] um [48:06] No. [48:12] Okay, I just want a basic plug-in [48:16] structure to check the referenced uh [48:21] composer package. [48:24] You have some WordPress develop [48:26] development [48:28] skills. So, please use them to scaffold [48:33] this basic plug-in structure. [48:38] because I have some um have some skills. [48:46] Let's open here in the meantime clo. [48:58] As you can see here, I have some skills [49:01] related to [49:11] But [49:15] it doesn't seem that. Yeah. [49:23] So the thing is that this um extension [49:26] of visual code or cursor doesn't really [49:30] has access doesn't really have access to [49:32] the skills. I let me check. Do you have [49:35] access to the skills? [49:50] It doesn't work as well as the terminal [49:54] thing. [49:58] So I may use this [50:05] or here instead. [50:11] But anyway, it it's creating the [50:16] it's creating the [50:19] PHP file for the plugin is creating [50:22] composer.json is within the admin which [50:25] I don't know exactly why. Let's see. [50:38] Okay. No, I don't like [50:44] um [50:49] Okay. Create a very basic plug-in [50:53] structure to test the [50:59] composer package that is in the [51:02] following repository. [51:06] I want the plug-in to be really really [51:08] basic. [51:12] Any settings or any value I will [51:17] define them via code. So please do not [51:20] implement any settings page or dashboard [51:23] or similar. Also, [51:28] please do not implement any life cycle [51:31] plug-in logic because this is just a [51:34] test and I want the plug-in to be really [51:36] basic. [51:46] And um [51:54] this is the [52:00] and this is the repository. Copy link [52:03] address. [52:19] Let's see what it does. [52:38] Um [52:45] Okay, [52:49] the thing is that I have defined to use [52:53] always the [52:55] context 7 MCP which [53:01] um [53:03] gets documentation directly. [53:08] Also do not forget that you have a [53:11] development [53:12] WordPress development skills. So please [53:15] use them [53:17] for this work. [53:43] Mhm. [54:03] Okay. So, it's um [54:05] it's checking the repository. [54:12] I told it I want to check. So, it's [54:16] creating a [54:32] Um, [54:34] okay. Nice. So, [54:38] besides [54:42] creating the [54:48] Okay, nice. Nice. I think [54:52] it was worth the the wait. [55:07] Okay. So here we are using the the name [55:10] space [55:12] in order to do that is loading the [55:14] autoload. [55:17] Yeah, this is more or less what I [55:19] wanted. Um, [55:27] we need to uh simply test functions [55:30] generate text using AI [55:39] error lock [55:41] return text. Okay. So we have these [55:45] functions. [55:54] So test AI text generation [55:59] is uh doing this [56:02] and it's returning the text [56:07] but uh this function need to be called [56:12] uh from somewhere. So maybe [56:16] I can just do from init. This can be [56:20] instead of calling directly this, this [56:22] can be a function [56:25] h where I call this and I um [56:32] I lock this [56:36] maybe that can be that can be a thing. [56:40] Um, [56:44] also [56:46] what I'm going to do [56:51] is to [56:56] um [56:58] Okay. [57:00] Yes. [57:08] Okay. I also prepare the plug-in. So [57:11] credentials can be [57:14] defined from a separate file inside the [57:18] project. [57:34] Okay, it's solving some issues [57:37] because the version is PHP AI client. [57:43] Let's see. [57:47] It's 040 3 days ago. [58:07] Okay, it's running composer install. [58:12] Uh, which means is creating the vendor [58:15] and inside the vendor [58:18] composer. [58:21] Okay, seems like a [58:25] seems like a minimal uh setup which is [58:28] what we were looking for. And then the [58:32] PHPA AI client will internally have some [58:37] other dependencies such as PHP HTTP I [58:41] guess and some others. [58:46] Um [58:56] okay so now [58:58] it's checking from the repository how [59:00] the credential system works. [59:06] Um [59:09] in our case in vendor [59:15] I know this is the vendor inside. [59:25] So the credentials [59:28] um [59:35] I need credentials in order to run this. [59:38] And in the meantime, what I can do is [59:40] I'm going to open studio. [59:45] I'm going to open studio. [59:52] Maybe I can leverage I can use the same [59:58] repository [60:00] or 2026 experiments. [60:05] Okay, let's use this. And in order to do [60:08] this, I'm going to click it term because [60:12] in WP content uh plugins [60:21] I'm going to remove. [60:29] And what I'm going to do is I'm going to [60:31] link I'm going to create a sim link to [60:35] the uh let me make this [60:39] bigger. [60:40] Okay. I'm going to ln [60:43] uh [60:46] project [60:49] um [60:52] cheese. [61:00] Perfect. [61:02] So if we [61:05] run this, [61:10] we should get this plug-in installed. [61:24] Okay, [61:27] define. Perfect. This is what I wanted [61:30] because I want this to be [61:33] credentials [61:41] because I want to do this in another uh [61:45] window in a different place. [61:49] Oh, bear with me. [62:00] I need to [62:09] I need to [62:12] move this to another folder. [62:15] And from here [62:22] I'm going to use [62:27] open AI [62:33] credentials and [62:52] I need to access my [62:59] open AI. [63:18] Okay, it's this one. Then if I edit this [63:23] open AI key. [63:32] Perfect. [63:48] Okay. [63:50] So now we should have the credentials [63:55] and [64:00] what I'm going to do is um [64:06] I'm going to close this because I want [64:09] to open this in cursor which is the [64:12] whole um [64:16] WordPress installation that includes [64:20] I'm going to be working on this [64:23] on this file. [64:27] Why do I want this? Because I want the [64:30] the backlog [64:35] to display the log. So if I reload [64:49] um [64:53] in WordPress settings online 560 Next [64:57] thing [65:23] include once plugin [65:27] Okay, I think I need to go to plugins. [65:41] Okay, [65:44] so I shouldn't get this error message. [65:59] Well, okay. It seems that um [66:04] it shouldn't happen because if I remove [66:06] the folder, I think that I should get [66:11] I should get um the plugin should be [66:13] removed. [66:15] Um, [66:20] so what I'm going to do is I'm going to [66:24] stop the side. [66:28] Going to remove this. [66:31] Then I'm going to [66:33] start again [66:35] the side. [66:39] And I'm going to [66:42] um [66:47] to log again. I need to get the password [66:50] from here. So, it's [67:02] so I'm logging in. [67:10] Okay. [67:19] I guess that's the first time. But now [67:21] if I reload, I don't get this. Okay. And [67:24] now that the backlog is uh clean again. [67:27] So now we have [67:31] the [67:35] plugin installed. [67:38] We have the credentials in place. [67:42] And [67:47] what we want is um [67:54] okay so we have [67:56] different functions [67:59] simple test function to generate text [68:02] using AI. [68:05] Okay, let me try one thing. I'm going to [68:07] try [68:13] I'm going to try [68:22] I'm going to try accessing the [68:28] let me if I go to GitHub and if I go to [68:34] my guests I have here. [68:38] Um [68:45] I have here uh [68:54] yeah this one. Okay. WP shell is the [68:58] command I was looking for. So if I do [69:02] not from here but from [69:06] DolbyP [69:07] like uh 2026 experiments. If I open a [69:12] terminal [69:15] and I do WP shell, [69:22] I get a terminal. [69:25] um [69:29] where my WordPress instance is loaded, [69:31] which means that [69:34] I should be able to access this. [69:42] For example, in my example, I was doing [69:46] this. So [69:52] test AI text generation [69:56] in my code [69:59] doesn't require any parameters. [70:05] Let's see. [70:25] Because [70:28] I think I forgot one thing. [70:32] I forgot to activate this. [70:37] Okay, let's start again. [70:48] No models found that support text [70:50] generation for this prompt. So the [70:53] function is working properly. [70:56] But uh something is going on here. Let's [71:01] try the other functions just to see. [71:08] Uh this is the one [71:13] no models found for provider. So yeah. [71:17] Um okay [71:25] found [71:30] with parameters. [71:33] Okay. Okay. [71:36] Well, but at least the testing setup is [71:38] is there. Now, we need to fine-tune this [71:43] function. So, um Okay. So, what I'm [71:47] going to do is [71:49] I'm going to remove all of them. And now [71:53] we can check the documentation. [71:56] Now, we can come here [72:00] and we can test um [72:06] called examples text generation using [72:08] any compatible model from a specific [72:11] provider. [72:14] So this is the [72:32] using provider open AI. [72:36] Um [72:46] So yeah, I actually like this structor. [72:50] I like it. [72:52] Yeah. Text. [72:55] This is the [72:59] And if not, I'm [73:03] getting here the um [73:07] the locks. [73:17] So let's start again. [73:20] Um [73:23] Dolby VP [73:25] shell [73:31] test AI text generation. [73:36] Test AI tech generation. [73:42] No models found for provider open AI. [73:53] Okay. Text generation using any [73:54] compatible model from a specific [74:01] provider. [74:04] But in theory, [74:07] generate text [74:10] should um [74:14] this should work with any compatible. So [74:18] in theory, [74:21] I shouldn't need to do this. [74:30] Um [74:38] So [74:47] what I'm going to do is I'm going to [74:51] ask the deep wiki thing which is here. [74:57] Um, [75:02] yeah, this PHP AI client. So, I'm going [75:06] to [75:07] open a new [75:12] Let's see what can it tell me about this [75:16] error. [75:24] Okay, I'm going to also [75:28] provide the function [75:33] and this is my code. [75:44] So it said [76:01] Uh, so I need to do [76:04] more things. [76:16] Um, Requirements [76:19] for success. For automatic discovery to [76:22] work, you need at least one provider [76:24] properly configured. [76:26] Happy keys. Set environment variables. [76:36] So we need to check first [76:42] if this is configured. So [76:49] um error rock is conf. Okay. [76:54] Open AI [76:58] and the backlog [77:03] is empty. [77:21] Okay. Because [77:26] No, it should fail. [77:33] Let's um [77:38] test this again. [77:52] Okay. So maybe [78:05] the credentials. No, the credentials are [78:08] uh properly [78:12] properly introduced [78:15] because his credentials, right? [78:20] Credentials. [78:22] um file exist. [78:24] Um what I can do. [78:41] What I can do is um [78:54] Okay. [78:56] Okay. We're fine. [79:11] Okay. [79:12] So [79:15] if I go to [79:21] shell. [79:26] So the file is being properly [79:31] loaded because this is something I just [79:33] added [79:35] and [79:44] And let me see if the way the [79:47] credentials are defined is correct. So [79:50] if we go to [79:52] PHP AI client and [79:58] let's look for [80:01] open [80:03] open [80:05] AI [80:09] happy [80:11] Okay. [80:26] Mhm. [80:36] Open AI. Okay. So [80:41] maybe this is not the way to define the [80:43] credentials. [80:45] Um [80:50] okay, let's look for [80:55] healing docs. [80:58] Um architecture requirements [81:01] requirements [81:14] Um, let's look for [81:19] credentials. [81:34] Um, [81:39] Okay. [81:41] All our credentials [81:43] provided to [81:47] the different providers. [81:53] So what I have done is I have defined [81:56] this [81:58] constant called open AAI API [82:04] key. [82:07] But um [82:47] Is it enough if I just do this [82:53] before calling the [82:59] PHP AI client SDK classes and methods. [83:14] Okay, let's see. [83:30] So be my AP key, my my real API key. [83:44] Mhm. [83:50] Um, [83:54] so the API key is defined. [84:05] If [84:18] Okay, let's try again. This [84:29] open AI is not configured. So that's the [84:32] issue. [84:34] That's the issue. Um, [84:51] the boss [85:12] Okay, [85:16] I have the open AI API_key [85:22] constant defined before calling the [85:27] methods like this. [85:44] But the following [85:48] cold returns false. [86:02] So [86:04] yeah something is going on. We have [86:07] defined the constant. So in theory it [86:10] should be [86:13] it should be well actually you know what [86:16] we can check how it's done here [86:34] okay so [86:38] so Maybe the API. Yeah, maybe the API [86:41] key is not [86:47] um maybe my API key [86:53] is not um [86:59] maybe my API key is not um [87:05] okay, let's try another one. [87:10] this one. Um, [87:32] okay, let's try another one. [87:38] because I think it [87:41] I think it runs a specific API [87:47] call. So I was I was expecting that um [87:52] I could get an error message saying that [87:56] your credentials are not correct. So [87:59] I know that the [88:03] the flow is working properly like the [88:05] proper calls, the proper functions are [88:08] being called. But no, it seems that my [88:10] API key um because I have uh [88:19] have several versions of the API key. So [88:21] maybe it's not the the latest one. [88:25] So let's try another one. Let's try [88:27] another one. [88:30] What I'm going to do is I'm going to [88:33] define [88:39] I'm going to define [89:09] I'm going to define [89:11] um [89:17] let's check now if the anthropic is [89:20] properly configured. [89:27] Okay, let's start again. Let's go with [89:31] uh [89:33] WP shell [89:39] traffic is not configured. [89:42] No models found that support text [89:45] generation for this prompt. [89:49] Let's check. [89:59] So I have uh don't they have [90:05] the model? Okay. [90:23] I'm going to test the [90:38] So I'm getting this errors all the time. [90:41] I have tried two API keys and [90:47] I think that they are fine. So I don't [90:50] think it's an issue with the wrong API [90:52] key. Can you double check with the [90:56] following repository how credentials [91:00] should be [91:02] defined in order to use these [91:08] methods of the PHP AI client SDK? [92:20] Um, [92:39] Okay, let me access the prompt that I [92:41] want to pass. [92:45] I want to pass to [92:48] code. [92:53] Sorry. [93:05] And in the meantime, we can check the [93:14] we can check the AI. [93:22] this one. And what we can also do is we [93:28] can come here and say uh deep [93:34] wiki for this. [93:40] How are credentials [93:43] managed in this project? [93:46] I want a clear reference of how to [93:50] provide credentials [93:53] to use PHP [93:56] AI [93:58] client SDK [94:01] functions. [94:34] Okay. So, it's managed internally. [94:39] Credentials are are stored internally [94:45] uh as valid AI credentials. Check if any [94:51] prompt [94:53] test is supported for text generation. [95:11] Okay. So, yeah. I don't know. Maybe the [95:14] credentials I'm using are not fine. [95:29] Um, [95:36] Baby. [96:45] Okay. Um [97:38] Okay. So the credentials [97:42] are correct. [97:49] I have just tested them with an API [97:52] call. [98:14] Um, [98:32] so lot credential ial the credentials [98:34] are required are defined. So yeah at [98:38] this point the API key should be defined [98:41] and should be available. [98:45] I'm not sure what's going on here. [99:19] Um, [100:26] Um, [101:20] Okay, so I need to [101:24] Let me try something. [101:51] I'm going to try. [101:59] So, do I need to initialize this? [102:03] Um, [102:11] do I need to initialize [102:16] AI client in it. [102:26] I'm not sure. [102:30] But let's try this again. [103:20] Uh, [103:24] so [103:27] in theory with this [103:31] I get [103:42] Um, [103:45] I can go here to [103:53] And now I have an error. [104:15] Mhm. [104:43] Okay, I'm getting an error because [104:49] I'm getting this. [104:51] And if I go to the book lock, [105:04] okay, I think it was because let me [105:11] remove the logs. [105:14] Then I'm going to check the code. [105:26] Do I have to? [105:33] No, I only have to. What in it? [105:37] Function AI [105:40] client in it. That's fine because I'm [105:43] doing this [105:47] um [105:56] Um, [106:02] okay. For now, I'm going to [106:05] comment this. Let's see what happens. [106:39] Okay, with this if I go to plugins [107:14] If I go to tools uh to [107:20] plugins [107:34] okay so we have the composer require [107:38] WordPress AI client. [107:45] This loads properly. Class exist. So I'm [107:48] going to add here error lock AI client [107:52] initialized. [107:58] Let me see [108:03] if I go to the backlog. [108:07] A class WordPress AI client. AI client [108:11] not found [108:45] Um, [108:46] if I go here, [108:53] this a thing. [109:08] AI client in it. [109:19] Okay, let's ask a little bit more. [109:30] Is there an init method that I can use [109:34] to initialize the WordPress AI client [109:39] that enables um [109:44] a specific dashboard to enter the AI [109:48] client credentials. [109:59] Mhm. [110:17] Okay. So that's true. [110:20] Um, [110:23] this is documented here. AI credentials [110:26] dashboard. [110:30] Not really documented here, [110:34] but it's interesting to know. [110:39] So this is correct. And now [110:48] The only thing I need to [111:20] Okay. [111:24] You need [111:26] else. [111:37] Let's reload. [111:42] AI client not initialized [111:45] because [112:11] Um, I client [112:36] not initialized. [112:44] Um [113:02] Um, what's uh wrong here? [113:09] And with this, I think we can call it a [113:13] day. [113:29] Let's see if we can finish the stream [113:31] with uh this uh [113:35] function working. [113:41] It shouldn't be [113:45] so difficult. [114:15] Okay. I think I'm going to leave it [114:18] here, [114:21] but um [114:23] next week [114:26] I will do a second part of this because [114:29] I want to really I want to really uh [114:33] move forward with this and [114:35] being able of um [114:43] calling this uh function successfully. [114:45] Okay. So, yeah, not a very successful [114:50] stream, but we have explored a few [114:52] things. We have learned a new things, [114:55] which is always good. And yeah, hope you [114:58] have you have enjoyed [115:01] watching me struggling while I try to [115:04] figure out how to talk things. So, yeah, [115:09] have a great weekend and see you next [115:13] week. uh same day, same time on Fridays [115:18] at around um [115:22] 5 uh [115:25] p.m. [115:27] set. Anyway, I I share the the specific [115:30] time with the time zone outline. So, [115:33] yeah, see you next week. Have a great [115:36] weekend.