Model Agnostic Prompt Per Feature/ Sub-Feature

Release notes

description: GitLab Duo Self-Hosted now enables "bring your own model" for use with GitLab Duo features. This feature is in beta, and available to all Self-Managed Duo Enterprise customers. Instance administrators can declare any model for use with GitLab Duo features, and configure that model with a "General" prompt. The General prompt is available for all supported GitLab Duo features

While GitLab cannot guarantee compatibility with all models, this is the first iteration towards expands the flexibility of GitLab Duo Self-Hosted. Instance administrators are responsible for validating the performance of their chosen model, and compatible models will not receive full technical support from GitLab.

documentation: ’https://docs.gitlab.com/administration/gitlab_duo_self_hosted/’ 

image:

Details

As Custom Models moves towards enabling self-hosted customers to configure any model API endpoint for use with Duo features, we need to add in optionality that supports generic model usage per sub-features.

We already have examples of customers (one example) who is using model family prompts with "off brand" unsupported models (i.e. the Mistral model family prompt to support Llama 3.1), the Mistral family to support Devstral, etc)

Definition of Done

• There is a "general" or "base" prompt available in the GitLab Self-Hosted drop down when configuring a compatible model (For this iteration, this may map to an existing baseline prompt, such as that for Claude).
• Customers do not have to select "off brand" prompts for use with compatible models, but can instead select the "general" or "base" prompt