Duo Agent Platform - 10/8 to 06/09 - Iterations Overview

Note: This overview issue spans two iterations due to multiple people being on PTO in August.

Overview

This iteration is split in two:

Until code-freeze for 18.3:

Priority is on making Issue-to-MR v0 (&18781 - closed) available to customers. Special priority on any related work that needs to happen in the GitLab instance.

Towards 18.4:

Our main target is to make the flow registry a total success. We should do this in multiple ways:

1. Actually improve the capabilities of the registry
2. Evangelize usage of the registry
3. Implement awesome flows based on the registry.

Main Goals

1. Evolve the Flow/Agent DSL to make it cover more use-cases
2. [Convert Issue to MR to the flow registry and enhance its capabilities](
   1. &18784)
3. Convert the "fix pipeline" flow to flow registry and into something we can release
4. Add @assignment / mention triggering for flows.
5. Enhance remote flows with ability to run command in a provided environment + MCP
   1. Use a suitable environment for a coding agent (&18306 - closed)
   2. Add MCP support for GitLab provided servers in ... (gitlab-org/duo-workflow/duo-workflow-executor#78 - closed)
6. Rework the session page towards the design vision
7. Improve our evaluation setup:
   1. SWE bench setup for issue to MR flow (gitlab-org/duo-workflow/testing/duo-workflow-tests#62)
   2. Implement Tool Routing Evaluation Framework (gitlab-org/modelops/applied-ml/code-suggestions/ai-assist#1327 - closed)

Deliverable issues

---
display: table
fields: title, epic, status, assignee
limit: 100
---
label="group::duo workflow" AND label="Deliverable" AND iteration=2622427 and group="gitlab-org"

Stretch issues

---
display: table
fields: title, epic, status, assignee
limit: 100
---
label="group::duo workflow" AND label="Stretch" AND iteration=2622427 and group="gitlab-org"