>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3577175. --> Reported by: [marcus_johansson](https://www.drupal.org/user/385947) >>> <p>[Tracker]<br> <strong>Update Summary: </strong>[One-line status update for stakeholders]<br> <strong>Short Description: </strong>[One-line issue summary for stakeholders]<br> <strong>Check-in Date: </strong>MM/DD/YYYY<br> <em>Metadata is used by the <a href="https://www.drupalstarforge.ai/" title="AI Tracker">AI Tracker.</a> Docs and additional fields <a href="https://www.drupalstarforge.ai/ai-dashboard/docs" title="AI Issue Tracker Documentation">here</a>.</em><br> [/Tracker]</p> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>In AI 1.0.0 we did add a config action called <a href="https://git.drupalcode.org/project/ai/-/blob/1.0.x/src/Plugin/ConfigAction/SetupAiProvider.php?ref_type=heads">SetupAiProvider</a> for Drupal CMS launch - we have since <a href="https://git.drupalcode.org/project/ai/-/tree/2.0.x/src/Plugin/ConfigAction?ref_type=heads">added some other ones</a>, but all of them are more or less workarounds to patch problems that existed in recipes at the time.</p> <p>What we need is:</p> <ul> <li>A way to check pre-configured requirements. For instance a recipe should only run if a "Chat with Tools" model is properly configured.</li> <li>The same goes for VDB providers - is a VDB provider installed and set as default.</li> <li>A way to create Keys via prompts and save them in a secure manner. Work exists in <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/ai_initiative/-/work_items/3559052" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/ai_initiative/-/work_items/3559052</a></span>.</li> <li>Handle installation of providers that are not simple api key providers like Ollama and Huggingface (complex like AWS, Vertex or Azure excluded).</li> </ul> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <ul> <li>Check related issues.</li> <li>Research this issue.</li> <li>If possible, add actionable follow up issues in AI module or Drupal Core.</li> </ul> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <h3>Optional: Other details as applicable (e.g., User interface changes, API changes, Data model changes)</h3> <h3 id="summary-ai-usage">AI usage (if applicable)</h3> <p>[ ] AI Assisted Issue<br> This issue was generated with AI assistance, but was reviewed and refined by the creator.</p> <p>[ ] AI Assisted Code<br> This code was mainly generated by a human, with AI autocompleting or parts AI generated, but under full human supervision.</p> <p>[ ] AI Generated Code<br> This code was mainly generated by an AI with human guidance, and reviewed, tested, and refined by a human.</p> <p>[ ] Vibe Coded<br> This code was generated by an AI and has only been functionally tested.</p> > Related issue: [Issue #3559052](https://www.drupal.org/node/3559052) > Related issue: [Issue #3562262](https://www.drupal.org/node/3562262)