>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3542200. --> Reported by: [abhisekmazumdar](https://www.drupal.org/user/3557964) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>For Drupal CMS, in the installer or when setting it up via CLI, we will face a problem: there are N number of AI provider modules and setups. A user can choose OpenAI or Anthropic.</p> <p>As Marcus explained it here: </p> <p><span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-13"><a href="https://www.drupal.org/project/drupal/issues/3463641" title="Status: Needs work">#3463641: Create a way for recipes to check their preconditions</a></span><br> <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/ai/issues/3525303" title="Status: Closed (fixed)">#3525303: Create Plugin Action for Recipes to check for installed default provider</a></span></p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>In addition to the two workarounds provided by Marcus in the links above, I would like to discuss a solution I have in mind and work on creating a POC around it.</p> <p>After the standard Drupal CMS installation, we can either redirect the user to a custom form page for enabling AI or add a section in the dashboard promoting the enable necessary AI options.</p> <p>This should occur after the standard Drupal installation because so that we can use the Package Manager module (the same module used for automatic updates and the Project Browser) to require the selected AI provider and update the composer file accordingly.</p> <p>Since the module(any AI provider or vector database provider) is required, we can apply the necessary AI recipes.</p> > Related issue: [Issue #3532795](https://www.drupal.org/node/3532795) > Related issue: [Issue #3463641](https://www.drupal.org/node/3463641) > Related issue: [Issue #3525303](https://www.drupal.org/node/3525303)