Modeler API: Modeler is at a different path than the form version

Created on 15 June 2025, 12 days ago

Problem/Motivation

If you click on an agent that doesn't have a model, the path is:

/admin/config/ai/agents/settings/node_content_type_agent

If you edit one that has a model you are taken to a completely different path.

/admin/structure/ai-agent/user_management_agent

Proposed resolution

Update the path to something like:

/admin/config/ai/agents/settings/node_content_type_agent/model

That will also allow the administrator to switch between the model and the form (going to make another issue for that)

Remaining tasks

Update the path

User interface changes

TBD

API changes

TBD

Data model changes

TBD

πŸ› Bug report
Status

Active

Version

1.2

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States thejimbirch Cape Cod, Massachusetts

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @thejimbirch
  • πŸ‡©πŸ‡ͺGermany jurgenhaas Gottmadingen

    This is not a bug and not related to Modeler API, therefore renaming the issue.

    The background is that /admin/config/ai/agents/settings is the original list of agents also back in version 1.0 of AI Agents. Back then, agents have been plugins, and the list of agents gets created by \Drupal\ai_agents\Form\AiAgentsSettingsForm. Now, in AI Agents 1.1, agents can either be plugins or config entities.

    However, the other path is /admin/structure/ai-agent which only contains agents that are config entities. And that path is defined by the config entity annotation.

    To resolve this inconsistency, I guess we have to deprecate agents as plugins. Then, there will only be one list and one path. All editing features will then also utilize the same path.

Production build 0.71.5 2024