Model selection compatibility for Duo Code Review on DAP

Problem

With Duo Code Review now integrated into Duo Agent Platform (DAP), there's a disconnect between the model selection UI and the actual model being used:

• Users can select a model for "Duo Code Review" in the model selection interface
• However, since DCR now runs through DAP, it uses the DAP model selection instead
• This creates confusion where users think their selected DCR model is being used when it's not

Current State

• DCR on DAP is enabled for GitLab internal team members via feature flag
• Model selection for remote flows (including DAP) doesn't work with self-hosted models
• All DAP flows currently use a single model selection (no per-flow model selection)

Dependencies

• Blocked by: #575859 (Remote flows for DAP do not work with self-hosted models and model switching)

Proposed Solution

1. First complete the work on #575859 to enable model switching for remote flows
2. Implement a way to respect the existing DCR model selection for the DCR flow within DAP
3. Consider this a high priority for compliance requirements

Related Resources

• Epic: &18645
• DCR Flow Config: https://gitlab.com/gitlab-org/modelops/applied-ml/code-suggestions/ai-assist/-/blob/main/workflow_service/agent_platform/v1/flows/configs/code_review.yml
• DCR Prompts:
  • https://gitlab.com/gitlab-org/modelops/applied-ml/code-suggestions/ai-assist/-/blob/main/workflow_service/agent_platform/v1/flows/definitions/review_merge_request/base/1.4.0.yml
  • https://gitlab.com/gitlab-org/modelops/applied-ml/code-suggestions/ai-assist/-/blob/main/workflow_service/agent_platform/v1/flows/definitions/code_review_prescan/base/1.0.0.yml