## Problem to solve The Web UI currently uses the `chat` flow for all Duo Chat conversations. As part of migrating to the Flow Registry, we need to enable the Web UI to use the `agentic_chat/v1` flow instead, controlled by a feature flag. ## Proposal Introduce a `agentic_chat_flow_registry_migration` feature flag that controls which flow the Web UI uses when starting a new conversation. **When the feature flag is enabled:** - The Web UI client sets `agentic_chat/v1` as the `workflowDefinition` field in the `startRequest` RPC call. - The flow configuration should follow the structure defined in [ai-assist !5328](https://gitlab.com/gitlab-org/modelops/applied-ml/code-suggestions/ai-assist/-/merge_requests/5328/diffs). **Compatibility constraint:** The `agentic_chat/v1` flow (Flow Registry) and the existing `chat` flow are **not compatible** due to structural differences in their LangGraph state (`FlowState` vs `ChatWorkflowState`). Because of this: - Clients must stick with the flow that was used when a conversation was created. - The feature flag change only takes effect when a user starts a **new** conversation (e.g., via the `/new` slash command). ## Implementation notes - Gate the `workflowDefinition` selection behind the `agentic_chat_flow_registry_migration` feature flag in the Web UI client. - Ensure no mid-conversation flow switching occurs; the selected flow must remain consistent for the lifetime of a conversation. - You need to register a new flow at `duo_workflow_service/agent_platform/v1/flows/configs/agentic_chat/1.0.0.yml` or somewhere. See [the PoC MR](https://gitlab.com/gitlab-org/modelops/applied-ml/code-suggestions/ai-assist/-/merge_requests/5328/diffs) about an example of configuration but the actual configuration could be different [according to the related issue's solutions](https://gitlab.com/groups/gitlab-org/-/work_items/21947). Make sure that users can have basic conversations as an exit criteria of [the epic](https://gitlab.com/groups/gitlab-org/-/work_items/21947).