[FF] duo_cli_first_party_tools -- trust the GitLab Duo CLI review tool under tool governance

Summary

Roll out the feature currently behind the duo_cli_first_party_tools feature flag. With the flag on, Rails signs a verdict for the GitLab Duo CLI's first-party tool mcp__duo__review into the Duo Workflow token claim (tool_access_policies.first_party_tools). The Duo Workflow Service then applies it, so an admin can allow, ask for or deny the tool like any other governed tool. Without a rule the tool runs without an approval prompt.

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 · Feature flag lifecycle

What could go wrong?

The Duo Workflow Service identifies the first-party tool by its exact raw name, and only from clients that send x-gitlab-client-type: node-websocket and Language Server version 9.33.0 or later: the first release that reserves the duo MCP server name. These are client-sent headers, so a modified client can still claim the name. The governance owners sign off on that trade-off in https://gitlab.com/gitlab-org/gitlab/-/issues/630456. Clients older than 9.33.0 keep today's behaviour: they prompt.

Acceptance criteria before rollout

  • Governance sign-off on https://gitlab.com/gitlab-org/gitlab/-/issues/630456.
  • ai-assist!7500 is deployed to every Duo Workflow Service the flag reaches. It is safe in either order: Rails copies only deny into the claim lists, so an older service drops a denied tool and prompts for the rest.
  • The flag is checked against the root group, so it can be enabled per top-level group.
  • Stored rules apply whether or not local tool governance is on for the namespace.

Events

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 in #production and cross-post the results to the team channel. Background: incremental rollout process, feature actors.

Non-production

/chatops gitlab run feature set duo_cli_first_party_tools 50 --actors --dev --pre --staging --staging-ref
/chatops gitlab run feature set duo_cli_first_party_tools true --dev --pre --staging --staging-ref

Production — the flag is checked against the root group, so target groups first:

/chatops gitlab run feature set --group=gitlab-org,gitlab-com duo_cli_first_party_tools true

Then percentage rollout (wait ≥15 min between steps, watch dashboards):

/chatops gitlab run feature set duo_cli_first_party_tools <percentage> --actors

Before global rollout

Confirm the relevant gotchas before going to 100% — see enabling a feature for GitLab.com:

Cleanup

Remove the flag once deemed stable — see cleaning up. 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_cli_first_party_tools --dev --pre --staging --staging-ref --production

Rollback

/chatops gitlab run feature set duo_cli_first_party_tools false                                         # production
/chatops gitlab run feature set duo_cli_first_party_tools false --dev --pre --staging --staging-ref     # non-production
/chatops gitlab run feature delete duo_cli_first_party_tools --dev --pre --staging --staging-ref --production  # remove entirely