doc/administration/gitlab_duo/configure/transition-to-the-agent-platform.md
{{< details >}}
{{< /details >}}
When you transition from GitLab Duo (non-agentic) to the Agent Platform, you get access to multiple assistants (called agents) throughout the software development lifecycle.
To transition your instance to the Agent Platform, complete the following steps:
The following table lists the GitLab Duo non-agentic features and the agentic version that your users can access after moving to the Agent Platform. For a complete list of features in the Agent Platform, see Generally available features and Beta and experimental features.
| Non-agentic feature | Agent Platform |
|---|---|
| GitLab Duo Non-Agentic Chat | Agentic Chat |
| Answer complex questions and autonomously create and edit files. Connects to the Planner and Security Analyst agents. Merge request summary, discussion summary, refactor code, and test generation are now part of Agentic Chat. | |
| GitLab Duo Code Review | Code Review Flow <sup>1</sup> |
| Automate code review tasks and enforce coding standards across your team. | |
| Root cause analysis | Fix CI/CD pipeline flow <sup>1</sup> |
| Diagnose and automatically fix failing CI/CD pipelines. | |
| Vulnerability explanation and resolution | SAST vulnerability resolution flow <sup>1</sup> |
| Automatically generate fixes and remediation steps for SAST vulnerabilities. |
Footnotes:
You must have GitLab 19.0 or later.
Unlike GitLab Duo (non-agentic), the Agent Platform runs flows on runners and uses service accounts to create commits and pipelines. This requires configuration requirements that non-agentic features did not have.
To set up your environment for the Agent Platform:
After you set up your environment, run the following diagnostic checks:
After you set up your environment, configure the following settings:
Before you roll out the Agent Platform to the majority of your users, ask a small group of users to confirm the following outcomes:
After these users have run some flows, you should also check the Credits Dashboard to confirm credit usage.
After you change your subscription from GitLab Duo Pro or Enterprise to usage billing, you are charged based on credit usage instead of seats.
To track your team's credit usage and to set usage caps, use the Credits Dashboard.
When you first transition your instance to the Agent Platform, you might encounter the following issues.
| Issue | Likely cause | Resolution |
|---|---|---|
| Flows not visible in the UI | GitLab Duo or flow execution is not turned on, the group lacks permission to use flows, or the flow is not enabled at the project level. | Flows not visible in the UI |
| Flows do not run because no runner picks up the job | No runner has the gitlab--duo tag, or runners are not configured for flows. | Configure runners |
Session is stuck in the created state | Push rules block the service account. The commit author email or the duo/feature/ branch prefix is not allowed. | Configure push rules to allow a service account |
Error in creating workload: Insufficient permissions to create a new pipeline | The foundational flow service account was set up before the imported or templated project existed. | Insufficient permissions to create a new pipeline for imported projects |
| A foundational flow is turned on but does nothing | The service account was not created, or a group membership lock prevents it from being added to projects. | Foundational flow service account not created and Group membership locked |
The Agent Platform is off, or Something went wrong while requesting a review from GitLab Duo | The user belongs to multiple GitLab Duo namespaces and no default namespace is set. | Default GitLab Duo namespace not set |
Your request was valid but Workflow failed to complete it | The repository has no commits, so the flow cannot find a default branch. | Error: Your request was valid but Workflow failed to complete it |
SSL certificate OpenSSL verify result: unable to get local issuer certificate (20) | On GitLab Self-Managed with a custom or self-signed CA, sandbox hardening blocks the runner's CA injection during git clone. | Error: SSL certificate OpenSSL verify result |
| All GitLab Duo features fail for all users immediately after transition | Silent Mode is turned on, which prevents GitLab from reaching the AI gateway. | Turn off Silent Mode |
| Health check network test fails, or GitLab Duo features are unavailable after transition | Outbound HTTPS to cloud.gitlab.com, customers.gitlab.com, or duo-workflow-svc.runway.gitlab.net is blocked by a firewall or proxy. | Allow outbound connections from the GitLab instance to GitLab Duo |
| Agent Platform features unavailable for all users right after conversion | Usage billing terms have not been accepted, or there are no credits available in the pool. | On-Demand credits |