Cant message custom agents in agentic mode git lab duo

Problem to solve

I am trying to use the GitLab Duo Agent Platform (custom agents), but every request fails.

What I am seeing:

When I try to use any custom agent I create, it immediately fails with the generic error:

There was an error processing your request in the Duo Agent Platform, please try again or contact support if the issue persists.

What I expect to see:

I expect the custom agent to execute its flow and provide a response.

Crucial Detail: The normal GitLab Duo Chat works perfectly fine. If I just message the default “Duo Agent” (not a custom agent), it answers my questions, explains code, etc. The error only happens with custom agents.

Most Important Detail: I am experiencing this identical failure on both my self-managed instance AND on my GitLab .com account.

Steps to reproduce

  1. In any project, open the GitLab Duo Chat window in the Web UI.

  2. click the chat icon a top the screen to list available agents.

  3. Select any custom-made agent (e.g., my_agent).

  4. Send any prompt.

  5. Result: The agent immediately returns the “error processing your request” message.

  6. (For comparison) Select the default “Duo Agent” from the list.

  7. Send any prompt.

  8. Result: The default agent works correctly and returns a valid answer.

Configuration

Self-Managed Instance

My self-managed instance configuration is all green:

  • I have applied an Ultimate license with an active Duo Enterprise trial.

  • I have manually assigned my user account a Duo Enterprise seat in Admin Area > GitLab Duo.

  • I am testing in a project that is inside a Group namespace.

  • The Admin Area > GitLab Duo > Health Check passes all probes 100% (Network, License, Token, and End-to-end).

Here is the part of the full (and successful) health check report:

JSON

[
  {
    "name": "license_probe",
    "success": true,
    "message": "Subscription can be synchronized.",
    "details": {
      ...
      "add_on_products": {
        "duo_core": [ { "quantity": 50, ... "trial": false } ],
        "duo_enterprise": [ { "quantity": 100, ... "trial": true } ]
      }
    }
  },
  {
    "name": "host_probe",
    "success": true,
    "message": "customers.gitlab.com reachable."
  },
  {
    "name": "host_probe",
    "success": true,
    "message": "cloud.gitlab.com reachable."
  },
  {
    "name": "access_probe",
    "success": true,
    "message": "Subscription synchronized successfully."
  },
  {
    "name": "token_probe",
    "success": true,
    "message": "Access credentials are valid."
  },
  {
    "name": "end_to_end_probe",
    "success": true,
    "message": "Authentication with the AI gateway services succeeded."
  }
]

IDE Configuration

This is the most important part: I am not using an IDE.

I am not using VS Code or a JetBrains IDE. I am trying to run the custom agents directly from the GitLab Web UI.

I have seen the troubleshooting docs that mention switching from gRPC to WebSocket in the IDE settings, but I cannot apply this fix because I am not using an IDE.

Versions

  • Self-managed

  • GitLab .com SaaS

Which GitLab Duo feature is involved:

GitLab Duo Agent Platform (Custom Agents)

Versions:

  • GitLab Self-Managed: 18.5.1-ee

  • GitLab .com SaaS: 18.5 (Latest)

  • IDE: N/A (Using the GitLab Web Interface)

(note: gitlab. com has space because not allowed to post links)

Thanks for the feedback. Mind opening a support ticket so that teams can investigate your account?

Thank you! I actually already have an official support ticket open for this issue. The ticket number is 667745

​I’ve included the full details there, including the successful health check from my self-managed instance and the fact that the error also happens on GitLab .com including screenshots.

​Thanks for looking into it!

1 Like

Update:

Despite having an ultimate subscription on My self managed instance account I received this: Hello,

You have opened this ticket through our paid support channel and we were unable to automatically determine whether you have a subscription to GitLab .com or a license to a self-managed GitLab installation because your user record is not associated with any organization.

If you hold a subscription or a paid license and would like to be added as a named contact within your organization, please refer to our documentation on how you can Prove your support entitlement and submit a Support Ops ticket with the required information. Once we have everything connected, our team will assist you with getting set up for support.

If you do not have a GitLab. com subscription, a self-managed license, or are on a trial, be aware that only community support is included; consider searching for and posting your question in our community forum. For reproducible issues, please search for and if none exists, file a bug issue in the Gitlab project.

For all other matters, we have listed some common places you might go:

For a reproducible issue or feature request, please search for an existing issue or open an issue on the related project, such as on the main GitLab project.

To report a potential vulnerability, please utilize our HackerOne Bug Bounty process. Alternatively, you may create an issue following the instructions in our security handbook.

To report abuse on GitLab .com, please utilize the ‘Report Abuse’ button while logged into your GitLab .com account and be sure to include any relevant details pertaining to your report in the text field. You can also submit more detailed reports via email to abuse@gitlab. com.

To stay updated on GitLab. com Availability, follow our status page.

This ticket will now be closed. If you believe this was received in error, please consider contacting your sales representative or account manager for further assistance.

Best regards,

GitLab Support

Update 2

Turns out unpaid license don’t allow you to post support request but now I have an issue id: 723

If you have a license then they should accept the ticket. However it would require opening the ticket with the email address/account of the person who purchased that subscription. But yes, if you are a free user or subscription has expired, then no you cannot open a ticket.

Is your organization part of the Open Source, Education or Startup programs? These subscriptions do not include paid support.

yes its education program that’s why i am using the open source support now(issue id: 723)

just wondering about something could the Microsoft azure outage be the reason??

Hi @al_ariefy ! I’m part of the DevRel programs team and I can confirm that we have received issue 723. I have sent a note for the team, as the queue for Education and Open Source are different ones (you can also contact us through education@gitlab.com or opensource@gitlab.com respectively). Please note that it might take a few days to receive a reply. Thank you!

2 Likes

Thanks all! We appreciate the bug report and this has been fixed. For transparency to anyone coming across the forum post, this bug was fixed within this refactor: refactor: use LocalPromptRegistry for prompt template overrides (!3748) · Merge requests · GitLab.org / ModelOps / AI Assisted (formerly Applied ML) / Code Suggestions / AI Gateway · GitLab

1 Like