Rename Workflow Catalog team to AI Catalog

| [Editor Extensions: Multi-Platform](/handbook/engineering/ai/editor-extensions-multi-platform/) | <ul><li>[JetBrains](https://gitlab.com/gitlab-org/editor-extensions/gitlab-jetbrains-plugin), [Neovim](https://gitlab.com/gitlab-org/editor-extensions/gitlab.vim) & [Visual Studio](https://gitlab.com/gitlab-org/editor-extensions/gitlab-visual-studio-extension) editor extensions</li> <li>Co-owns [Language Server](https://gitlab.com/gitlab-org/editor-extensions/gitlab-lsp) with [Editor Extensions: VS Code](/handbook/engineering/ai/editor-extensions-vscode/) </li><li>Duo CLI (Ideation/MVC phase)</li></ul>  |

| [Global Search](/handbook/engineering/ai/search/) | Abstraction Layer / Vector Storage / Semantic |

| [Infrastructure Platforms - Runway](/handbook/engineering/infrastructure-platforms/gitlab-delivery/runway/) | AI Gateway Scalability / Runway infrastructure |

| [Workflow Catalog](/handbook/engineering/ai/workflow-catalog) | AI Catalog / Custom Agents / Custom Flows |

| [AI Catalog](/handbook/engineering/ai/ai-catalog/) | AI Catalog / Custom Agents / Custom Flows |

## Counterparts

---

title: Workflow Catalog Group

description: "The Workflow Catalog Group is focused on developing Workflow Catalog, a catalog of Agents, tools, and flows that can be created, curated, and shared across organizations, groups, and projects."

title: AI Catalog Group

description: "The AI Catalog Group is focused on developing AI Catalog, a catalog of Agents, tools, and flows that can be created, curated, and shared across organizations, groups, and projects."

---

## Vision

The Workflow Catalog Group is focused on developing Workflow Catalog, a catalog of Agents, tools, and flows that can be created, curated, and shared across organizations, groups, and projects.

The AI Catalog Group is focused on developing AI Catalog, a catalog of Agents, tools, and flows that can be created, curated, and shared across organizations, groups, and projects.

## Team members

## How to reach us

Depending on the context here are the most appropriate ways to reach out to the Workflow Catalog group:

Depending on the context here are the most appropriate ways to reach out to the AI Catalog group:

* Slack Channel: `#g_workflow_catalog`

* GitLab group `@gitlab-org/ai-powered/workflow-catalog/engineering` (just engineers)

* Slack Channel: `#g_ai_catalog`

* GitLab group `@gitlab-org/ai-powered/ai-catalog/engineering` (just engineers)

## What we're working on

Right now, we're working on the first iteration of the Workflow Catalog (the MVP).

You can track this work in the [MVP epic](https://gitlab.com/groups/gitlab-org/-/epics/17989).

TBD

## How we work

* [Root Epic](https://gitlab.com/groups/gitlab-org/-/epics/11111): For grouping all the work and setting out a roadmap

* [Issue board](https://gitlab.com/groups/gitlab-org/-/boards/3871464): For all in-flight issues

* [Team tasks](https://gitlab.com/gitlab-org/ai-powered/workflow-catalog/team-tasks/-/issues): For all non-product related team issues

* [Async updates](https://gitlab.com/gitlab-org/ai-powered/workflow-catalog/team-tasks/-/issues/?label_name%5B%5D=async%20update)

* [Team Wiki](https://gitlab.com/gitlab-org/ai-powered/workflow-catalog/team-tasks/-/wikis/home): For product decisions and useful information

* [Team tasks](https://gitlab.com/gitlab-org/ai-powered/ai-catalog/team-tasks/-/issues): For all non-product related team issues

* [Async updates](https://gitlab.com/gitlab-org/ai-powered/ai-catalog/team-tasks/-/issues/?label_name%5B%5D=async%20update)

* [Team Wiki](https://gitlab.com/gitlab-org/ai-powered/ai-catalog/team-tasks/-/wikis/home): For product decisions and useful information

### DRIs

Each milestone, we assign a new goalkeeper and open a goalkeeping issue.

You can find more information in the [issue template](https://gitlab.com/gitlab-org/ai-powered/workflow-catalog/team-tasks/-/blob/main/.gitlab/issue_templates/goalkeeper.md).

You can find more information in the [issue template](https://gitlab.com/gitlab-org/ai-powered/ai-catalog/team-tasks/-/blob/main/.gitlab/issue_templates/goalkeeper.md).

### Communication

The Workflow Catalog Team communicates based on the following guidelines:

The AI Catalog Team communicates based on the following guidelines:

* Always prefer async communication over sync meetings.

* Don't shy away from arranging a [sync call](/handbook/communication/#video-calls) when async is proving inefficient, however always record it to share with team members.

* By default communicate in the open.

* Prefer public channels (`#g_workflow_catalog`) over private message for work-related Slack messaging.

* Prefer public channels (`#g_ai_catalog`) over private message for work-related Slack messaging.

### Frontend-Backend collaboration

  using mock data, mock endpoints, or API stubs that match the agreed schema. The backend can

  focus on implementing the data model, business logic, and actual API schema.

* **Maintaining alignment**: We value great communication. When requirements or schema need to change, we communicate

  early through the relevant GitLab issue or in [`#g_workflow_catalog`](https://gitlab.enterprise.slack.com/archives/C08T5J1KXKQ)

  early through the relevant GitLab issue or in [`#g_ai_catalog`](https://gitlab.enterprise.slack.com/archives/C08T5J1KXKQ)

  so our frontend or backend counterparts stay informed of all changes and can provide feedback early to avoid late-stage blockers.

### AI stage collaboration

The Workflow Catalog relies on the

The AI Catalog relies on the

[Workflow Service](https://gitlab.com/gitlab-org/modelops/applied-ml/code-suggestions/ai-assist/-/tree/main/duo_workflow_service?ref_type=heads)

as a foundational backend service.

Most Workflow Catalog features require new capabilities to be developed within Workflow Service,

Most AI Catalog features require new capabilities to be developed within Workflow Service,

which means our engineers will need to contribute directly to that codebase in partnership with the

[Agent Foundations team](../agent-foundations/_index.md).

**During the milestone:**

* If a `~Deliverable` issue becomes blocked or cannot be completed, communicate this early in `#g_workflow_catalog` or the relevant issue

* If a `~Deliverable` issue becomes blocked or cannot be completed, communicate this early in `#g_ai_catalog` or the relevant issue

* The Engineering Manager may adjust `~Deliverable` labels during the milestone based on changing priorities or capacity

### Our tech stack

## Team meetings

### Workflow Catalog: Group meeting

### AI Catalog: Group meeting

* **Time**: Every Tuesday, alternating weekly between 05:30 UTC and 15:00 UTC.

* **Purpose**: This meeting serves as a general sync meeting to bring up any current issues and blockers.

1. Customer-facing DSL implementation. This blueprint involves building an internal YAML-based DSL for scalable Flow implementation in the AI Gateway.

   Please note this DSL is entirely internal and improves our existing AI stack. Building a customer-facing DSL that

   customers may use for building their own custom Flows is out of scope for this blueprint. However, the work done

   in this proposal can be reused by the Duo Workflow Catalog team to further extend its functionality for customers.

   in this proposal can be reused by the AI Catalog team to further extend its functionality for customers.

## Implementation details

## Future evolution

Implementing customer-facing DSL might be considered as the next step.

This work will require additional effort and collaboration with the Duo Workflow Catalog team.

This work will require additional effort and collaboration with the AI Catalog team.

## Problem Statement

The workflow catalog backend architecture has evolved incrementally to support (see [glossary](https://docs.gitlab.com/development/ai_features/glossary/#agent-types)):

The AI catalog backend architecture has evolved incrementally to support (see [glossary](https://docs.gitlab.com/development/ai_features/glossary/#agent-types)):

- Custom agents

- Custom flows

### Exploring this design

Whilst not connected to this domain (notifications), this architectural design proposition was explored by

[the Workflow Catalog group](/handbook/engineering/ai/workflow-catalog/)

[the AI Catalog group](/handbook/engineering/ai/ai-catalog/)

in [merge request 194032](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/194032).

Rather than the [notification creation service](#notification-creation-service) proposed above,