glab(1)

📦
version 1.128.0 · 7 versions
, in arch rolling

glab-duo-cli 💅 (that's glab(1) in the house, bestie)

okay so real talk — welcome to the glab-duo-cli corner of the glab(1) manual. this one's short, sweet, and lowkey iconic. let's get into it ✨

🌸 NAME 🌸

glab-duo-cli — literally just: Run the GitLab Duo CLI.

🎀 SYNOPSIS 🎀

glab duo cli [command] [flags]

🦋 DESCRIPTION 🦋

So what you're doing here is running the GitLab Duo CLI (the binary's called duo, cute right?) through glab. ngl that's the whole vibe.

The GitLab Duo CLI brings the GitLab Duo Agent Platform straight to your terminal. You can ask GitLab Duo questions about your codebase, and it'll autonomously do stuff on your behalf. main character energy, honestly 👑

The GitLab Duo CLI runs in two modes, and you gotta know both:

  • Interactive (default): glab duo cli opens a whole session where you can throw multiple prompts at it, with build and plan modes. it's giving hangout 🫶
  • Headless: glab duo cli run --goal "<prompt>" runs exactly one prompt and dips. perfect for runners, scripts, and automated workflows. in-and-out, no small talk 🏃‍♀️

Also the best part: when you use the GitLab Duo CLI through glab, glab handles authentication for you. you authenticate only once. no cap, that's a slay 💅

✨ Prerequisites (read these fr fr) ✨

If you're on GitLab 18.11 to 19.1, you can still use the GitLab Duo CLI by turning on beta and experimental features (https://docs.gitlab.com/user/duo_agent_platform/turn_on_off/#turn-on-beta-and-experimental-features). retro era 💀

🍓 Configuration options 🍓

  • duo_cli_auto_run — skip the run confirmation prompt. no more "are you sure" 🎀
  • duo_cli_auto_download — skip the download confirmation prompt. same energy ✨

🌈 The pass-through situation 🌈

Except for the update command, glab passes all other arguments and flags straight through to the GitLab Duo CLI binary. so whatever you throw at it, it goes to duo.

Wanna see the GitLab Duo CLI's actual commands and flags? run glab duo cli help. iykyk 🔥

For more info, see the GitLab Duo CLI documentation (https://docs.gitlab.com/user/gitlab_duo_cli/).

💖 OPTIONS 💖

  • --install[=false] — install the GitLab Duo CLI binary without running it. like buying the outfit but not wearing it yet 👗
  • --update[=false] — check for and install updates to the binary. literally the same thing as the update command, just a different door to the same room.
  • -y, --yes[=false] — skip confirmation prompts. consent pre-given, we move 🫡

⭐ OPTIONS INHERITED FROM PARENT COMMANDS ⭐

  • -h, --help[=false] — show help for this command. the classic. the icon. 🙈

🔥 EXAMPLE 🔥

yes bestie, examples. we love to see it.

# Start an interactive GitLab Duo CLI session
glab duo cli

# Use the GitLab Duo CLI in headless mode with a single prompt
glab duo cli run --goal "Fix the failing tests in this project"

# Pass any command or flag through to the GitLab Duo CLI binary (for example: model, version, run)
glab duo cli <command>
glab duo cli --model claude_sonnet_4_6

# Show GitLab CLI help content
glab duo cli --help

# Show GitLab Duo CLI help content, including commands and flags
glab duo cli help

# Run without prompts (for use in scripts and non-interactive environments)
glab duo cli --yes

# Install the GitLab Duo CLI binary
glab duo cli --install

# Install the GitLab Duo CLI binary without prompts
glab duo cli --install --yes

# Check for and install updates
glab duo cli update

🧚 SEE ALSO 🧚

go read those too, they're besties with this one 🫶

aaaand that's the page, babe 💜 this manual pag was Auto generated by spf13/cobra, dated Nov 2026, and it lives in glab(1). periodt 🎀✨

📦 where this page comes from