GitLab 19.2 adds agentic automation to clear AI coding backlogs
GitLab Inc. released GitLab 19.2, introducing governed agentic automation to manage the increased code and dependencies generated by AI. Key features include Dependency Scanning Auto-Remediation, Security Review Flow, and GitLab Duo CLI. A commissioned study reported a 400% return on investment for users of the GitLab Duo Agent Platform.

*this image is generated using AI for illustrative purposes only.
GitLab Inc. today released GitLab 19.2, introducing governed agentic automation to address the backlog of code, dependencies, and changes created by AI. The update allows developers to fix vulnerable dependencies automatically, catch logic flaws missed by scanners, and create custom agentic workflows while maintaining organizational controls. A Forrester Consulting study commissioned by GitLab found that organizations using the GitLab Duo Agent Platform can achieve a 400% return on investment with payback in under six months.
Dependency Scanning Auto-Remediation
Dependency Scanning Auto-Remediation is now available in public beta. This feature addresses security risks from transitive dependencies, which a study of the Maven ecosystem found reach roughly 63% of latest releases. When a scan identifies a vulnerable package, GitLab opens a merge request with a suggested fix. If an upgrade breaks the build, agents iterate to resolve the issue within the same merge request. New configuration controls allow developers to set severity thresholds and version scopes. All changes stop at existing approval gates and generate a full audit trail.
Security Review Flow
Security Review Flow, now in public beta, detects vulnerabilities that pattern-based scanners cannot identify, such as business logic errors and race conditions. The feature analyzes code intent rather than matching known patterns to find flaws like broken object-level authorization, missing authorization on state-changing operations, and information disclosure. Findings include severity ratings and suggested fixes where available. The flow does not approve changes automatically; a person must make the final decision.
GitLab Duo CLI and Custom Flows
GitLab Duo CLI is now generally available across GitLab.com, Self-Managed, and Dedicated deployments. This tool brings GitLab Duo Agent Platform's agents to the developer's terminal with full project context, allowing users to diagnose failed pipelines or propose fixes without leaving the command line. Custom Flows are also generally available, enabling teams to replace manual multi-step workflows with agentic automations triggered by GitLab events. These flows authenticate to external services using short-lived, job-scoped tokens.
Controls and Governance
GitLab 19.2 introduces controls to ensure automation remains trustworthy at scale. The AI Audit Event Report, now in beta, records AI-assisted actions as dedicated audit events for compliance and security teams. Group-level custom instructions for GitLab Duo Code Review allow administrators to set review behavior across projects simultaneously. New MCP access controls govern which agents can run and what resources they can access.
| Feature | Status | Function |
|---|---|---|
| Dependency Scanning Auto-Remediation | Public Beta | Fixes vulnerable dependencies automatically |
| Security Review Flow | Public Beta | Detects logic flaws and race conditions |
| GitLab Duo CLI | Generally Available | Provides agent access in the terminal |
| Custom Flows | Generally Available | Automates multi-step workflows |
How will the introduction of auto-remediation and agentic workflows impact the traditional roles and responsibilities of security and DevOps teams?
What competitive responses can we expect from rival DevSecOps platforms like GitHub or Bitbucket regarding AI-driven governance?
How might the requirement for human approval in the Security Review Flow affect the speed of development cycles in high-velocity environments?






























