GitLab 19.5

19.5

GitLab 19.5 release notes

Added 11
  • GitLab MCP server is generally available, giving MCP-compatible agents direct access to the expanded GitLab tool catalog and GitLab Duo Agent Platform agents and flows
  • GitLab Secrets Manager is generally available on GitLab.com and GitLab Self-Managed, built on OpenBao and using existing group and project permissions
  • Each CI secret in GitLab Secrets Manager can be scoped to the job that needs it based on environment, branch, and branch protection rules
  • Audit logs are generated for every create, read, update, and delete operation in GitLab Secrets Manager
  • Externally Connected Agents such as Claude Code, Cursor, and Codex can be connected to GitLab AI Governance using the GitLab CLI after a one-time glab govern setup (beta)
  • Externally Connected Agent sessions are captured in the AI Governance Dashboard and AI audit events report, and audit events flow to SIEM through audit event streaming
Changed 2
  • Restrict access based on group membership for GitLab Duo now accepts any subgroup, not just top-level groups, so direct members of the selected subgroup receive access
  • The Run suggested prompts as /goal sessions setting in GitLab Duo CLI runs suggested prompts as /goal sessions instead of chat messages

From GitLab

On October 15, 2026, GitLab 19.5 was released with the following features. We are excited to recognize Dhairya, a Level 3 contributor, as this month’s Notable Contributor! Dhairya contributed to offline transfer and Organizations support for import, so that groups, projects, and their memberships can move between GitLab instances.

Primary features
GitLab MCP server is generally available
  • Tier: Free, Premium, Ultimate
  • Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
  • Links: Documentation · Related Issue In previous versions of GitLab, MCP clients could reach only a limited set of GitLab tools. Now the GitLab MCP server is generally available. With the MCP server, any MCP-compatible agent, such as Claude Code or Cursor, gets direct access to the expanded GitLab catalog of tools and GitLab Duo Agent Platform agents and flows. Your agents can work across more of your GitLab workflow and run Agent Platform agents and flows without leaving your preferred tool.
GitLab Secrets Manager is generally available
  • Tier: Premium, Ultimate
  • Offering: GitLab.com, GitLab Self-Managed
  • Add-ons: GitLab Secrets Manager
  • Links: Documentation · Related Issue Without a centralized secrets store, credentials can become scattered across over-scoped CI/CD variables, local config files, and standalone vaults. This makes them harder to manage, protect, and audit. GitLab Secrets Manager is now generally available on GitLab.com and GitLab Self-Managed. Built on OpenBao, it uses your existing group and project permissions, so there’s no separate access model to maintain. Each CI secret is scoped to the job that needs it, based on environment, branch, and branch protection rules. Audit logs are generated for every create, read, update, and delete. GitLab Secrets Manager consumes GitLab Credits. Start a free 30-day trial or enable it for your group or instance.
Connect Externally Connected Agents (ECAs) to AI Governance
  • Tier: Premium, Ultimate
  • Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
  • Links: Documentation · Related Issue Previously, the AI Governance Dashboard showed activity only from GitLab Duo Agent Platform agents. This provided you total visibility into all of your Agent Platform agents, including the sessions they were running, including tool calls, MCPs used, and the prompt input and output from the user and agent respectively. With the GitLab 19.5 release, after a one-time glab govern setup, you can now extend governance visibility past just GitLab Duo Agent Platform agents, and connect Externally Connected Agents (ECAs) like Claude Code, Cursor, and Codex to GitLab AI Governance by using the GitLab CLI (glab). When Allow external agents and Store AI audit events are enabled, security and compliance teams get visibility into ECAs that run outside GitLab, alongside your GitLab Duo Agent Platform agents. Every qualifying agent session is captured, including who ran it, which agent, which project, and when, with sessions and tool calls appearing in the AI Governance Dashboard and the AI audit events report. Audit events also flow to your SIEM through audit event streaming. Tool output is not sent, except for short error messages from failed tool calls. This feature is in beta. Share your feedback in issue 633489.
Non-default branch tracking generally available
  • Tier: Ultimate
  • Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
  • Links: Documentation · Related Issue Non-default branch tracking is now generally available. You can track vulnerabilities on branches other than the default branch. For the best results, target a small number of long-lived release branches, such as branches for specific environments (project-qa, project-prod) or deployment platforms (project-iOS, project-android). This release includes the following capabilities:
  • Track three additional branches or tags on the security configuration page. This is in addition to the default tracked branch.
  • Filter by tracked ref on the vulnerability report.
  • Filter by branch on the project-level security dashboard.
  • Update vulnerability status on tracked branches.
  • Vulnerability management policies evaluate each tracked branch separately and update only the vulnerabilities on that branch.
Restrict GitLab Duo access by subgroup membership
  • Tier: Free, Premium, Ultimate
  • Offering: GitLab Self-Managed, GitLab Dedicated
  • Links: Documentation · Related Issue Administrators can now select any subgroup, not just top-level groups, in the Restrict access based on group membership setting for GitLab Duo. You can scope GitLab Duo Agent Platform access to a specific team or pilot group without restructuring your group hierarchy. Previously, this setting accepted only top-level groups. Organizations with a single top-level group for all users had no supported way to limit GitLab Duo Agent Platform access to a subset of users. Now, when you select a subgroup, direct members of that subgroup get access. This makes it easier to run a GitLab Duo Agent Platform pilot or roll out access one division at a time on GitLab Self-Managed and GitLab Dedicated.
