>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3567006. --> 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>Research and draft first mapping Drupal AI Agents to Symfony AI Agents (including chat)<br> <strong>Check-in Date: </strong>MM/DD/YYYY<br> [/Tracker]</p> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>In addition to migrating the core abstraction layer and vector database support, we want to evaluate whether Drupal AI Agents (and related chat functionality) can be migrated to Symfony AI Agents. While this is not a hard requirement for switching frameworks, it is important for longer-term alignment and for reducing duplicated agent/chat frameworks across ecosystems.</p> <p>Drupal AI Agents include Drupal-specific concepts such as tool/plugin integration with Drupal capabilities and multi-step workflows. Symfony AI Agents may have different assumptions around tools, memory, chat/session handling, and execution lifecycle. We need an explicit first mapping between Drupal AI Agents&rsquo; current responsibilities and Symfony AI Agents&rsquo; concepts, along with a rough initial idea for how this could be implemented inside Drupal without changing UX.</p> <p>This research depends on:<br> - The documented understanding of Drupal AI&rsquo;s current capabilities (including AI Agents and chat integration points).<br> - The structured document of open questions and unknowns identified during the exploratory phase.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>- Review the Drupal AI capabilities document and extract AI Agents and chat-related responsibilities, supported workflows, and extension points.<br> - Review the open questions/unknowns document and highlight which questions relate directly to agents, tool calling, memory, chat/session handling, and orchestration.<br> - Analyze Symfony AI Agents (and any chat-related APIs) and map them to Drupal AI Agents&rsquo; current model:<br> - Identify direct equivalents where Drupal can become a thin adapter.<br> - Identify mismatches where Drupal AI needs glue code or alternate patterns.<br> - Identify missing capabilities that would require upstream Symfony AI changes or Drupal-side workarounds.<br> - Draft a first-pass &ldquo;mapping&rdquo; document that includes:<br> - A side-by-side mapping of key concepts (Drupal AI Agents responsibilities &rarr; Symfony AI Agents equivalents).<br> - A proposed Drupal-side architecture for integration (rough implementation idea), including:<br> - How agent definitions/configuration would map to Symfony agent setup.<br> - How Drupal tool/plugins would map to Symfony &ldquo;tools&rdquo; and how execution would be bridged.<br> - How memory/state and chat sessions would be stored and restored in Drupal.<br> - How existing Drupal AI Agents APIs and plugin points could wrap Symfony Agents without breaking contrib expectations.<br> - How the Drupal chat experience could be powered by Symfony chat/agent APIs without changing UX.<br> - Summarize feasibility and risks:<br> - Clear list of blockers or major incompatibilities.<br> - Clear list of assumptions and what must be validated in prototyping.<br> - Any areas that likely require upstream contributions to Symfony AI.<br> - Keep this work at the &ldquo;rough plan&rdquo; level: enough detail to guide the prototype phase, but not an implementation task.</p> <p>- <strong>This issue was created with the help of AI</strong></p> > Related issue: [Issue #3538499](https://www.drupal.org/node/3538499)