Take advantage of Project Browser alpha7's new features for recipes

I am curious how well is the drupal_cms_ai recipe with all related modules tested? Because until now, the recipe was hidden and I doubt that a lot of folks searched a way how to enable it in the Drupal CMS dev and tested it. Is it a good idea to expose it this late phase before general release given what all can be done by using the AI in a *wrong* way? (just to note, I have not tested it yet, so this opinion is based on comments from different AI track issues from the past)

That's a product decision, I think, so deferring to Pam to make that call.

My opinion: I suspect people will want to use the AI stuff, considering how spotlighted it has been in Driesnotes, etc. I don't know of any particular reason to hide it. Savvy folks can already use it by applying the recipe at the command line, but I don't know if that makes them any more or less likely to use the AI in the "wrong" way, since it's such a black-box technology to begin with.

since it's such a black-box technology to begin with

I think this should be a reson to be carefull with it, especially given the AI hype and Drupal CMS promo. We were for example close to remove the Coffee module because of performance issues, but on the other hand, there seems to be everything OK when adding a lot of AI modules, when a lot of them has less than 100 installs and are even without security coverage (yes, the recipe is already included, and I think a bigger issue is exposing it to everyone)? For example this one ( https://www.drupal.org/project/ai_simple_provider_installer → ) is not even opted into security advisory coverage.

So probably a question for @pameeela - is there any possibility to postpone the intention to expose the AI recipe to a later minor version of Drupal CMS? It will be still included (if I understand correctly), but not available to all, only to those with some technical knowledge.

@poker10 the recipe was hidden because the functionality to prompt for the API key was not ready, so the recipe application was fairly manual and we didn't have a way to explain the manual steps. It has been undergoing large amounts of testing including with end users via the AI team in coordination with UX folks.

So we're ready to expose it now because we can provide a relatively simple setup process. However, in order to use it, you still need to provide an API key from either Open AI or Anthropic, with paid credit. So you need to be fairly savvy to get it working anyway at this point, it's not like you can apply the recipe and run wild with AI everywhere. Additionally, the functionality is limited and targeted. It's certainly not perfect, but neither is a lot of Drupal CMS. For my part I can't argue with the obvious demand for this functionality, even if I personally am not overly enthusiastic about it.

The AI team will be tagging a stable release before the weekend, so security coverage won't be an issue.

About time we had this! Merged into 1.x and cherry-picked to 1.0.x.

It has been undergoing large amounts of testing including with end users via the AI team in coordination with UX folks.

That is possible, but it still recommends to download Drupal 9 (if you ask which Drupal version to use), posting links to non-existing modules and docs pages and some commands are not even executed because of Guzzle timeouts. Seems like a lot of issues for new Drupal CMS users to fight with:

https://www.drupal.org/project/ai/issues/3479159#comment-15936515 🐛 cURL Timeout and Deprecated Function Error When Using AI Translate Submodule Active
https://www.drupal.org/project/ai/issues/3498934 🐛 Instructions how to use cron are outdated Active
https://www.drupal.org/project/ai/issues/3498932 🐛 Links provided by AI assistant are frequently not working Active

And I only started to test it..

And now imagine someone will use the SEO checklist module included in Drupal CMS and start asking AI assistant things based on that list (how to xxx ...). That will not be funny at all.

Automatically closed - issue fixed for 2 weeks with no activity.