>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3556400. --> Reported by: [marcus_johansson](https://www.drupal.org/user/385947) Related to !1475 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Currently we are using modeler api as the way of listing agents and it also makes it possible to use a modeler api based modeler to setup the agents.</p> <p>If we are moving AI Agents to AI Core, we need to decide if we want to keep it and then how. Since we want to move the agents to work inside workflows, if modeler api and ECA is the future, then yes is the obvious answer.</p> <p>But the alternatives I could think of are:</p> <p><strong>(1) Keep as is</strong><br> Modeler api takes care of listing, which also gives some cool export and import functionality. This means that the AI module will require modeler api to be installed everywhere.</p> <p><strong>(2) Have UI submodule</strong><br> Similar to how Views has Views core and Views UI, you might not actually want the possibility to manipulate agents on production, so the setup of an agent should be something that requires a specific submodule. Then we could say that the requirement of Modeler api is to this submodule, not AI Core.</p> <p><strong>(3) Remove the dependency</strong><br> This means that we remove the dependency completely, and just have our "normal" form and other modules that wants to add graphical ways of doing this, has to add this "on top".</p> <p>Personally I lean towards #2, mostly because I could see the security impacts of actually splitting editing and using.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Take a decision.</p>