Skip to content
AAA.win

AI tool

GitLab Duo

GitLab's AI product family spanning code suggestions and chat through configurable agents and multi-step flows across supported software-lifecycle workflows.

Editorially reviewedVerified 2026-08-112 official or primary sources

What it is

GitLab Duo remains the documentation-level name for GitLab's AI features, while current product material emphasizes the GitLab Duo Agent Platform for agents and flows. The broader family can assist work across planning, coding, review, security, and operations in GitLab.

Do not treat the family name as one uniform capability. Record whether a test uses suggestions, chat, an agent, or a flow; then inspect permissions, repository context, diffs, commands, pipeline evidence, security findings, audit trails, and approvals.

Worth evaluating for

  • Organizations managing software work inside GitLab
  • Lifecycle pilots connecting issues, code, review, security, and pipelines
  • Teams testing configurable agents under existing project permissions

What to measure

  • Change correctness, pipeline results, security findings, and reviewer effort
  • Project permissions, context boundaries, auditability, and action approval
  • Differences between suggestions, chat, agents, and multi-step flows

Decision cautions

  • GitLab Duo is an umbrella brand; individual features have different risks and controls.
  • Agent and flow access can extend beyond code generation into lifecycle actions.
  • Generated changes and security guidance require human review and pipeline validation.

Sources checked

Open the original pages before relying on a time-sensitive product decision.

  1. GitLab Duo Agent PlatformGitLab
  2. GitLab Duo documentationGitLab
Version · v4.3.4-indexnow-root-proof

Latest releases

IndexNow root-proof request compatibility

After v4.3.3, the exact root-level {key}.txt proof returned HTTP 200, but a full request carrying keyLocation still returned HTTP 403; a minimal homepage request with the same production key and no keyLocation returned HTTP 202. This release omits that field, while the automatic full run and idempotent rerun remain deployment checks.

IndexNow key-proof compatibility

Changed IndexNow verification to the official root-level {key}.txt convention after the first production notification returned HTTP 403; revalidation remains pending, while the website, sitemaps, and Bing sitemap processing are unaffected.

Bing sitemap discovery and IndexNow change notifications

Prepared canonical sitemap discovery for Bing and added automatic IndexNow change notifications while keeping segmented sitemaps authoritative and making no claim that a notified URL has been crawled or indexed.

View all releases