Currently, there is no self-serving way to know exactly which Agents would be impacted by disabling/excluding objects such as LLMs and Actions. Some of these suggestions are built in, but not across all features.
- Dependency Check on Deletion:
- Implement a dependency check mechanism that runs before allowing the deletion of any object.
- If an object is dependent on another (e.g., an Action within an Agent), the system should either prevent the deletion or offer a solution path (such as assigning a new Action to the Agent).
2. Contextual Information Before Deletion:
- Provide contextual information to users before they delete an item - let them know which Agents are impacted so they can notify the users that their Agent will be impacted and they may want to take action.
- Include prompts that indicate the number of Agents impacted, such as Actions or LLMs linked to the Agent.
- This will help users understand the implications of deleting an item more clearly.
Tracking elements of this in FR-3279
