Custom Models Planning 18.7

Milestone planning for the Custom Models Group

Milestone Information

  • Milestone: 18.7
  • Start date: 2025-11-15
  • End date: 2025-12-12

🎯 Milestone Summary

The main goals are to:

  1. Finalize the model selection implementation by cleaning up several feature flags
  2. Investigate and plan to support Self-Hosted models for Duo Agent Platform on GitLab Dedicated

We will also prioritize any newly identified work items that directly GA readiness for Duo Agent Platform.

Priority Projects

Priority Epic / Issue Teams in addition to Custom Models Goal for the milestone DRI/Staffing Status

priority1

Deliverable

Break out DAP feature setting to two - agentic ... (gitlab-org&19998 - closed)

Haiku is the default model for agentic chat / GitLab Duo Agent; Haiku is a selectable model for all other agents

DRI: @manojmj

workflowcomplete

priority1

Deliverable

https://gitlab.com/gitlab-org/gitlab/-/issues/581395+

Fulfilment, AI Framework Spike for 18.7 - work itself is due 18.8

DRI: @mhamda

Additional Staffing:

@cindy-halim

workflowcomplete

Tasks are broken down

The new SKU work is 80% complete, not much to change left, but we have to wait for fulfillment to provision the new SKU

priority1

Add support for exposing Duo Agent Platform ser... (gitlab-org/charts/ai-gateway-helm-chart#6 - closed)

Blocking customers using DAP

DRI: @jpcyiza

workflowcomplete

priority1

Duo Agent Platform GA Hard Blocker

https://gitlab.com/gitlab-org/gitlab/-/issues/582878+s

DRI: | @jessieay ,

@eduardobonet

Staffing @cindy-halim FE|

workflowin dev

priority1 Duo Agent Platform GA Hard Blocker

https://gitlab.com/gitlab-org/gitlab/-/work_items/583038+

DR: @julie_huang

workflowin review

priority2

Deliverable

Make model selection feature flags for .com and... (gitlab-org/gitlab#569140 - closed)

Resolve each action listed here

DRI: @mhamda

workflowcomplete Remove Beta in code but keep Beta in doc till 18.8

priority3

Cost indicator and description for model selector

DRI: @julie_huang

workflowin review

Want this feature to be behind FF agentic_chat that is the same flag that controls usage billing GA

priority3

Deliverable

Improve Quality of DAP features on Self-Hosted ... (gitlab-org&19986)

DRI: @aying-gl

Additional Staffing: @bcardoso-

workflowin dev

priority3

Deliverable

Data-driven prioritization for self-hosted models (gitlab-org&19862)

DRI: @bcardoso-

Additional Staffing: @aying-gl @jordanjanes

workflowin dev

Borrowed

Foundational Chat Agents: Consolidation (gitlab-org&19707) - FE

Governance

DRI: @cindy-halim @eduardobonet

workflowin review can start looking into SKU work

Borrowed

https://gitlab.com/gitlab-org/gitlab/-/issues/577516+

Duo Chat

UI Bugs - Duo Chat in AI Side Panel (gitlab-org&19613)

DRI: @julie_huang @dmishunov

workflowcomplete

Borrowed

SWE bench setup for issue to MR flow (gitlab-org/duo-workflow/testing/duo-workflow-tests#62)

DAP

DRI: @bcardoso-

priority3

Stretch

Support Duo for Personal Namespaces on Self-Man... (gitlab-org/gitlab#568942)

Duo supported in personal namespaces

DRI: @mhamda ?

priority4

Stretch

Spike: Duo Agent Platform Self-Hosted models fo... (gitlab-org/gitlab#580510)

Technical plan to support SH on Dedicated for DAP

DRI: @jpcyiza

priority4

Stretch

OAuth2 for AI Gateway Authentication to Azure O... (gitlab-org&17451)

Support OAuth2 integration

DRI: @jpcyiza

🐛 Priority Bugs

Issue Severity Priority DRI Status Notes

https://gitlab.com/gitlab-org/gitlab/-/issues/578756+

severity1

priority1

@cindy-halim

workflowin review

Security Issue

https://gitlab.com/gitlab-org/gitlab/-/issues/581268+

severity1

priority1

@mhamda

workflowin review

It's been a learning process and hoops to get through all the security pipeline checks.

Dec 8 -still blocked and contacting delivery team

Security Issue

Model Selection Not Respected for Ambient Flow ... (gitlab-org/gitlab#582678 - closed) • Manoj M J

severity1

priority1

@manojmj

workflowin review

Features moved to websocks and Custom Models was unware

User model selections are not staying persisted... (gitlab-org/gitlab#582136 - closed) • Julie Huang • 18.7

severity2

priority1

@julie_huang

workflowcomplete

Team Capacity

Planned Time Off

Note: Estimated Weight Capacity is (Working days in milestone - Total days off) / 2, rounded down.

Working days in milestone = 20

Team Member Role Total Days Off* Estimated Weight Capacity
Product Manager
@jordanjanes Product Manager 3 n/a
Engineering Manager
@aying-gl Engineering Manager 1 n/a
Engineers
@mhamda Senior Backend Engineer 0 7 (10-3 Work council working days)
@cindy-halim Fullstack Engineer 1 9
@julie_huang Frontend Engineer 0 10
@manojmj Backend Engineer 0 10
@bcardoso- ML Engineer 7 13 days
Note: Total Days Off includes all types of leave (e.g., vacation, public holidays, family & friends time, conferences, personal time, etc.)

Quality Capacity Allocation

  • Capacity for support:
  • Capacity for bugs:
  • Capacity for maintenance:

Milestone Deliverables

Deliverable Issues

---
display: table
fields: title, epic, weight, assignee
limit: 100
---
label="group::custom models" AND label="Deliverable" AND milestone="18.7" AND group="gitlab-org"

Stretch Issues

---
display: table
fields: title, epic, weight, assignee
limit: 100
---
label="group::custom models" AND label="Stretch" AND milestone="18.7" AND group="gitlab-org"

typebug Issues

---
display: table
fields: title, epic, labels("priority::*") AS "Priority", status, weight, assignee
limit: 100
---
label="group::custom models" AND label="type::bug" AND milestone="18.7" and group="gitlab-org"

~"support::request-for-help" Issues

---
display: table
fields: title, labels("priority::*") AS "Priority", status, weight, assignee
limit: 100
---
label="group::custom models" AND label="support::request-for-help" AND milestone="18.7" AND group="gitlab-com"

Planning and Build Boards

Milestone Checklist

Engineering Manager

  • Get team capacities and post them by the 10th of the month
  • Add proposed prioritized list of type::maintenance issues to the planning board
  • Obtain weights for all proposed issues
  • Collaborate with product manager to finalize the plan
  • Assign Deliverable and Stretch labels to milestone issues
  • Confirm DRIs and backup DRIs for all priority projects
  • Identify items for release post highlights

Product Manager

  • Define key themes for the milestone
  • Add prioritized list of type::feature issues to the planning board
  • Request weights from engineering where necessary
  • Collaborate with engineering to finalize the plan
  • Identify items for release post highlights
  • Update the Direction page
  • Sign off on final plan for the milestone
  • Close the planning issue

Stable Counterparts

  • Technical Writing: Confirm feature documentation with the Product or Engineering Manager.
  • Quality: Review testing requirements
  • UX: Confirm design support availability

(improve this template?)

Edited by Annie Ying