Switch GitLabDuo mention interactions in MR comments to use Agentic Chat for DAP flow
Problem
Currently, when users interact with @GitLabDuo in MR discussions/comments, the system routes through AIGW Duo Chat endpoints (Classic Duo Chat). This results in:
- No consumption-based billing charges applied
- Inconsistent user experience compared to the DAP-based Duo Code Review feature
- Potential confusion for customers who have different quality experiences depending on how they invoke Duo
Current Behaviour
@GitLabDuo as a reviewer:
- Duo Enterprise customers: Uses classic Duo Code Review (no billing charges)
- Duo Core/Pro customers: Uses new DAP-based Duo Code Review (consumption-based billing applied)
- Exception: Internal users always use the new DAP Duo Code Review even with Duo Enterprise seats
@GitLabDuo mentions in comments (all customers):
- Routes through AIGW Duo Chat endpoints (Classic Duo)
- No consumption-based billing charges applied
- Lower quality experience compared to DAP-based interactions
Proposed Solution
Switch @GitLabDuo mention interactions in discussions/comments to use Agentic Chat/DWS for customers on the DAP flow. This would:
- Enable consumption-based billing charges for these interactions (Duo Core/Pro users)
- Improve interaction quality to match the DAP-based Duo Code Review experience
- Provide a consistent experience across all Duo Code Review touchpoints
Note: Duo Enterprise customers using classic Duo Code Review would remain unchanged.
Related Discussion
Edited by 🤖 GitLab Bot 🤖