# Adding a Billable Feature to Duo Agent Platform ## Process Background - Please fill out this template when you are adding a newly billable feature to Duo Agent Platform. - Beta or GA features can consume usage Credits. - Usage Billing requires each billable feature to be added to an opt-in list, otherwise usage of that feature will not consume credits. - Please open this request **one milestone** before you intend for the feature's usage to consume credits. ## Details Needed 1. Feature name: `GitLab Duo mention responses in merge requests (Code Review Flow)` 1. feature_qualified_name (ex. workflow_definition): `gitlab_duo_mention_assistant/v1` 1. feature_ai_catalog_item (TRUE or FALSE): `false` 1. is feature_ai_catalog_item required? (TRUE or FALSE): `false` 1. Date on which feature's usage should consume credits: `As soon as possible, in 19.3`. This is earlier than the template's one-milestone-ahead guidance. We're asking for an exception because this closes an existing gap in billing for a feature that is already live and already documented as consuming credits, rather than launching something new. ## Why this is being requested - `gitlab_duo_mention_assistant/v1` powers the response when a user mentions `@GitLabDuo` in a merge request discussion thread, or replies to a Duo review comment. It is part of the Code Review Flow feature surface, not a separate product. - The parent Code Review Flow (`code_review/v1`) is GA and already consumes credits. Mention responses run as a separate flow config, so they emit usage events under a different `workflow_definition` and were never added to the billable opt-in list. - As a result, these events are being emitted but not billed. This was spotted from live usage-event data. - Customer documentation already states that these interactions consume credits: https://docs.gitlab.com/user/duo_agent_platform/flows/foundational_flows/code_review/#interact-with-gitlab-duo-in-reviews — "Discussions with GitLab Duo in comments use GitLab Duo Agent Platform and consume credits." So the docs update step in "Next Steps" is likely already satisfied; the gap is the opt-in list, not the docs. - The flow was introduced by the work to move `@GitLabDuo` mention interactions onto Duo Agent Platform: https://gitlab.com/gitlab-org/gitlab/-/work_items/585237+ (shipped in GitLab 19.1). - It is not an AI Catalog item — the flow config ID is set in the monolith (`ee/app/services/ai/messaging/adapters/gitlab_duo_note.rb`) and passed straight through to Duo Workflow Service, so no `Ai::Catalog::Item` backs it. - Related: https://gitlab.com/gitlab-org/customers-gitlab-com/-/work_items/18669 plans an allowlist of known `workflow_definition` values at the usage-quota API. This flow needs to be on that list as a billed flow rather than a known-unbilled one. - Raised by the Utilization group in Slack; confirmed by @phikai and @kinsingh that it should be billed. ## Approvals Needed In order to add a billable feature to DAP, you must get approval from each of the teams below: - Pricing — @sarah_zywicki (Backup: @jennguyen OR @steph_cheung) - Default (no flat rate pricing) - {+Approved+}: https://gitlab.com/gitlab-org/customers-gitlab-com/-/work_items/18694#note_3741399271 - Revenue Accounting — @msubramanian (Backup: @brianon ) - {+Approved+}: https://gitlab.com/gitlab-org/customers-gitlab-com/-/work_items/18694#note_3740872066 - Billing — @tcheeney OR @JosephineHararah - {+Approved+}: https://gitlab.com/gitlab-org/customers-gitlab-com/-/work_items/18694#note_3740872066 Ensure each of these approvals is documented on this issue. ## Next Steps: 1. The issue will be worked on by the Utilization Group. The Utilization Group is responsible for validating that the feature works as expected after usage billing is applied. 1. It is your responsibility to **update the customer documentation to include your billable feature**. 1. You can add your feature to the [DAP GA Features table](https://docs.gitlab.com/user/duo_agent_platform/#generally-available-features) or the [DAP Billable Beta Features table](https://docs.gitlab.com/user/duo_agent_platform/#beta-features-that-consume-credits). 1. You also need to remove the feature from the [DAP Non-Billable Beta Features table](https://docs.gitlab.com/user/duo_agent_platform/#beta-and-experiment-features) if it appears there. 1. You only need to make these updates for the Docs version in which your feature will begin consuming credits.