Skip to content

GitLab Duo: AI features, Agent Platform and plans

GitLab Duo is the set of AI features built into GitLab. Because GitLab covers planning, code, CI/CD and security in one product, Duo can work with more than the file you are editing: it can read an issue, open a merge request, review it, explain why a pipeline failed and propose a fix. GitLab groups the features into two families. The GitLab Duo Agent Platform provides agentic features: agents and flows that work through multi-step tasks. GitLab Duo (non-agentic) features help with one specific task, such as completing code, reviewing a merge request or explaining a vulnerability.

This page explains both families, what you need to use them, and how to use them safely, with examples from an invented OrdersPortal project. It was checked against the GitLab documentation source for GitLab 19.x in November 2026; Duo changes every month, so check the feature tables in the official docs for the version your instance runs.

Topic Answers
Agent Platform features Agentic Chat, Code Suggestions and flows that open MRs, review code and fix pipelines.
Non-agentic features Code Review, Root Cause Analysis, test generation and other single-task helpers.
Add-ons and credits Duo Core, Pro and Enterprise, and usage-based GitLab Credits.
Using GitLab Duo safely Turning features on, reviewing output and protecting data.

The GitLab Duo Agent Platform has been generally available since GitLab 18.8. It is available on GitLab.com, Self-Managed and Dedicated for Premium and Ultimate, and on the Free tier with purchased GitLab Credits; generally available features consume credits when used. You can use it in the GitLab UI and through the editor extensions (VS Code, JetBrains IDEs, Visual Studio and others) once you have a project in a group namespace and the Developer role or higher.

