## Summary Roll out [the feature](https://gitlab.com/gitlab-org/gitlab/-/work_items/605161) currently behind the `duo_chat_flow_commands` feature flag. - DRI: @samdbeckham - Team Slack channel: `#g_ai_catalog` The flag gates the slash command Duo Agentic Chat offers for each AI Catalog flow enabled in the current project, which starts that flow directly. Introduced in [!252920](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/252920), milestone %"19.4". This issue is being opened after the fact: the flag was already enabled globally on production on 2026-09-14 and the feature is [confirmed working there](https://gitlab.com/gitlab-org/gitlab/-/work_items/605161#note_3831968938). The percentage rollout below is recorded for completeness, so the real remaining work is the two items under **Definition changes needed** plus **Cleanup**. > [!note] > Process and guidance live in the docs — this issue is just the commands and a place to track the rollout. > "Rolling out" means incrementally enabling the flag on GitLab.com to validate stability — it is not the same as releasing the feature, which happens when the flag is removed. > [Feature flag controls](https://docs.gitlab.com/development/feature_flags/controls/) · [Feature flag lifecycle](https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/feature-flag-lifecycle/#feature-flag-lifecycle) ## Definition changes needed `ee/config/feature_flags/wip/duo_chat_flow_commands.yml` is still `type: wip`, which is the type for code that is merged but hidden while incomplete. The feature is complete and enabled, so: - [ ] Change the type from `wip` to `gitlab_com_derisk` (short-lived, removed soon) or `beta` (kept as an off switch for self-managed), and move the YAML file into the matching directory. A `wip` flag should be transitioned before it is enabled, and its lifespan is capped at 4 months from merge — see [`wip` type](https://docs.gitlab.com/development/feature_flags/#wip-type). - [ ] Set `rollout_issue_url` in the YAML to this issue. It is currently blank. ## What could go wrong? - The command list is built from every flow enabled in the project, regardless of its triggers. Projects with many enabled flows get a long command list. - Two flows can produce the same command name. The current behaviour appends the consumer ID to the second one, which is ugly but visible. Tracked as an open question on [#605161](https://gitlab.com/gitlab-org/gitlab/-/work_items/605161). - Starting a flow spends CI minutes, and the flow can act on real issues and merge requests. There is no test-mode containment, so repeated runs leave real comments. - Session persistence depends on the AI Gateway change in [ai-assist!6690](https://gitlab.com/gitlab-org/modelops/applied-ml/code-suggestions/ai-assist/-/merge_requests/6690). If the gateway and monolith versions drift, chat can lose track of a session it started. - Disabling the flag removes the commands from chat. It does not stop sessions that are already running. ## Events - [Exceptions with duo_chat_flow_commands:1](https://log.gprd.gitlab.net/app/discover#/?_g=(time:(from:now-1d,to:now))&_a=(index:'7092c4e2-4eb5-46f2-8305-a7da2edad090',query:(language:kuery,query:'json.exception.feature_flag_states.keyword:%22duo_chat_flow_commands:1%22'),columns:!(json.exception.class,json.exception.message,json.extra.workflow_id,json.meta.caller_id),sort:!(!(json.time,desc)))) - [Events with duo_chat_flow_commands:1](https://log.gprd.gitlab.net/app/discover#/?_g=(time:(from:now-1d,to:now))&_a=(index:'7092c4e2-4eb5-46f2-8305-a7da2edad090',query:(language:kuery,query:'json.feature_flag_states:%22duo_chat_flow_commands:1%22'),columns:!(json.meta.caller_id,json.feature_flag_states),sort:!(!(json.time,desc)))) - [Error rate and other graphs by modifying the examples in the Visualization Library](https://log.gprd.gitlab.net/app/visualize#/?_g=h@358d019&s=FF%20Observability) Feature Flag events are only logged by default for feature flags marked for the current or future milestones. To enable while the feature flag is active, see https://docs.gitlab.com/development/feature_flags/#logging ## Rollout Run all production chatops commands in [`#production`](https://gitlab.slack.com/archives/C101F3796) and cross-post the results to `#g_ai_catalog`. Background: [incremental rollout process](https://docs.gitlab.com/development/feature_flags/controls/#process), [feature actors](https://docs.gitlab.com/development/feature_flags/#feature-actors). **Non-production** - `/chatops gitlab run feature set duo_chat_flow_commands 50 --actors --dev --pre --staging --staging-ref` - `/chatops gitlab run feature set duo_chat_flow_commands true --dev --pre --staging --staging-ref` **Production** — percentage rollout (wait at least 15 minutes between steps, watch dashboards): - `/chatops gitlab run feature set duo_chat_flow_commands <percentage> --actors` Or target specific actors instead: - `/chatops gitlab run feature set --project=gitlab-org/gitlab,gitlab-org/gitlab-foss duo_chat_flow_commands true` - `/chatops gitlab run feature set --group=gitlab-org,gitlab-com duo_chat_flow_commands true` - `/chatops gitlab run feature set --user=samdbeckham duo_chat_flow_commands true` Progress: - [x] Enabled globally on production (2026-09-14, done ahead of this issue) ## Before global rollout Confirm the relevant gotchas before going to 100% — see [enabling a feature for GitLab.com](https://docs.gitlab.com/development/feature_flags/controls/#enabling-a-feature-for-gitlabcom): - [ ] [Docs and version history](https://docs.gitlab.com/development/documentation/feature_flags/) updated - [ ] [Breaking changes](https://docs.gitlab.com/development/documentation/release_notes/#deprecations-removals-and-breaking-changes) announced, if any - [ ] [Change management issue](https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/change-management/#feature-flags-and-the-change-management-process) opened, if required - [ ] [External API consumers](https://docs.gitlab.com/development/feature_flags/#do-not-use-feature-flags-in-external-api-consumers) handled with a fail-open mechanism, if applicable ## Cleanup Remove the flag once [deemed stable](https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/feature-flag-lifecycle/#feature-flag-lifecycle) — see [cleaning up](https://docs.gitlab.com/development/feature_flags/controls/#cleaning-up). This is the work [Jafar asked to capture](https://gitlab.com/gitlab-org/gitlab/-/work_items/605161#note_3832053150). Remove the flag and its YAML definition from the codebase, then: - `/chatops gitlab run release check <merge-request-url> <milestone>` - `/chatops gitlab run feature delete duo_chat_flow_commands --dev --pre --staging --staging-ref --production` ## Rollback - `/chatops gitlab run feature set duo_chat_flow_commands false` (production) - `/chatops gitlab run feature set duo_chat_flow_commands false --dev --pre --staging --staging-ref` (non-production) - `/chatops gitlab run feature delete duo_chat_flow_commands --dev --pre --staging --staging-ref --production` (remove entirely)