>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3566997. --> 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>Document current capabilities and architecture of the Drupal AI module<br> <strong>Check-in Date: </strong>MM/DD/YYYY<br> [/Tracker]</p> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Before exploring or committing to a partial or full migration of Drupal AI to Symfony AI, we need a clear, authoritative understanding of what Drupal AI provides today.</p> <p>Drupal AI has grown to include multiple layers and responsibilities, including provider abstraction, vector database integration, AI Agents, chat-related functionality, and a wide range of extension points used by contrib modules. Without a comprehensive and up-to-date description of these capabilities, it is difficult to:<br> - Evaluate feature parity with Symfony AI components.<br> - Identify true blockers versus perceived gaps.<br> - Make informed architectural decisions during the exploratory phase.<br> - Communicate expectations clearly to contributors helping with research and evaluation.</p> <p>This issue exists to establish a written baseline of Drupal AI&rsquo;s current functionality and architecture that can be referenced throughout the exploratory and prototype phases.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>- Write a comprehensive document describing the current capabilities of the Drupal AI module.<br> - Cover both functional features and architectural responsibilities.<br> - Include (at a minimum):<br> - Supported AI providers and models.<br> - The current abstraction layer and its responsibilities.<br> - Vector database support and RAG-related functionality.<br> - AI Agents module capabilities and assumptions.<br> - Chat-related functionality and integration points.<br> - Extension points and APIs relied upon by contrib modules.<br> - Focus on describing what exists today, not what should exist in the future.<br> - Avoid proposing solutions or migration strategies in this document; those belong in separate issues.</p> <p>- <strong>This issue was created with the help of AI</strong></p> > Related issue: [Issue #3565674](https://www.drupal.org/node/3565674)