Create Duo Developer 'Auto' option

Julie Huangrequested to merge
duo-developer-auto-model-selection into master

What does this MR do and why?

As part of phase 1 of the phased rollout plan for intelligent model selection, this MR re-labels the GitLab default model option as Auto on the Duo Developer feature setting across namespace and instance-level model selection pages.

The change is gated behind the duo_developer_model_routing feature flag.

Changes:

  • Updates admin (namespace and instance-level) model selectors to display the Auto label + description while dropping provider and cost indicators in the model selection pages
  • Pins the Auto option to the top of the model selectors
  • Shows updated copy in the confirmation modal when clicking the Auto option

References

Screenshots or screen recordings

SaaS

Admin model selector

Before (FF disabled) After (FF enabled)
Screenshot_2026-09-10_at_3.01.07_pm Screenshot_2026-09-10_at_3.00.12_pm

Confirmation modal

Before (FF disabled) After (FF enabled)
Screenshot_2026-09-10_at_7.54.23_pm Screenshot_2026-09-10_at_7.50.27_pm

Self-managed

Admin model selector

Before (FF disabled) After (FF enabled)
Screenshot_2026-09-10_at_2.48.57_pm Screenshot_2026-09-10_at_2.46.43_pm

Confirmation modal

Before (FF disabled) After (FF enabled)
Screenshot_2026-09-10_at_2.49.19_pm Screenshot_2026-09-10_at_2.47.03_pm

How to set up and validate locally

Pre-requisites:

  • An active online Ultimate license.
  • Enable the duo_developer_model_routing feature flag (http://gdk.test:3000/rails/features/)

Validating in SaaS:

  1. Start GDK in SaaS mode GITLAB_SIMULATE_SAAS=1 gdk start
  2. Run the Duo setup rake task GITLAB_SIMULATE_SAAS=1 bundle exec 'rake gitlab:duo:setup' to seed the instance with Duo Enterprise.
  3. Navigate to the namespace-level model selection page (http://gdk.test:3000/groups/gitlab-duo/-/settings/gitlab_duo/model_selection) and open the model selector for the Duo Developer feature.
  4. Confirm the default option is relabelled to "Auto" and matches the screenshots.
  5. Select the Auto option and validate the confirmation modal contains the updated copy matching the screenshots.

Validating in self-managed:

  1. Start GDK in self-managed mode GITLAB_SIMULATE_SAAS=0 gdk start
  2. Run the Duo setup rake task GITLAB_SIMULATE_SAAS=0 bundle exec 'rake gitlab:duo:setup' to seed the instance with Duo Enterprise.
  3. Navigate to the instance-level model selection page (http://gdk.test:3000/admin/gitlab_duo/model_selection) and open the model selector for the Duo Developer feature.
  4. Confirm the default option is relabelled to "Auto" and matches the screenshots.
  5. Select the Auto option and validate the confirmation modal contains the updated copy matching the screenshots.

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Julie Huang

Merge request reports