Agentic Core
/goal command in GitLab Duo CLI is generally available
  • Tier: Premium, Ultimate
  • Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
  • Links: Documentation · Related Issue The /goal slash command in GitLab Duo CLI is now generally available in GitLab Duo CLI 9.27.0. Describe an open-ended goal, and GitLab Duo delegates it to a governed, goal-driven flow that runs locally and handles both implementation and verification. To start, run /goal . For example: In GitLab 19.5 (GitLab Duo CLI 9.24.0), the Run suggested prompts as /goal sessions setting in /settings runs suggested prompts as /goal sessions instead of chat messages. /goal requires GitLab 19.3 and later, and GitLab Duo CLI 9.17.0 and later.
Auto mode in GitLab Duo CLI
  • Tier: Premium, Ultimate
  • Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
  • Links: Documentation · Related Issue GitLab Duo CLI has a new auto mode. In auto mode, GitLab Duo uses tools without asking for approval first, so longer tasks run without stopping for each shell command, git operation, or MCP tool call. Auto mode respects your organization’s controls:
  • Auto mode is off by default. Administrators, Owners, and Maintainers can turn the setting on for instances, groups, and projects. Administrators and group Owners can also lock it to Always off for the entire instance or group.
  • Agent tool governance still applies. Tools set to Always Deny stay blocked. To use auto mode, you need GitLab Duo CLI 9.22.0 or later. Press Tab until the mode under the > prompt shows auto. Use auto mode only in repositories you trust and on branches you can discard.
Configure GitLab Duo CLI with settings files
  • Tier: Premium, Ultimate
  • Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
  • Links: Documentation · Related Issue You can now configure GitLab Duo CLI with settings files, for yourself or for your whole organization. The settings file stores the choices you make in the /settings panel. You can also edit the file directly, or create it in advance, for example in a container image. System administrators can deploy a managed settings file to each machine with a mobile device management tool or group policy. Settings in the managed file take precedence over the settings file, command-line options, and environment variables, and users can’t change them. Settings not in the managed file remain under user control. The settings file requires GitLab Duo CLI 9.26.0 or later, and the managed settings file requires GitLab Duo CLI 9.27.0 or later.
Follow-up reviews in Code Review Flow
  • Tier: Free, Premium, Ultimate
  • Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
  • Links: Documentation · Related Issue In previous versions of GitLab, when you asked GitLab Duo to review a merge request again, it treated the review as a first pass. It could repeat findings from its earlier threads, even ones you had already addressed. Now, Code Review Flow uses comment threads from earlier GitLab Duo reviews, including your replies, to evaluate new changes. GitLab Duo focuses on lines added after its last review, does not repeat points it already raised, and lists outstanding findings in its summary. If you reply on a thread to explain why the code is correct, GitLab Duo does not raise the point again. To start a follow-up review, ask GitLab Duo to review the merge request again. With Start a new review on push turned on, GitLab Duo automatically starts a follow-up review when you push changes.
IAM roles for Amazon Bedrock self-hosted models
  • Tier: Premium, Ultimate
  • Offering: GitLab Self-Managed, GitLab Dedicated
  • Links: Documentation · Related Issue Previously, you could not control which AWS credentials the AI Gateway used for your Amazon Bedrock models. A single AWS identity needed access to all these models. With this release, you can specify an IAM role for each model, and the AI Gateway assumes that role when calling the model. This way, each model gets only the AWS access it needs, even when the role is in another AWS account.
Image context in GitLab Duo CLI
  • Tier: Free, Premium, Ultimate
  • Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
  • Links: Documentation · Related Issue Previously, GitLab Duo CLI could read text files but could not use screenshots or diagrams as context. Now, when you run the CLI locally in interactive or headless mode, it can read images from your repository and attachments on issues, merge requests, and comments in the same project. Image context requires GitLab Duo CLI 9.27.0 or later and a GitLab-managed model.
Improved first-run experience in GitLab Duo CLI
  • Tier: Premium, Ultimate
  • Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
  • Links: Documentation · Related Issue GitLab Duo CLI now helps new users get started without leaving the terminal:
  • On first run, an onboarding card helps you connect MCP servers and install GitLab plugins.
  • Each new session opens with prompts suggested from your open merge requests and issues. For a merge request prompt, GitLab Duo checks out the source branch first if it exists.
  • The status bar shows your branch, project, merge request, /goal progress, and MCP status.
  • The setup screen links to token creation and validates your token before saving.
  • Tips in the prompt and the /whatsnew command point you to new features. To get the full experience, update to GitLab Duo CLI 9.28.0 or later.
MCP server CI/CD artifact tool
  • Tier: Free, Premium, Ultimate
  • Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
  • Links: Documentation · Related Issue Previously, if you needed an agent to check something inside a CI/CD job’s build artifacts, it had to download and unzip the whole archive just to read one file. Now the get_artifact_file MCP tool lets your agent read a single file directly from a job’s artifacts, whether it’s a log, a generated report, or a test fixture.
MCP server GitLab Duo agent and flow tools
  • Tier: Free, Premium, Ultimate
  • Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
  • Links: Documentation · Related Issue New GitLab Duo agent and flow tools let you invoke and track GitLab Duo agents and flows from any MCP client:
  • start_duo_session starts a session.
  • get_duo_session reads a session’s current state.
  • list_duo_sessions pages through your session history.
  • list_duo_agents_and_flows lists the GitLab Duo agents and flows enabled in a project.
MCP server groups tool
  • Tier: Free, Premium, Ultimate
  • Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
  • Links: Documentation · Related Issue …
View original

Upgraded? How did it go?

Discussion