Add agentic_chat_flow_registry_migration feature flag

Shinya Maedarequested to merge
duo/feature/599430-agentic-chat-flow-registry-migration into master

What does this MR do and why?

Introduces the agentic_chat_flow_registry_migration WIP feature flag to control which flow the Web UI uses when starting a new Duo Chat conversation.

When enabled: the startRequest RPC call includes flowConfigId: 'agentic_chat', flowVersion: '1.0.0', and flowConfigSchemaVersion: 'v1' — routing the conversation through the flow registry. See gitlab-org/modelops/applied-ml/code-suggestions/ai-assist!5748 (merged) for more information.

When disabled (default): existing behaviour is preserved; no flowConfig is set.

Compatibility: when a foundational agent (agentConfig) is selected, flowConfig is set to null regardless of the flag.

Note that this FF is still WIP that we will not rollout on production until phase 1 and future phases are done.

References

How to set up and validate locally

  1. Enable the flag: 
    Feature.enable(:agentic_chat_flow_registry_migration)
  2. Open Duo Chat and start a new conversation.
  3. Verify the start request includes flowConfigId: 'agentic_chat', flowVersion: '1.0.0', flowConfigSchemaVersion: 'v1'.
  4. Disable the flag and confirm no flowConfig fields are sent.

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Shinya Maeda

Merge request reports