Title: AI as a WordPress Fundamental Author: Jason Adams Published: December 4, 2025 Last modified: December 9, 2025 --- [ ](https://profiles.wordpress.org/jason_the_adams/) [Jason Adams](https://profiles.wordpress.org/jason_the_adams/) 7:37 pm _on_ December 4, 2025 Tags: [#core-ai ( 3 )](https://make.wordpress.org/core/tag/core-ai/) # AI as a WordPress Fundamental ## **WordPress Fundamentals** Imagine WordPress without a database. Not changing the kind of database. No database at all. WordPress without the ability to persist data. One could use the filesystem. But how would things like 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. work? Some particularly clever minds might take this as a challenge and think of something, but WordPress would be fundamentally different. The funny thing about this mental experiment is that your average WordPress user doesn’t know what a database is, much less the fundamental role it plays within WordPress. It’s taken for granted. Of course posts save, comments can be made, and settings are stored. Why wouldn’t they? Even for 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. developers the presence of the database is assumed. No one checks if the database exists before using get_post_meta() or grabbing $wpdb. Entire products are built around the assumption that the database is present. Simpler products store things in meta while more complex products add custom tables. From simple to complex, products utilize the database to unlock incredible possibilities. It’s safe to say the vast majority of the impressive plugin ecosystem relies on the database. ## **AI as a Fundamental** What if this were true of AI? What if, from the end-user to the plugin developer, they could take for granted that there’s an AI model accessible to me by virtue of being in WordPress? What kinds of things would people use it for? What amazing things would people create that are built on the reliable presence of a capable LLM? It’s tempting to think of AI as a feature. Users look at products like ChatGPT or Claude Code and imagine a chat interface. So it may be tempting to imagine WordPress with a chat interface to a powerful LLM that does all sorts of cool things with and for the user. But the idea is not merely that; it is more than that. Even with the database, there are certain features like saving a post that feel closely tied to the database. But when someone likes a post, they’re not thinking“ I’m saving this like”. They just did something and it’s still there. Why wouldn’t it be? With LLMs the chat interface feels close to the model because it’s a direct interaction. But what about features like clicking a “generate alt text” button for an image that just fills in the alt text? In this case, it’s creating an AI- powered feature without it being obvious. And so it should be! When one imagines AI as an engine, humming within WordPress that can be _used for anything_, then things get even more exciting. ## **AI Features at WordPress Scale** The most incredible thing about WordPress _is_ its ecosystem. Every single day there are people creating and improving plugins that push the capabilitiescapability A** capability** is permission to perform one or more types of task. Checking if a user has a capability is performed by the `current_user_can` function. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts (the “edit_posts” capability), but not permission to edit other users’ posts (the “edit_others_posts” capability). of WordPress further and further. Each day WordPress grows to be even better. Imagine if every single developer was empowered with AI capabilities without having to handle the complexities of AI integration. What if the developer just did something like ```notranslate $$image = Ai_Client::prompt( 'Create an image that beautifully reflects this post content' ) ->with_text($post_content) ->generate_image(); ``` Simple as that. Nothing more required to interact with the AI. One could build everything from simple interactive tools to powerful agents. If AI is fundamental to WordPress, and it’s unleashed on the ecosystem, then there’s simply no competitor that can keep up. (As a note, this code isn’t just an idea, this is real! It’s the [WP AI Client](https://github.com/wordpress/wp-ai-client) and is proposed for WordPress 7.0!) To be abundantly clear, this is the bedrock of this vision: In order for AI to truly be a cornerstone of WordPress’ next wave of success, AI has to be a win for the entire ecosystem. To press it further, WordPress is what it is today _because_ of its ecosystem, therefore adoption by the ecosystem is not a nice to have, it’s the most necessary goal. No competitor can possibly keep up with the scale and speed of innovation in the WordPress ecosystem. That is our advantage, and AI can unlock the next stage of innovation. ## **An ushering strategy** The real challenge, therefore, is how to empower everyone with this capabilitycapability A **capability** is permission to perform one or more types of task. Checking if a user has a capability is performed by the `current_user_can` function. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts (the “edit_posts” capability), but not permission to edit other users’ posts (the “edit_others_posts” capability).. At this moment, the most feasible method for integrating with LLMs is through cloud providers such as OpenAI, Google, and Anthropic, or through self-hosted means which is not for the faint of heart. So if a plugin adds a bunch of AI features then they need to either provide the service themselves (e.g. Elementor’s Angie) or send the user off to generate an OpenAI (or whatever) key, come back, and paste it in. In either case there’s additional complexity and cost, the kinds of which drive away the majority of users. Again, imagine if it was also _Bring Your Own Database_? What if hosts brought the AI like they do databases? If databases were optional in WordPress, then hosts including a database as part of their managed hosting would be a huge competitive advantage. The capabilities and experience of the WordPress site would be substantial. If plugins included AI- powered features, then this same reasoning would flow into hosts that provide the AI model as part of the hosting plan. WordPress would work without AI (an important note), but to a noticeably lesser degree in terms of user value. Hosts even have the choice to determine how they want to solve that problem (proprietary model, proxy, etc.) to play with their own cost-to-value proposition and be competitive. With this in place, plugin developers would be able to assume that a capable model exists which they can use to power their features. This eliminates the common and substantial pain point for each developer to figure out how to bring a model or get the user to bring their own. Not only does that reduce friction for the user, but it greatly lowers the necessary competency for the developer. Armed with the ability to simply run prompts any time and anywhere, the developer doesn’t need to know more than how to do that and can get back to innovating. ### **Backwards Compatibility** This is WordPress, so it’s important to acknowledge the need for backwards compatibility. There’s a strategy that’s already in place for this. Within the WP AI Client, it has a [system for finding the best model for a given prompt](https://make.wordpress.org/ai/2025/12/04/ai-for-wordpress-developers/)— based on the needs of the prompt. It’s quite sophisticated! It also has methods that can be used to check if there is a model available to do the work. This is really important, because it allows the developer to check for the AI before making the assumption. Imagine a “Generate Alt text” button, for example. The developer can use the check methods to conditionally display the button — present if there’s a supporting model, and hidden if not. This keeps the plugin working in a backwards compatible way. As time goes on, ideally the need for these sorts of checks will be reduced, ultimately getting to the point now where databases are truly assumed to be present. ## Where the vision meets us This journey has already begun with the formation of the AI Team in WordPress and the [AI Building Block for WordPress](https://make.wordpress.org/ai/2025/07/17/ai-building-blocks/) was created. For this to succeed, innovation and effort are needed from two communities within the WordPress community: ### Developers Adoption and innovation of the Abilities 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. (coming in WP 6.9), [WP AI Client](https://github.com/wordpress/wp-ai-client)( proposed for WP 7.0), and [MCP Adapter](https://github.com/wordpress/mcp-adapter) from developers is critical. Even if you’re not sure about what AI features to make, just using Abilities will make other AI integrations even more capable. Otherwise, thinking outside the chat bot (though that’s great, too) and imagining what you could do by passing text, images, audios and so forth to AI, and getting back text, images, audios, videos, and embeddings. The upcoming [Workflows API](https://github.com/WordPress/gutenberg/issues/70710) will then make it possible to chain together Abilities into truly powerful flows. Imagine publishing a post which triggers a workflow to use AI to summarize its content, send an AI generated email to an audience, and then note its completion in a SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) post. Really, just do what you do already and make amazing things! To learn more about how this connects to developers and what they can do, read [AI for WordPress Developers](https://make.wordpress.org/ai/2025/12/04/ai-for-wordpress-developers/). ### Hosts As already mentioned, hosts are critical in the distribution of AI models to the ecosystem. By introducing AI in hosting plans, WordPress becomes even more capable simply by including a model, giving a competitive advantage. Hosts can also use this AI within WordPress for doing things like interacting with the customer’s account via MCP. Also think about developers and how to empower them to develop within your environment, possibly offering some access for developers to test their plugin on your platform to make sure it works as intended. To learn more about how this connects to hosts and what they can do, read [AI for WordPress Hosts](https://make.wordpress.org/ai/2025/12/04/ai-for-wordpress-hosts/). ## Conclusion There will be separate posts written specifically for developers and hosts to provide more specific information on what they’ll need to understand to get started. You’re encouraged to jump into the Making WordPress Slack and reach out in the [#core-ai](https://make.wordpress.org/core/tag/core-ai/) channel with any questions or needs that arise. AI is an industry shift, quickly becoming a cornerstone of the next generation of technology. For WordPress to grow into the next phase it’s critical that AI become a fundamental part of WordPress itself, and for this to succeed everyone has a role to fulfill. _Props to [@annezazu](https://profiles.wordpress.org/annezazu/), [@jeffpaul](https://profiles.wordpress.org/jeffpaul/) for the pre-publish review_ ### Share this: * [ Threads ](https://make.wordpress.org/core/2025/12/04/ai-as-a-wordpress-fundamental/?share=threads) * [ Mastodon ](https://make.wordpress.org/core/2025/12/04/ai-as-a-wordpress-fundamental/?share=mastodon) * [ Bluesky ](https://make.wordpress.org/core/2025/12/04/ai-as-a-wordpress-fundamental/?share=bluesky) * [ X ](https://make.wordpress.org/core/2025/12/04/ai-as-a-wordpress-fundamental/?share=x) * [ Facebook ](https://make.wordpress.org/core/2025/12/04/ai-as-a-wordpress-fundamental/?share=facebook) * [ LinkedIn ](https://make.wordpress.org/core/2025/12/04/ai-as-a-wordpress-fundamental/?share=linkedin) 1. ![](https://secure.gravatar.com/avatar/c6992b336d142228011bd36c3e3a3bbe7da868af9dcf2aff4a648ec2cc0b46d1? s=32&d=mm&r=g) 2. [Jason Adams](https://profiles.wordpress.org/jason_the_adams/) 7:47 pm _on_ December 4, 2025 3. +make.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. [https://wordpress.org/](https://wordpress.org/)/ai/ 4. ![](https://secure.gravatar.com/avatar/86a40c321ab5bdc2d91ea37a21d6fcee577bdc9f25b5ccfb032b18c1c237bd83? s=32&d=mm&r=g) 5. [David E. Smith](https://profiles.wordpress.org/desmith/) 8:21 pm _on_ December 4, 2025 6. Will there be appropriate filters to disable this, and to prevent accidental use of any such features? I know I sound like the living embodiment of the Old Man Yells At Cloud meme, but I have serious ethical and legal concerns about generative AI. As a site owner I want to be sure I’m not enabling the proliferation of AI slop. (Yes, site users can still create and upload it manually but I don’t need to make it easier for them.) To expand on the pseudocode in the above, I’d like any instances of `new AiClient` to return an error. 7. * ![](https://secure.gravatar.com/avatar/c6992b336d142228011bd36c3e3a3bbe7da868af9dcf2aff4a648ec2cc0b46d1? s=32&d=mm&r=g) * [Jason Adams](https://profiles.wordpress.org/jason_the_adams/) 9:53 pm _on_ December 4, 2025 * As this is considered for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., avenues for restricting AI can certainly be explored. The simplest way to go about this is removing all registered providers in the WP AI Client. That way developers creating AI-powered features can check and see that there’s no supporting model, gracefully omitting the feature entirely. - ![](https://secure.gravatar.com/avatar/33212bff2915bd72792772a2d3203abe0402352b6be6ba65081036f10560c6e6? s=32&d=mm&r=g) - [David Levine](https://profiles.wordpress.org/justlevine/) 11:56 pm _on_ December 4, 2025 - Hosts could make deregistering providers problematic. When the time comes I recommend we implement a capabilitycapability A **capability** is permission to perform one or more types of task. Checking if a user has a capability is performed by the `current_user_can` function. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts (the “edit_posts” capability), but not permission to edit other users’ posts (the “edit_others_posts” capability). that can be revoked as needed * ![](https://secure.gravatar.com/avatar/c6992b336d142228011bd36c3e3a3bbe7da868af9dcf2aff4a648ec2cc0b46d1? s=32&d=mm&r=g) * [Jason Adams](https://profiles.wordpress.org/jason_the_adams/) 6:47 pm _on_ December 5, 2025 * We’ve explored this a bit. I think this is another great direction to go! 8. ![](https://secure.gravatar.com/avatar/6f505c6be9a951929a99becb6b413dcfa583a5ca3dd0f7320766fee1481f0f82? s=32&d=mm&r=g) 9. [Jb Audras](https://profiles.wordpress.org/audrasjb/) 8:29 pm _on_ December 4, 2025 10. I think this AI thingy is going to be a massive disaster for our ecosystem and our economy. Plus, this is more and more looking like a dotcom bubble-like, which is going to explode due to the same old factors than the previous bubble (too many investments, unrelated to the real benefit of this technology). 11. By the way, your alt text example is the worst possible example of good use of AI technology for a better accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “ direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). ( https://en.wikipedia.org/wiki/Accessibility). 12. * ![](https://secure.gravatar.com/avatar/6f505c6be9a951929a99becb6b413dcfa583a5ca3dd0f7320766fee1481f0f82? s=32&d=mm&r=g) * [Jb Audras](https://profiles.wordpress.org/audrasjb/) 8:50 pm _on_ December 4, 2025 * My comment was quite rude, sorry. But this tech thing is not sustainable for now and we know that we cannot sustain it in a world with limited resources. I’m unsure that doing massive investment in this tech is the right thing to do. Low-tech is probably a better bet than IA in a long term point of view. - ![](https://secure.gravatar.com/avatar/c6992b336d142228011bd36c3e3a3bbe7da868af9dcf2aff4a648ec2cc0b46d1? s=32&d=mm&r=g) - [Jason Adams](https://profiles.wordpress.org/jason_the_adams/) 10:11 pm _on_ December 4, 2025 - I appreciate your passionate perspective, no worries. 🙂 - Personally, I do believe folks will continue to find the practical limits of AI. It’s not great at everything, and it is great at some things. So long as we press into where these things do well, and don’t assume they do everything well, we can come up with some great new features that would’ve been historically quite difficult to make. - Kindly, I also want to acknowledge your point regarding generating alt text. Now, I do believe AI is capable of analyzing an image and producing good alt text. That said, I think a good UXUX User experience is to provide it as a starting point rather than blindly trusting the AI. A simple “generate alt text” button that pre-fills the input could be useful. For some users, they may not even know what to put there, so having the AI suggest something is helpful. At that point we get human validation, wherein the user may choose to save it as-is, or change it. - I think AI works best when it empowers human decision, not when it tries to replace it. * ![](https://secure.gravatar.com/avatar/4fd344e387cd0febbb417ee2a2bef7db6b40c8f7ecf4265fb41dcef8e9fa8c4b? s=32&d=mm&r=g) * [Joe Dolson](https://profiles.wordpress.org/joedolson/) 11:02 pm _on_ December 4, 2025 * I was also coming here to suggest that the specific example given is a terrible example of AI usage. What AI is very capable of producing is an image description, and that is in no way the same thing as alternative text, and we need to be more cautious about avoiding conflating those two functions. - ![](https://secure.gravatar.com/avatar/c6992b336d142228011bd36c3e3a3bbe7da868af9dcf2aff4a648ec2cc0b46d1? s=32&d=mm&r=g) - [Jason Adams](https://profiles.wordpress.org/jason_the_adams/) 11:41 pm _on_ December 4, 2025 - I’ve gone ahead and changed the example, as I don’t want it to become a distraction. The point of the example is to reflect the simplicity of making prompts and generating text and such. The alt text example was in place to show the multi-modal capabilitiescapability A **capability** is permission to perform one or more types of task. Checking if a user has a capability is performed by the `current_user_can` function. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts (the “ edit_posts” capability), but not permission to edit other users’ posts (the “edit_others_posts” capability). (image in and text out), and the new example reverses this. - If and how AI can be effectively used to generate alt text is a good question and worth exploring, but not the intent of this post. - Thank you for all the feedback. I hope the new example proves useful and less distracting! 😊 - ![](https://secure.gravatar.com/avatar/33212bff2915bd72792772a2d3203abe0402352b6be6ba65081036f10560c6e6? s=32&d=mm&r=g) - [David Levine](https://profiles.wordpress.org/justlevine/) 11:49 pm _on_ December 4, 2025 - [@audrasjb](https://profiles.wordpress.org/audrasjb/) I share your broader concerns. - For example, I’m curious about the prioritization of Workflows – an entirely new vertical – before we discuss proven use cases like semantic search ( which could even be vectorized for free using browser models and not privilege- locked behind tokens)? - Or less theoretical: I’m concerned by how much we’re investing into MCP, but even more so how much we’re pushing it ([@jason_the_adams](https://profiles.wordpress.org/jason_the_adams/) even this post calls it “critical”), when we know both our implementation and the technology itself face significant issues in their current form. And now into plugins like WooCommerce that we allowed to bundle 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. prematurely as a Composer package… - I believe this post was meant to be aspirational, but if we want to craft an effective narrative, I think we’re first overdue a public discussion about what “AI at WordPress Scale” looks like, what non-hype use cases we can already meet by giving our vision a bit of scope, and how we decide how individual AI Experiments or canonical plugins are prioritized. * ![](https://secure.gravatar.com/avatar/33212bff2915bd72792772a2d3203abe0402352b6be6ba65081036f10560c6e6? s=32&d=mm&r=g) * [David Levine](https://profiles.wordpress.org/justlevine/) 1:37 am _on_ December 5, 2025 * Just to clarify, I’m a very happy volunteer contributor _on_ the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. AI team and very supportive of everything [@jason_the_adams](https://profiles.wordpress.org/jason_the_adams/) and the team are doing. I also agree with the sentiment of this post, even if I think some of the specifics would benefit from discussion/ evaluation by the team and beyond before they become prescriptive. * I _also_ think that we’d have more success building a narrative, reaching consensus, and shipping adoptable features if we had a clearer mechanism for shaping the roadmap and making informed decisions about what’s worth exploring, let alone recommending, vs hype. * Or to quote Jason 😉 * > To be abundantly clear, this is the bedrock of this vision: In order > for AI to truly be a cornerstone of WordPress’ next wave of success, > AI has to be a win for the entire ecosystem. To press it further, > WordPress is what it is today because of its ecosystem, therefore > adoption by the ecosystem is not a nice to have, it’s the most necessary > goal. * ![](https://secure.gravatar.com/avatar/5bccf439e28a96b79ced740b6c17811af9340bef54767c639c601953de5b1551? s=32&d=mm&r=g) * [SirLouen](https://profiles.wordpress.org/sirlouen/) 1:05 am _on_ December 5, 2025 * [@audrasjb](https://profiles.wordpress.org/audrasjb/) people have been building wrappers and prompts and selling businesses based on this, so it looks like this may happen at some point * But on the other side, the .com was back in the day a big thing (apart from those guys creating empty businesses based on a .com), and similarly happens to AI now. Imagine you bought `cars.com` back in the day; you would probably be writing this from a boat in the Caribbean sea 😉 * For example, WebGPU has been surging in 2025 like crazy, and I hope that is completely supported in 2026. SLMs will be a thing sooner rather than later, and we will most likely see them running even in smartphones. Like we have plenty of compatibility layers for super bleeding-edge features (like the experimental “view transitions” and “client-side media processing”), we will forcefully need to add support for all these potential side-AI features that will bring the web experience to a whole new level. * So all these new advancements feel like little steps into this new tech. But I agree with you that we should not be too reckless and not deliver too much fake hype (although, to some degree, this is part of any marketing campaign, so I’m pretty confident that Mr. M is entirely happy that this is happening). 13. ![](https://secure.gravatar.com/avatar/4b04f3868d5d00557a0e117f43262a23de2b023b16cf33e18bf233ecce7e4515? s=32&d=mm&r=g) 14. [Hudson Atwell](https://profiles.wordpress.org/hudson-atwell/) 8:44 pm _on_ December 4, 2025 15. **On UXUX User experience:** 16. As a user the more execution I can achieve with plain language prompts, the better the experience. 17. As a developer, having ways to program these AI-assisted tasks, in an LLM-assisted worktree, makes sense, and it appears that’s where we are headed. I am a fan. 18. Beyond AI reliability, there is also the concern that users need to be able to articulate their needs accurately. 19. Perhaps there should be a stage in the AI execution flow where the LLM offers confirmation of what the user is asking (possibly even several variations in case the LLM detects different interpretations), and then allows the user to select a confirmation and preview the worktree before executing. 20. Then there is the issue of dissatisfaction. What happens if a user does not like the effect of their action? Will worktrees be reversible? 21. As we delegate more to interpretation (LLM, User, etc), guardrails may matter just as much as capabilitycapability A **capability** is permission to perform one or more types of task. Checking if a user has a capability is performed by the `current_user_can` function. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts (the “edit_posts” capability), but not permission to edit other users’ posts (the “edit_others_posts” capability).. 22. **On Hosting:** 23. With all things AI/LLM, the long-term ideal is self-hosted LLMs operating at the local or server level, rather than relying entirely on third-party cloud- driven solutions. 24. I think people are willing to spend 3 to 7k USD for the hardware to claim full ownership. Hosts possibly can and should cut into the cloud market as soon as possible by buying and clustering this hardware for their customers. 25. The least desirable outcome (and most likely guaranteed outcome in the short term) for WordPress and the consumer is a dependence on cloud-provided models. 26. The second-best outcome is host-owned yet just as reliable LLMs. If the host is buying discount credits from the big-three, then I don’t think this really counts as a better outcome. 27. The ideal outcome is that technology and hardware enable self-hosted, self-supplied models to integrate seamlessly into the WP experience. This eliminates the need for the “shared” service, secures data, and protects against uncertainties. 28. Anyhoo, am a fan of the progress. Good work so far, love to see it. I will look to implement it into my own plugins when/if applicable. 29. * ![](https://secure.gravatar.com/avatar/c6992b336d142228011bd36c3e3a3bbe7da868af9dcf2aff4a648ec2cc0b46d1? s=32&d=mm&r=g) * [Jason Adams](https://profiles.wordpress.org/jason_the_adams/) 9:33 pm _on_ December 4, 2025 * Thanks for sharing your thoughts, as well as your support! I’ll respond in two parts: * **On UXUX User experience:** * It’s important to note here that the UX is determined by the implementing developer. The WP AI Client doesn’t provide a chat UIUI User interface, just a means of communicating uniformly with different model providers. All of your UX feedback is good and should be taken into consideration by the developers imagining and building the UIs that are AI-powered. * For example, if a button is provided to generate a post title based on the content, then you could perhaps give the user multiple titles to choose from. Then, when they select one, the title is changed but the post not saved. So if the user changes their mind they can still change it or discard the changes entirely. All good UX to think through on a per feature basis. * **On Hosting:** * A large part of the philosophy behind the WP AI Client is to avoid coupling to any one provider. For now, cloud-based models are the most reliable and easiest to onboard with, but that will quite likely change. Browsers are experimenting with having a model included, which the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. AI team has discussed connecting with as an intent. This is true of local models and so forth. The hosting strategy is the fastest and (from an average user perspective) the simplest way forward at this moment. I personally do believe we’ll have lots of great opportunities to explore local and OSS models to make this even more accessible. 🙂 - ![](https://secure.gravatar.com/avatar/4b04f3868d5d00557a0e117f43262a23de2b023b16cf33e18bf233ecce7e4515? s=32&d=mm&r=g) - [Hudson Atwell](https://profiles.wordpress.org/hudson-atwell/) 2:30 am _on_ December 6, 2025 - Great points on both fronts. Anytime. Ty, too. 30. ![](https://secure.gravatar.com/avatar/d46006b4017f007537a2c0dcf966ca7b3a5e0a3c89d2c15a569596da7329d561? s=32&d=mm&r=g) 31. [Anthony Hortin](https://profiles.wordpress.org/ahortin/) 2:05 am _on_ December 5, 2025 32. First and foremost, if WordPress intends to invest this heavily in the use of AI, then it also needs to provide a way to turn every single AI option, completely off. Right from the very start! Not everyone is as enthusiastic as yourself, in giving AI access to their sites, or encouraging the use of AI slop. Too many companies are forcing AI into their apps with little to no thought on whether the end user actually wants it. 33. * ![](https://secure.gravatar.com/avatar/c6992b336d142228011bd36c3e3a3bbe7da868af9dcf2aff4a648ec2cc0b46d1? s=32&d=mm&r=g) * [Jason Adams](https://profiles.wordpress.org/jason_the_adams/) 9:43 pm _on_ December 9, 2025 * This is an important discussion! I’ve opened an [Issue in the WP AI Client](https://github.com/WordPress/wp-ai-client/issues/38) repository for us to continue the discussion there. It’s important we have proper systems of control in place. I invite you to join the discussion and feel free to share concerns, solutions, or specific scenarios you have in mind. * Thank you! 34. ![](https://secure.gravatar.com/avatar/2ada113f1a81801cf4421e0b5af53c08bab45292957545dc68753ac5147b7c6f? s=32&d=mm&r=g) 35. [Tom J Nowell](https://profiles.wordpress.org/tjnowell/) 1:24 pm _on_ December 5, 2025 36. We have clients who cannot use AI for compliance and legal reasons, and any proposed use has to be individually vetted. Is there a way of turning this off by default at a code level and opting in so that we be sure no 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/](https://wordpress.org/plugins/) or can be cost- based plugin from a third-party. is exposing data to AI companies or models that might train or leak data? 37. I’m mindful that all of this is high positive energy, and the WP AI Client repo is very keen on _how_ to use it, but there is nothing mentioned about protections and controls. Reading through the code I see there’s a capabilitycapability A** capability** is permission to perform one or more types of task. Checking if a user has a capability is performed by the `current_user_can` function. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts (the “edit_posts” capability), but not permission to edit other users’ posts (the “edit_others_posts” capability). registered for allowing admins to directly prompt the AI models via the client, but no mention of that in the documentation. 38. The best I could come up with is this untested snippet, though I’ve not looked deep enough to check where it should go: 39. ```notranslate global $wp_ai_client_providers_metadata; $wp_ai_client_providers_metadata = []; ``` 40. I could find no filters for AI provider availability ( what if I want to use a more expensive model _but only for certain users/environments/tasks?_ What if I want to disable a model locally in code so it isn’t used accidentally when it’s copied to local and runs up a massive bill? ), entire classes are lacking in 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 filters for basic things. 41. I was hoping to see a measured well thought out approach to this, and I’m hopeful we see some counterbalance that acknowledges that there are more reasons to control AI than just “slop”. E.g. data security, costs, data breaches at the model provider, system prompts, injections attacks. What’s to prevent a rogue plugin update abusing our AI 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 to steal compute? Or a mistake on a local environment running up millions of wasted tokens in a cron job? 42. * ![](https://secure.gravatar.com/avatar/c6992b336d142228011bd36c3e3a3bbe7da868af9dcf2aff4a648ec2cc0b46d1? s=32&d=mm&r=g) * [Jason Adams](https://profiles.wordpress.org/jason_the_adams/) 9:41 pm _on_ December 9, 2025 * Thanks for the thoughtful comment and questions, Tom! I’ll try and address what I can, leaving room for more to learn from here, as AI is a fast moving ship. * > Is there a way of turning this off by default at a code level and opting > in so that we be sure no 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/](https://wordpress.org/plugins/) or can > be cost-based plugin from a third-party. is exposing data to AI companies > or models that might train or leak data? * First and foremost, it almost goes without saying, don’t install plugins you don’t trust. I’m sure you know this, but I’m saying it for everyone. Plugins have the ability to run arbitrary code on your server and whether or not AI is available doesn’t stop them from doing things with your data. This, on principle, really has nothing to do with AI. * That said, this is an important discussion! I made an [Issue in the WP AI Client](https://github.com/WordPress/wp-ai-client/issues/38) repository so we can dive into this further. * I’ve reached out to others to ask for their ideas. Please join the discussion so we can make sure to consider this carefully and come up with a proper solution. Feel free to drop in specific concerns and scenarios for us to consider! 43. ![](https://secure.gravatar.com/avatar/e994054dac8d6935f2774ea0aff3a620e4694b29c7e08d103c59e553cbd9bd87? s=32&d=mm&r=g) 44. [Paul Shryock](https://profiles.wordpress.org/paul-shryock/) 2:46 pm _on_ December 5, 2025 45. No thanks. 46. * ![](https://secure.gravatar.com/avatar/c6992b336d142228011bd36c3e3a3bbe7da868af9dcf2aff4a648ec2cc0b46d1? s=32&d=mm&r=g) * [Jason Adams](https://profiles.wordpress.org/jason_the_adams/) 5:31 pm _on_ December 29, 2025 * I’m gathering you’d prefer AI to not be available in your WordPress site(s). If you have any specific feedback or thoughts on how to control/disable AI, you’re welcome to contribute to the discussion in the [WP AI Client Issue](https://github.com/WordPress/wp-ai-client/issues/38) about this. 🙂 47. ![](https://secure.gravatar.com/avatar/4f2a3ef2cdcbc7acc8092a33b574c2cf3496d95d6d74ea12bccd056cab4fc0e2? s=32&d=mm&r=g) 48. [Jon Waldstein](https://profiles.wordpress.org/jonwaldstein/) 6:04 pm _on_ December 5, 2025 49. This is a great thought experiment. 50. I think that WordPress investing in AI, means empowering people to build things faster and in some cases even more intuitively. I can imagine a future for website owners and builders to rely less on a plethora of UIUI User interface controls with the rise of using our native language as an alternative. 51. From 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. standpoint, there is a lot to like about actually having an API lol. AI will inevitably be coming to the WordPress ecosystem regardless, so we might as well join forces as a community to build a unified solution. 52. I’m optimistic that we’ll figure out the logistics of how this will work safely but even more excited about the powerful possibilities! 53. ![](https://secure.gravatar.com/avatar/8cf7655071f82970f9635a0c7e7646551756c333b57166083e506a72cad98916? s=32&d=mm&r=g) 54. [David Anderson / Team Updraft](https://profiles.wordpress.org/davidanderson/) 12:29 pm _on_ December 6, 2025 55. > What if, from the end-user to 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/](https://wordpress.org/plugins/) > or can be cost-based plugin from a third-party. developer, they could take > for granted that there’s an AI model accessible to me by virtue of being in > WordPress? 56. Well, for one thing, from what I’ve read, it would probably mean we could no longer take for granted the presence of the database. 🙂 57. * ![](https://secure.gravatar.com/avatar/3675e517648529c13627e384ef76c3bfc81f7ef216951f4d0cdad6732cb4be29? s=32&d=mm&r=g) * [mkdev](https://profiles.wordpress.org/mkdev/) 3:06 pm _on_ December 8, 2025 * All cool! But before “WordPress will grow into the next phase” can we at least have mobile-responsive controls in the editor? 🙂 - ![](https://secure.gravatar.com/avatar/5bccf439e28a96b79ced740b6c17811af9340bef54767c639c601953de5b1551? s=32&d=mm&r=g) - [SirLouen](https://profiles.wordpress.org/sirlouen/) 6:49 pm _on_ December 9, 2025 - This AI thing is a parallel project. Not everyone is working on everything. The AI members are completely independent from the Editor members. * ![](https://secure.gravatar.com/avatar/c6992b336d142228011bd36c3e3a3bbe7da868af9dcf2aff4a648ec2cc0b46d1? s=32&d=mm&r=g) * [Jason Adams](https://profiles.wordpress.org/jason_the_adams/) 8:25 pm _on_ December 9, 2025 * > Well, for one thing, from what I’ve read, it would probably mean we could > no longer take for granted the presence of the database. * Can you elaborate on this, please? I’m not following how you arrived at this conclusion and I want to understand. 🙂 58. ![](https://secure.gravatar.com/avatar/c351da0b667baf3599ca3492cb29b3f872fca04ace42e252cd8bdc8f9eb059e9? s=32&d=mm&r=g) 59. [Prashant Baldha](https://profiles.wordpress.org/pmbaldha/) 9:32 am _on_ December 9, 2025 60. Love this direction! 🚀 61. Making AI a fundamental part of WordPress will empower developers and creators with smarter, built-in tools without the hassle of extra setup. The proposed unified AI client feels like a game-changer. 🔧🤖 62. Excited to see how this shapes the future of the ecosystem! ✨ 63. * ![](https://secure.gravatar.com/avatar/c6992b336d142228011bd36c3e3a3bbe7da868af9dcf2aff4a648ec2cc0b46d1? s=32&d=mm&r=g) * [Jason Adams](https://profiles.wordpress.org/jason_the_adams/) 8:56 pm _on_ December 15, 2025 * I appreciate the enthusiasm and excitement! 😄 64. ![](https://secure.gravatar.com/avatar/affd6fba1ac644529708d2c80e5d45420698ab62003d12d5376f88dc0c249c06? s=32&d=mm&r=g) 65. [Kevin Batdorf](https://profiles.wordpress.org/kbat82/) 6:04 am _on_ December 10, 2025 66. Has there been discussion on whether WordPress needs an AI code of ethics that developers should follow with regards to how AI should be used? Both in general and specifically to be hosted on w.org? Otherwise I feel like it’s a dangerous free-for-all. 67. For example, should a 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. be allowed to process user data via AI without human in the middle confirmation? What data/files/etc are on/off limits? Should a plugin be able to let AI write to disk? Can an AI decide to “ phone home” (how much agency does the AI have)? 68. Just some ideas I haven’t personally thought out much yet. 69. > Adoption and innovation of the Abilities 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., WP AI Client, > and MCP Adapter from developers is critical 70. Are there plans to promote or boost developers who create unique experiences? Much like 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.” specific plugins that are scoped to specific blocks, should there be exposure incentive to devs likewise creating scoped tooling specifically related to AI? 71. * ![](https://secure.gravatar.com/avatar/c95de1e6c222121175c2c0dddf4631d2ea45704938f53332d12710379c6153e6? s=32&d=mm&r=g) * [Jeffrey Paul](https://profiles.wordpress.org/jeffpaul/) 11:06 pm _on_ December 10, 2025 * There’s some in-progress work to create some policies around AI usage within the project, but none that I believe specifically target what a 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. can or cannot do. That later bit feels like something perhaps the [Plugins team](https://make.wordpress.org/plugins/) could do in extending any project-wide policies. As for the boosting of AI- based plugins, there’s nothing currently planned on that topic but would be a good item to raise in a [Meta Trac](https://meta.trac.wordpress.org/) ticketticket Created for both bug reports and feature development on the bug tracker. as something best discussed there. 72. ![](https://secure.gravatar.com/avatar/82b5a152df9fb7ea4c3eb99703ee00f04982391b94dd47a7390c31e3024eb3a7? s=32&d=mm&r=g) 73. [Patrick Johanneson](https://profiles.wordpress.org/pjohanneson/) 12:08 am _on_ December 13, 2025 74. > What amazing things would people create that are built on the reliable presence > of a capable LLM? 75. Nothing I’ve seen yet convinces me that there’s such a thing as a “capable LLM”, so this is a bit like asking “What amazing things would people create that are built on the reliable presence of an actual elf?” 76. Also: add my voice to the chorus demanding complete, transparent, and effective opt-out controls on this. 77. * ![](https://secure.gravatar.com/avatar/e153b7d4a6f60ae4bd4de278e8dfdf80a1879d4309465b17a2ae76511df6ab16? s=32&d=mm&r=g) * [tyeth](https://profiles.wordpress.org/tyeth/) 12:16 am _on_ December 13, 2025 * Same here. Want to opt out on behalf of clients I host. * Also, who is funding this AI token based system, and why is everything encouraged towards a subscription AI first model that hasn’t been proven cost effective, let alone even goal effective. * At the same time, a local model that ran optimally on low end hardware, was accurate + safe, and provided great value would obviously be useful / wonderful, but unlikely before 2030. - ![](https://secure.gravatar.com/avatar/c6992b336d142228011bd36c3e3a3bbe7da868af9dcf2aff4a648ec2cc0b46d1? s=32&d=mm&r=g) - [Jason Adams](https://profiles.wordpress.org/jason_the_adams/) 5:41 pm _on_ December 29, 2025 - Hi! You’re welcome to share your thoughts in the the WP AI Client Issue if you have specific ideas on how we can better control/disable AI. I agree it’s important. - As far as funding, the initial strategy being presented is for [WP hosts to innovate ways to handle the cost](https://make.wordpress.org/ai/2025/12/04/ai-for-wordpress-hosts/). It’s not just a cost thing, either, but also about lowering the bar of even introducing AI to a site as creating accounts, getting APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. keys, and such is understandably too complex for many folks. - There are promising results for WebGPU-powered models right now, actually! A good example of this is the [LFM2 model](https://huggingface.co/spaces/LiquidAI/LFM2-WebGPU) by LiquidAI. This also helps with things like privacy and security, which is exciting. * ![](https://secure.gravatar.com/avatar/c6992b336d142228011bd36c3e3a3bbe7da868af9dcf2aff4a648ec2cc0b46d1? s=32&d=mm&r=g) * [Jason Adams](https://profiles.wordpress.org/jason_the_adams/) 5:36 pm _on_ December 29, 2025 * Thank you for sharing your thoughts and concerns! * I won’t try and argue about the value of what AI can produce. For some folks it feels like magic and for others its unreliable and sloppy. This surfaces the reality that getting value from AI is not a given and takes skill/effort. This motivates folks like myself to continue to work to see how we can stabilize the results as valuable — as well as (and I feel strong about this) help folks understand when AI _is not_ a good solution for something. * Also, if you have any specific thoughts on how we can control/disable AI, please join the discussion in the [WP AI Client Issue](https://github.com/WordPress/wp-ai-client/issues/38). 🙂 78. ![](https://secure.gravatar.com/avatar/dbd7b3c9ec285cf57b1b39ecc20bdf8b5da09d6165758fe37ce8151751a816c2? s=32&d=mm&r=g) 79. [pjedavison](https://profiles.wordpress.org/pjedavison/) 12:49 am _on_ December 16, 2025 80. No. No, no, no, no, NO. Absolutely one thousand per cent not. 81. Generative AI is an economic, environmental and societal disaster waiting to happen, and the general public outside of goldrushing AI nerds (who were probably all “to the moon!” about NFTs and the Metaverse too) absolutely HATES it. Creative types, who make up a significant proportion of the WordPress user base, also hate it. Read the goddamn room. 82. We do not need slop generation and lying chatbots built into WordPress. If you insist on trying to jam this garbage into the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. WordPress offering, as others have said, at least have the decency to allow everyone to turn it off. Completely. Otherwise you are going to find a lot of people who have been considering jumping ship for some time finally finding the motivation to actually do so. 83. I hear Ghost is pretty good. 84. * ![](https://secure.gravatar.com/avatar/c6992b336d142228011bd36c3e3a3bbe7da868af9dcf2aff4a648ec2cc0b46d1? s=32&d=mm&r=g) * [Jason Adams](https://profiles.wordpress.org/jason_the_adams/) 5:50 pm _on_ December 29, 2025 * I appreciate your passionate thoughts! * If it helps, the proposal here isn’t to be prescriptive about which models to use or even how. Ideally, we’d see more local models such as [LMF2](https://huggingface.co/spaces/LiquidAI/LFM2-WebGPU), which use less resources and are secure/private by default. The way we’re going about this is to support those models as well as cloud-based models. * As far as “slop” is concerned, you’re certainly right that this is quite possible. I think of it similar to database bloat that can bring a site to its knees. Any system needs to be used mindfully and in a way that scales while bringing real value. The good news is that, ultimately, users/customers care about what helps them to create value, which will become increasingly true as the fad of AI for the sake of AI diminishes. This means folks utilizing generative AI within products will need to make sure the AI produces value reliably. This is happening in many products now, but to your point it’s easy to take the lazy route, generate slop, and throw it out there. AI isn’t a magic wand; it’s another tool to be used responsibly. * Lastly, if you have specific thoughts on how to control/disable AI usage in WordPress, you’re welcome to share your ideas in the [WP AI Client Issue](https://github.com/WordPress/wp-ai-client/issues/38) for the topic. 🙂 85. ![](https://secure.gravatar.com/avatar/32f74bcee58afa01ac192560fac183d7d582f7be37779dc0bb2afc747fb4e415? s=32&d=mm&r=g) 86. [flberger](https://profiles.wordpress.org/flberger/) 9:40 am _on_ December 21, 2025 87. This is sad news. If projects absolutely want to connect to unethical services, by all means they should do so via pluggable components – not making it “a fundamental part”. Losing crucial infrastructure one by one to a hype that is engineered to damage both society and the planet is heartbreaking to witness. We lost WordPress, and I will shift the sites I manage to alternative solutions, hoping some islands withstand the flood. 88. * ![](https://secure.gravatar.com/avatar/c6992b336d142228011bd36c3e3a3bbe7da868af9dcf2aff4a648ec2cc0b46d1? s=32&d=mm&r=g) * [Jason Adams](https://profiles.wordpress.org/jason_the_adams/) 6:10 pm _on_ December 29, 2025 * Hello! Sorry to hear this saddens you. Let me see if I can provide any clarity that’s comforting. * First, this is being proposed as infrastructure, not something concrete. In other words, WP will have the ability to integrate with an AI model, but it doesn’t come with any bundled integrations. This means that a fresh WP install is not using AI. The site owner would need to opt to use AI through a host, 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party., and such. * Building on this, it remains in the control of the site owner to side if and what AI providers they want to connect to. There are ethical providers, even some that are things like HIPAA compliant for handling sensitive information. It’s important that these are usable so folks can opt to use model(s) they feel good about, if any at all. This will also extend to things like local models to reduce cloud-based usage. * I’m sure that doesn’t address all your concerns, but wanted to share at least a couple things in case it’s comforting. 🙂 89. ![](https://secure.gravatar.com/avatar/86456359a84a8bc5d9717cdbd5f0bd4f1f6aaa452d9f4b993eda2f0e14aa66a5? s=32&d=mm&r=g) 90. [Juanma Guerrero](https://profiles.wordpress.org/juanma-guerrero/) 6:58 pm _on_ December 24, 2025 91. I can’t believe all tech companies keep pushing AI into our faces without giving abilities to turn completely off or opt-out (which, by the way, should be opt- in, deactivated by default…). 92. If things keep this way, I understand there will be a break in the community and many will migrate to other CMS options. I have deactivated automatic updates on my websites until I see what comes out of all this… 93. * ![](https://secure.gravatar.com/avatar/c6992b336d142228011bd36c3e3a3bbe7da868af9dcf2aff4a648ec2cc0b46d1? s=32&d=mm&r=g) * [Jason Adams](https://profiles.wordpress.org/jason_the_adams/) 5:59 pm _on_ December 29, 2025 * Thank you for chiming in within the [WP AI Client Issue](https://github.com/WordPress/wp-ai-client/issues/38) on the topic. I agree that it’s important to make sure site owners have control. WordPress philosophically puts control in the hands of each site owner and will continue to be this way. As a note, too, the intention of WordPress itself is that it _does not_ ship with any specific model integration. This effectively means it is opt-out by default. * The hope here is to carefully introduce the ability to integrate with AI in a way that is flexible enough to be disabled, work with local models, work with HIPAA compliant models, and so forth. * It’s quite possible to introduce AI as an option without pushing it in anyone’s faces. 🙂 94. ![](https://secure.gravatar.com/avatar/fe4bb42f5cfd28c796ed7b2dffb299ad49f14d3cd3ed4abf1b648244f6771863? s=32&d=mm&r=g) 95. [T](https://profiles.wordpress.org/mateitudor/) 7:44 pm _on_ December 24, 2025 96. Please make sure whatever this is it will be _opt in_, so we can have ethical websites by default. Thanks in advance! 97. * ![](https://secure.gravatar.com/avatar/c6992b336d142228011bd36c3e3a3bbe7da868af9dcf2aff4a648ec2cc0b46d1? s=32&d=mm&r=g) * [Jason Adams](https://profiles.wordpress.org/jason_the_adams/) 5:53 pm _on_ December 29, 2025 * Hello! To be clear, there is no plan to make it such that WordPress itself automatically does anything with AI. The AI system would sit there passively to be optionally used by themes/plugins, which remains at the discretion of the site owner. * There’s also [discussion](https://github.com/WordPress/wp-ai-client/issues/38), which you’re welcome to share thoughts in, on how best to control/disable AI within sites. It is an important context for reasons of preference, security, and so forth. You’re not alone in thinking this. 🙂 98. ![](https://secure.gravatar.com/avatar/f796f3d4d9e99572bc0b5a59924b6e91880a7d2872b291a0c83b1f7008148d4f? s=32&d=mm&r=g) 99. [Christopher Mackay](https://profiles.wordpress.org/christantramarca/) 8:16 pm _on_ December 31, 2025 100. Can’t begin to express how deeply I want nothing whatsoever to do with AI anywhere, let alone inside WordPress. 101. It’s unethical, it’s environmentally unsustainable, and it’s a disinformation machine *at best*. 102. Keep this billionaire’s profoundly irresponsible fever-dream as far away as possible from my websites. 103. * ![](https://secure.gravatar.com/avatar/c6992b336d142228011bd36c3e3a3bbe7da868af9dcf2aff4a648ec2cc0b46d1? s=32&d=mm&r=g) * [Jason Adams](https://profiles.wordpress.org/jason_the_adams/) 8:57 pm _on_ December 31, 2025 * Thank you for sharing your thoughts. You’re not alone in your concerns surrounding AI, which I can appreciate. * I want to make it clear that AI will not be quietly forced on anyone using WordPress. By default, the client being bundled into WordPress won’t include any specific integrations with AI providers. This is by design, to avoid implicitly endorsing any specific provider or forcing connection. So folks have agency in connecting to a provider if they are interested in utilizing AI. * There’s also a [discussion](https://github.com/WordPress/wp-ai-client/issues/38) going on to make sure we have clear thinking on how to control/disable AI. It’s always important that the WordPress site owner has full control and agency over their own site, especially as AI is concerned. It’s a powerful tool but one which needs to be used thoughtfully, and some may fairly choose not to use at all. Comments are closed. # Post navigation [← What’s new in Gutenberg 22.2 (03 December)?](https://make.wordpress.org/core/2025/12/03/whats-new-in-gutenberg-22-2-dec3/) [Coding Standard Proposal: Allow the use of the PHP short echo tag →](https://make.wordpress.org/core/2025/12/05/coding-standard-proposal-allow-the-use-of-the-php-short-echo-tag/)