Today, there is no way for an instance or top-level group admin to fully disable Custom Agents and Custom Flows as a feature category. Customers with strict AI governance policies need a kill-switch for all custom AI functionality — independent of whether catalog access is restricted — so that only GitLab-managed foundational agents are available to their users. **Proposed Solution** * Add an TLG Owner-level toggle that disables Custom Agents and Custom Flows entirely. When disabled, no user regardless of role should be able to create, enable, or invoke custom agents or flows within the namespace. * Location of proposed toggle: [https://gitlab.com/groups/\[YOUR-GROUP-NAME\]/-/settings/gitlab_duo/configuration](https://gitlab.com/groups/gl-demo-ultimate-rkolosovskiy/-/settings/gitlab_duo/configuration) {width=900 height=535} **Acceptance Criteria** * An admin can disable Custom Agents and Custom Flows at the instance or TLG level * When disabled, existing enabled custom agents and flows are no longer invocable * The setting is reflected in audit logs