Generally available features in all three tiers include:

  • Agentic Chat: answers complex questions about your projects and can create and edit files.
  • Code Suggestions: completions and code generation as you type in the IDE. Tab accepts, Ctrl+Right Arrow (Cmd+Right Arrow) accepts part of a suggestion, Esc rejects, and in VS Code Alt+] and Alt+[ cycle alternatives.
  • Developer Flow: turns an issue into a merge request.
  • Code Review Flow: reviews merge requests and enforces your team’s review instructions. Ask for it by mentioning @GitLabDuo or adding GitLab Duo as a reviewer.
  • Fix CI/CD Pipeline Flow: diagnoses a failing pipeline and proposes a fix.
  • Convert to GitLab CI/CD Flow: converts pipelines from other CI systems.
  • Custom agents and flows, an MCP server for connecting AI tools to GitLab, and MCP clients so Duo can use external tools.

Premium and Ultimate add features such as resolving merge conflicts (GitLab Duo edits the conflicting files and pushes a resolution commit, generally available in 19.3), resolving review discussions and Recommend Reviewers. Ultimate adds security flows, such as SAST vulnerability resolution and false positive detection.

An example request in Agentic Chat:

In orders/orders-portal, the pipeline for MR !482 fails in the "integration-tests" job.
Explain the root cause from the job log, propose the smallest fix,
and do not change the test expectations in tests/refunds.

Pitfalls:

  • Agents act with your permissions. A flow that can push and open merge requests should go through the same protected branches, approval rules and pipelines as human changes.
  • Credits are consumed per action. Long agent sessions and large contexts cost more; set budgets and watch usage for the top-level group.

These features require Premium or Ultimate and the GitLab Duo Pro or GitLab Duo Enterprise add-on (or GitLab Duo with Amazon Q on Self-Managed). They are billed by add-on seat, not by credits. With Duo Pro you get Code Suggestions, non-agentic Chat, and in the IDE: Code Explanation, Refactor Code, Fix Code and Test Generation, plus Code Explanation in the GitLab UI. Duo Enterprise adds:

  • GitLab Duo Code Review: an initial AI review of a merge request (the non-agentic version; depending on add-ons and settings, GitLab may run the agentic Code Review Flow instead).
  • Root Cause Analysis: explains why a CI/CD job failed.
  • Vulnerability Explanation and Vulnerability Resolution: explain a vulnerability and propose a merge request that fixes it.
  • Discussion Summary and Merge Commit Message Generation.

Merge request summaries, code review summaries and issue description generation are in beta or experiment status for Duo Enterprise.

A test generation prompt in the IDE, with the pricing function selected:

/tests Generate Jest tests for calculateRefund(order, lines).
Cover: full refund, partial refund of one line, a refund above the paid amount (must throw),
and an order paid with a discount code. Use the existing buildOrder() helper.

Pitfalls:

  • Two code review features exist. Which one runs depends on the add-on and group settings; check which one your group uses before writing review instructions.
  • Generated tests confirm the code, not the requirement. State the expected behavior in the prompt and review the assertions.

Three add-ons extend Premium and Ultimate. GitLab Duo Core is included automatically with Premium and Ultimate on GitLab 18.0 and later (existing customers from 17.11 or earlier must turn it on). Since GitLab 19.0 (May 2026), Duo Core users use the Agent Platform (Agentic Chat, agents, flows and Code Suggestions) with GitLab Credits instead of non-agentic Chat. GitLab Duo Pro and GitLab Duo Enterprise are paid seat-based add-ons for the non-agentic features above and do not consume credits.

GitLab Credits are the usage-based currency for the Agent Platform and some other features. Credits are billed at the top-level group or root namespace, not per project, and come as included credits, a monthly commitment pool, or on-demand credits. For prices and the credits each model and feature consumes, see GitLab’s pricing page and the credit multiplier tables in the docs.

You have You can use
Free tier Agent Platform features available on Free, with purchased GitLab Credits
Premium or Ultimate (Duo Core included) Agent Platform features for your tier, consuming GitLab Credits
Plus Duo Pro Non-agentic Code Suggestions, Chat and IDE helpers, per seat
Plus Duo Enterprise Duo Pro features plus Code Review, Root Cause Analysis, vulnerability features, per seat

Pitfalls:

  • Self-Managed needs configuration. Instances must be connected to the GitLab AI Gateway (or run GitLab Duo Self-Hosted with your own models); offline licenses cannot use Duo Core.
  • Version matters. Many features need GitLab 18.8 or later; behavior on older instances may differ from GitLab.com.

Administrators turn GitLab Duo on or off for an instance, a top-level group, subgroups and projects, and separately turn the Agent Platform on (GitLab 18.8 and later) and beta or experimental features. Start with a pilot group, define which projects may use Duo, and document what data may be shared with AI features. Self-Managed customers who cannot send code to external model providers can use GitLab Duo Self-Hosted with models they host.

Treat Duo’s output like a contribution from a new team member. Review every suggestion, run the pipeline, and keep security scanning and approval rules in place for AI-generated merge requests. Write review and coding instructions for your repositories so agents follow your conventions, and use the AI audit events to see what agents did.

Pitfalls:

  • “The AI reviewed it” is not an approval. Duo Code Review comments are input; required approvals must still come from people listed in approval rules or CODEOWNERS.
  • Prompt injection is real. Agents read issues, comments and files that anyone can write. Keep agent permissions minimal and review what they change; GitLab documents these security threats for the Agent Platform.
Need Start with
Completions while typing Code Suggestions
Questions about code, issues or pipelines Agentic Chat
Turn an issue into a merge request Developer Flow
First-pass review of every MR Code Review Flow (or Duo Code Review with Enterprise)
A failing pipeline Fix CI/CD Pipeline Flow or Root Cause Analysis
Vulnerability triage Vulnerability Explanation and Resolution, or Ultimate security flows

What is the difference between the GitLab Duo Agent Platform and non-agentic GitLab Duo features? The Agent Platform runs agents and flows that work through multi-step tasks (chatting, editing files, opening and reviewing merge requests, fixing pipelines) and is billed with GitLab Credits. Non-agentic features each help with one task, such as Code Suggestions or Root Cause Analysis, and are billed through the Duo Pro or Enterprise seat add-ons.

What does GitLab Duo Core include? It is included with Premium and Ultimate on GitLab 18.0 and later. Since GitLab 19.0 it gives access to the Agent Platform features, including Agentic Chat and Code Suggestions, which consume GitLab Credits.

How do you get an AI review of a merge request? Mention @GitLabDuo or add GitLab Duo as a reviewer, which starts the Code Review Flow; with Duo Enterprise and the matching settings, the non-agentic GitLab Duo Code Review may run instead. Either way it adds comments; human approvals are still required.

Senior scenario: security asks how you will prevent an agent from merging unsafe code into main. What is your answer? Agents get no special path: main is protected with push set to No one, approval rules and Code Owner approval are required, and pipelines with SAST, secret detection and dependency scanning must pass. Agents run with the permissions of the user or service account that triggered them, so keep those minimal; turn on the Agent Platform only for a pilot group first, review the AI audit events, and add repository instructions that define the coding and review standards agents must follow.