## Problem With the changes from https://gitlab.com/groups/gitlab-org/-/work_items/18785+ the Duo Developer setup of prompts and available tools is probably better suited to local development tasks than the more generic Agentic Chat flow, that is used both by IDE extensions and the Duo CLI for interactive sessions of users. The fact that we use two completely different flow setups (Python for Agentic Chat, Flow Registry for Duo Developer), makes it harder to just re-use the same Duo developer setup across both. Duo CLI can run any flow today in [headless mode](https://gitlab.com/groups/gitlab-org/-/work_items/18785) (e.g. one-shot without human interaction) but technical restrictions do keep us from running these flows also interactively. ## Desired Outcome Duo Developer can be run interactively in Duo CLI with the same level of security, UX polish as Agentic Chat today. This includes: 1. Tool approval 2. Streaming 3. Asking user questions / soliciting interactive feedback.