Agentic Chat fails in VS Code Workflow v6.47.0 on Gitlab 18.4.1 due to missing aiCatalogConfiguredItems (rename mismatch)

Summary

VS Code GitLab Workflow extension v6.47.0 fails to load Duo Agentic Chat against a GitLab EE 18.4.1 instance due to a GraphQL schema rename mismatch.

The extension queries the renamed field aiCatalogConfiguredItems, but 18.4.1 exposes the older aiCatalogItems. As a result, the Agentic Chat panel shows an error and cannot list configured agents.

Steps to reproduce

1. On GitLab EE 18.4.1 instance
2. Use VS Code 1.104.2 with GitLab Workflow v6.47.0.
3. Open a project/MR and launch Duo Agentic Chat from the GitLab panel/command palette.
4. Observe that the Agentic Chat panel shows a schema error and does not populate available agents.

Example Project

Reproducible on any 18.4.1 instance with a configured Duo Agent.An example internal issue here

What is the current bug behavior?

Agentic Chat panel displays a GraphQL schema error:

Error: Field 'aiCatalogConfiguredItems' doesn't exist on type 'Query' (Did you mean aiCatalogItems?)
Variable $projectId is declared by getConfiguredAgents but not used
Variable $groupId is declared by getConfiguredAgents but not used

What is the expected correct behavior?

• The extension should be backward compatible with older server schemas (e.g., 18.4.1).
• If aiCatalogConfiguredItems (or the “item consumers” query) is absent, the extension should fallback to querying aiCatalogItems (with itemType: AGENT) and proceed without surfacing an error to the user.

Relevant logs and/or screenshots

VS Code GitLab Workflow output / DevTools console shows:

GraphQL request "getConfiguredAgents" failed:
Field 'aiCatalogConfiguredItems' doesn't exist on type 'Query' (Did you mean aiCatalogItems?)

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)
(we will only investigate if the tests are passing)

Possible fixes

Patch release information for backports

If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.

Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.

High-severity bug remediation

To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.