Foundational Agent Research, MR Reviews, and Task Planning

July 30, 2026 #gitlab

TL;DR

Did deep research on foundational agent creation (AI catalog vs. Duo Workflow Service methods) to respond to the Slack thread with Agent 3621, tagging Agent 6645, Agent 9437, and Agent 5552.
Left a thorough review comment on MR-246-884 (internal note indicator for email notifications) addressing Agent 2498’s StyleSheet claim before approving.
Outlined remaining tasks: two Fenwick Gigglesnort issues, Code Warrior training (due Aug 10), and the maintainer MR process (to ping Agent 2397, likely Tuesday).
Filed a new bug (607514) for a pagination issue in the VS Code chat interface, same root cause as the managed tab bug.
Had an idea to integrate voice notes on my phone with my local radar setup, though the approach isn’t worked out yet.

Foundational Agent Flow Registry Research

I need to respond to the Slack thread with Agent 3621 about the flow creation foundational agent — I’ve done the research and just need to organize my thoughts before replying. I’ll tag Agent 6645, and together with Agent 3621, Agent 9437, and Agent 5552, we should be able to map out a path forward that addresses the ambiguities still needing resolution for this milestone.

I dug into Agent 5552’s issue (number 1919, created Feb 17, 2026), which is essentially a checklist for moving the flow registry assistant AI catalog item (number 110, GitLab Project ‘flow registry chat helper’) into a foundational agent — a GitLab-maintained, platform-native agent available across gitlab.com, self-managed, and dedicated deployments.

There are two ways to create a foundational agent: the AI catalog method (preferred, user-friendly, testable) or directly in the Duo Workflow Service (DWS). For the AI catalog method: you make the agent public, note its ID, and open an MR to DWS’s Dockerfile using poetry (there’s a ‘poetry run fetch foundational agents’ script) with a root URL and GitLab API token — this bundles the agent with DWS across all deployment types. Currently only three foundational agents exist: Duo Planner (ID 348), Security Analyst, and CI Expert. Under the hood, foundational agents are actually flows.

After the Dockerfile MR, the agent needs to be made selectable by adding it to the foundational chat agents definitions Ruby file and updating the documentation (the ‘available foundational agents’ section) — ideally merging the documentation and Ruby file changes together.

For the DWS method: create a flow configuration file under duo_workflow_service/agent_platform/v1/flows/configs (in GDK’s gitlab-ai-gateway folder or the AI Assist repo directly), then open an MR. The same steps apply for updating the foundational chat agents definitions file and documentation. The key difference: when created via AI catalog, the version field in the definitions.rb file should be ’experimental’; when created via DWS, it should be ‘v1’ (lowercase).

I also found the foundational chat agents documentation, which stresses that these flows may expose secrets, so our flow creation agent should follow the same security/compliance/performance guidance.

I resolved a discrepancy about versioning: there’s a flow registry (schema) version — mapping to either the v1 or experimental folders under agent_platform — and a separate flow version, which is the semantic-versioned YAML filename (e.g., 1.0.0.yaml) inside flows/configs for a given agent.

Agent 5552’s original issue didn’t reference an MR — he closed it a month ago as a duplicate of Agent 9437’s issue, without producing the Dockerfile change or the definitions.rb update. Also missing from his issue: adding a feature flag gate to the Foundational Chat Agents Resolver (ee/app/graphql/resolvers/ai/foundational_chat_agents_resolver.rb) for controlled rollout. He did create a flow, though, so I should reach out to see how well-tested it was, compare it with Agent 9437’s proof-of-concept flow, and figure out which one Agent 6451 was testing.

MR-246-884: Internal Note Indicator

Working on MR-246-884 to add an internal note indicator to email notifications. I want to leave a comment addressing Agent 2498 (@Poffee21) — he (or Duo) claims the StyleSheet likely only serves the web renderer preview in the browser and not actual email clients, but I believe I’ve determined that’s incorrect. His style is probably fine either way, so I want to leave a thorough comment to build organizational knowledge before approving and passing it to another reviewer.

Remaining Tasks

Two issues to work on with Fenwick Gigglesnort. One more to do, and one to just polish off.

Training: I have until August 10th (about 10 days) to complete two modules of Code Warrior training, which requires actual code, so I should start today or tomorrow.

Maintainer MR: I need to open an MR to become a front-end maintainer on the GitLab project in the monolith. First I need to reread the maintainer documentation (can get a synopsis from Glean), then open the MR, then ping Agent 2397 — giving him a few days’ notice. Since it’s Thursday and I’m taking Monday off, I’ll probably ping him Tuesday, so I should get the reading and MR done today or tomorrow.

VS Code Chat Bug

Found a new bug in the VS Code chat interface — same as the pagination bug from the managed tab, where we try to fetch more than 20 items at a time because we’re fetching the group and project configuration pinned item versions. Created bug 607514 for it.

Personal Project Idea

I want to build an integration with my local radar setup on my phone — so I can send what I’m currently working on, or take voice notes on my phone. Not sure how to work that out yet.