GitLab connects Claude Code to Duo agents with a single skill: 4 workflows from the terminal
If you write code in Claude Code, you don't have to switch to another interface to get automation. One skill (a ready-made set of instructions for an agent) configures a GitLab group and connects it via MCP, the standard protocol for linking an agent to a service. After that, you can tell Claude from the terminal to "take my issue," and a Duo agent in GitLab opens a merge request on its own. The long-running work happens on the GitLab side, and the code still goes through the usual reviews, pipelines and scans.
AI-processed from GitLab Blog; edited by Hamidun News
Many developers already work in a local AI agent such as Claude Code, Codex or Cursor, and don't want to move to another interface for the sake of automation. GitLab proposes a setup where you stay in your familiar terminal and send long tasks that need the context of the whole repository to GitLab Duo Agent Platform for execution. This is a GitLab platform where agents work directly inside a project using ready-made scenarios (GitLab calls them flows).
A skill, which is a pre-written set of instructions for an agent, and MCP, an open protocol through which an agent talks to an external service, connect the terminal to the platform. Picture an ordinary morning: an issue is assigned to you, and instead of opening a branch yourself, you type into Claude Code, "take issue number 1 and hand it to the Developer flow." After a while, a finished merge request shows up in your queue.
For those who already use GitLab and a local agent, this is a way to cut out routine work without giving up their usual tools.
In its examples, GitLab uses Claude Code because it is the tool the company's customers choose most often. The same setup works for other environments, including GitLab's own Duo CLI.
Setup with a single skill
Instead of manual configuration, GitLab released a skill called gitlab-duo-setup. You copy it into the ~/.claude/skills/ folder, then invoke it from the project directory with the /gitlab-duo-setup command. You can also put the skill in .claude/skills/ inside the repository so the whole team has it. There is a second skill, gitlab-mr-followup, which helps the local agent track the state of a merge request and take steps on your behalf.
Before making any changes, the skill reads the top-level group and its projects and presents a single plan: what will change and who will be affected. Group settings reach all projects and members, and the plan says so explicitly. You can remove any line. Once you approve, the skill:
- enables Duo Agent Platform and flow execution for the group, adding the Code Review, Duo Developer and Fix CI/CD Pipeline flows;
- enables automatic code review for the group, which applies to all projects;
- creates automation in every project with CI/CD that triggers Fix CI/CD Pipeline when a pipeline fails (projects that already have it are skipped, so running the skill again is safe);
- adds the GitLab MCP server to Claude Code and walks you through a browser login;
- verifies the result by calling list_duo_agents_and_flows.
You need a top-level group on GitLab.com with GitLab credits (Premium and Ultimate groups receive monthly promotional credits per user), a project with a pipeline, several issues and a couple of merge requests, and the Owner role on the group. With the Maintainer role, the skill configures only a single project and lists what to ask the owner for. You will also need Claude Code, git and the GitLab CLI (glab). If you get a 403 error after logging in, the group most likely has MCP client connections turned off: the owner enables "Allow connection to GitLab" in the group settings.
Four workflows from the terminal
Once connected, Claude Code can find your issues, launch flows, read review discussions and pipeline statuses, and reply in discussions over a single OAuth connection. Every call leaves an audit event for the platform team.
- Hand an issue to the Developer flow. The agent lists the issues assigned to you, you pick one, and Claude starts a Duo session with a link to it. From there, the work runs not on your computer but in a CI job on a runner: the flow reads the issue and the repository, writes the changes and opens a merge request. The merge request is created under your name, not a service account, and lands in your review queue. The clearer the task description, the better the result.
- Automatic review of every merge request, working through comments without leaving the terminal, and resolving merge conflicts.
- Automatic fixing of a failed pipeline.
- Triage and fixing of security findings; this workflow is available only in GitLab Ultimate.
What this means in practice
GitLab's main argument is that the agent does not create a workaround. Every merge request still goes through the same reviews, pipelines, scans and approval policies. The skill is also not tied to a single tool, so you can keep using it if you switch local agents.
There are limitations: you need GitLab credits, security requires Ultimate, and projects need runners that can execute flows. Group settings affect all members, so it is better to run the skill after agreeing with your team. If the GitLab server is connected but no tools appear, check /mcp and restart Claude Code. If tools show up twice because of connections at both the user and project level, keep one.
- Nov 20, 2026GitLab makes Duo Agent Platform credits last up to 2x longer
- Nov 20, 2026Anthropic Completes Record IPO: Raises $81.34 Billion at a $1.5 Trillion Valuation
- Nov 20, 2026Superhuman opens Go to 20 third-party agents as the assistant passes 1 million users
- Nov 20, 2026Anthropic raised $104.8 billion in its IPO, but its infrastructure commitments total $1 trillion
Key Questions Answered
What are the key details on Setup with a single skill?
Instead of manual configuration, GitLab released a skill called gitlab-duo-setup. You copy it into the ~/.claude/skills/ folder, then invoke it from the project directory with the /gitlab-duo-setup command. You can also put the skill in .claude/skills/ inside the repository so the whole team has it. There is a second skill, gitlab-mr-followup, which helps the local agent track the state of a merge request and take steps on your behalf.
What are the key details on Four workflows from the terminal?
Once connected, Claude Code can find your issues, launch flows, read review discussions and pipeline statuses, and reply in discussions over a single OAuth connection. Every call leaves an audit event for the platform team. Hand an issue to the Developer flow. The agent lists the issues assigned to you, you pick one, and Claude starts a Duo session with a link to it.
What this means in practice?
GitLab's main argument is that the agent does not create a workaround. Every merge request still goes through the same reviews, pipelines, scans and approval policies. The skill is also not tied to a single tool, so you can keep using it if you switch local agents. There are limitations: you need GitLab credits, security requires Ultimate, and projects need runners that can execute flows. Group settings affect all members, so it is better to run the skill after agreeing with your team.
Build & Ship Production AI Agents Without Boilerplate Code
Start your free 72-hour trial at Hamidun Academy (academy.hamidun.com) — interactive lessons on Claude Code & Cursor, live Tech Radar, and production agent templates.
The AI world, distilled — once a week
Seven stories that actually mattered, hand-picked. No noise, no reposts, no press releases.
Done! Check your inbox for a confirmation.