Skip to content

[UX] Multiple Model per Duo Feature + Namespace Configuration

Self-hosted model configurations are currently implemented at the instance level, which enables self-managed customers to declare and configure self-hosted models for their instance. Users of GitLab.com do not have these instance level configurations.

SaaS-based Duo features current supports a limited set of models across features on Gitlab.com, and customers lack an in-product mechanism to choose specific models when multiple are supported. New models are introduced via feature flags, which can be challenging to manage for large numbers of users.

Additionally, some customers require internal review processes before adopting new models or subprocessors. Customers may want to continue using prior models during review processes or if new models aren't approved. Some customers may further want to pilot new models with a subset of their team.

This issue is to capture a consolidated UX that would enable both self-hosted models customers and others. This issue supports work proposed in gitlab-com/content-sites/handbook!11970 (merged)

Proposal

  • Allow self-managed, self-hosted customers to configure multiple models per Duo feature.
  • Allow self-managed, Dedicated, and .com admins to select a single model for each Duo feature at the namespace/organization level when multiple are supported.
  • Apply admin model selection to all users in the group.
  • Model list must match the customer's GitLab version.
  • Model availability can be informed by feature flags.
  • For SaaS and Dedicated implementations, customers would not be declaring their models (as they do for self-hosted models), but would instead be selecting from the SaaS supported models
  • For Self-Hosted models implementation, customers would be able to choose from among their hosted models (or adapters) and configure them per feature, per group.
  • Follow the pattern of AI-powered feature model selection in self-hosted models

Definition of Done

  • Self-managed, Dedicated, and .com admins are able to select from among supported models for a feature within the Gitlab UI, configured at the organization, group, and/or project level.

Resources

Edited by Graham Bachelder