### Release notes description: GitLab Duo Model Selection is now generally available, giving organizations greater control over which AI models power their development workflows. Model Selection is available for all top-level GitLab owners on GitLab.com, Dedicated, and Self-Managed accessing GitLab Duo via the GitLab-hosted AI Gateway. Namespace administrators on Gitlab.com and instance administrators on Self-Managed and Dedicated can now choose a specific model from a variety of GitLab AI Model Vendors for use with their Duo features. GitLab users that belong to multiple namespaces on GitLab.com can now set a default namespace to ensure consistent AI model preferences across all development contexts. [Read the blog ](https://about.gitlab.com/blog/speed-meets-governance-model-selection-comes-to-gitlab-duo/)for more information on GitLab Duo Model Selection. To get started, access Model Selection through Settings \> GitLab Duo \> Model Selection documentation: 'https://docs.gitlab.com/user/gitlab_duo/model_selection/'[ ](https://docs.gitlab.com/administration/gitlab_duo_self_hosted/%E2%80%99%C2%A0) image:  # Details This epic is to capture the scope and requirements to GA Model Selection for GitLab Enterprise customers using GitLab.com, Dedicated, and Self-Managed ### In Scope * Model Selection access for all namespace admins on **GitLab.com**, and instance admins on **Dedicated, and Self-Managed** using the GitLab.com AIG * Correct model routing in the case of no attributable GitLab resources (context) * Default namespace detection and assignment as possible * Default namespace manual selection as necessary (only Gitlab.com) ### Not in Scope * Model Selection at the namespace level for customers using the GitLab.com AIG (next iteration) * Model Selection support for instance owners on Self-Managed using the Self-Hosted AIG * End-user model selection (will be included in the next iteration) ### Definition of Done * Model Selection is accessible to: * namespace owners on GitLab.com (SaaS) * instance owners on GitLab Dedicated (using GitLab.com AIG) * instance owners on Self-Managed instances (using GitLab.com AIG) * Aforementioned owners can set their preferred models via namespace/instance \> Settings \> GitLab Duo \> Model Selection * System correctly routes requests when no attributable GitLab resources (context) are available * Default namespace detection and assignment works automatically when possible * Users with only one Duo seat assignment see no changes to their experience * Users with multiple Duo seat assignments are prompted to set a default namespace * Users are prompted to set default namespace when any one of their namespaces pins a model * Banner notification appears for users who need to set a default namespace * Error messaging provides clear instructions to set a default namespace * End user can manually set default namespace * Once the user has set the default, all no-context inputs go to the model chosen by the default namespace (or the GL default, if no model is pinned) * All feature flags removed for GA * Grace period logic removed * Documentation updated for Model Selection GA