glab(1)

πŸ’… glab(1) β€” the orbit one (yes, the glab manual, bestie)

okay so real talk: this is the glab page for the glab orbit corner of the universe, and it's giving experimental in the most serious way possible. buckle up, we're going orbital πŸš€βœ¨


🌸 NAME 🌸

glab-orbit β€” query the GitLab Orbit context graph. (EXPERIMENTAL) πŸ§ͺ


πŸŽ€ SYNOPSIS πŸŽ€

glab orbit [] [flags]

yes, that empty [] is literally in there. she's mysterious, she's minimal, she's iconic. πŸ’…


πŸ¦‹ DESCRIPTION πŸ¦‹

So glab orbit is basically a little doorway β€” you run the GitLab Orbit CLI through glab. Cute, right? 🫢

Coding agents, listen up: run glab orbit --yes skills get orbit to load the Orbit skill. The --yes is doing the heavy lifting there β€” it installs the binary without a prompt on first use, no cap.

Okay so here's the whole vibe: every command and flag, including --help, is forwarded verbatim to the managed Orbit binary. Verbatim. Like, glab is not editing your stuff, she's just the messenger. And glab downloads, verifies, and updates that binary for you on first use β€” she's got you, fr fr. 🌈

Until the binary is actually installed, --help shows this text instead. (A little placeholder moment. She's doing her best. πŸ₯Ί)

Also super important: glab passes your resolved GitLab credential to the binary on every invocation. So remote commands like glab orbit query need no separate login. Zero. None. You're already in. πŸ‘‘

Scope check: glab handles only the update command and the --install, --update, and --yes flags herself. Everything else gets yeeted straight to Orbit. Run glab help orbit to see those.

⭐ Prerequisites ⭐

  • Run glab auth login to authenticate.
  • Orbit must be enabled for your namespace (the knowledge_graph feature flag).

⭐ Configuration options ⭐

  • orbit_cli_auto_run: skip the run confirmation prompt.
  • orbit_cli_auto_download: skip the download confirmation prompt.

Want the full lore? Check the Orbit documentation ⟨https://docs.gitlab.com/orbit/⟩.

🚨 Heads up, bestie: this feature is an experiment and is not ready for production use. It might be unstable or removed at any time. Like, at any time. For more information, see https://docs.gitlab.com/policy/development_stages_support/.

✨ OPTIONS ✨

  • -h, --help[=false] β€” show the Orbit binary's help, or this text until the binary is installed. either way you're getting help, slay πŸ’–
  • --install[=false] β€” install the Orbit binary without running it. just the install. no plot twist.
  • --update[=false] β€” check for and install updates to the binary. same as the update command. πŸ”₯
  • -y, --yes[=false] β€” skip confirmation prompts. the "don't ask me, just do it" flag. periodt.

🌟 EXAMPLE 🌟

okay these examples ate, ngl. study them like they're exam material πŸ“š

# Connect Orbit to the coding agents on this machine, or undo it
$ glab orbit setup
$ glab orbit uninstall

# Query the remote Orbit graph (authenticates automatically)
$ glab orbit status
$ glab orbit query ./query.json
$ glab orbit graph-status --full-path gitlab-org/gitlab

# Index and search a local copy of the code graph
$ glab orbit index .
$ glab orbit grep "parse config"

# Show the Orbit binary's own help and version
$ glab orbit --help
$ glab orbit version

# Install or update the managed binary without running it
$ glab orbit --install
$ glab orbit update

that glab orbit grep "parse config" line? obsessed. πŸ“


πŸ‘€ SEE ALSO πŸ‘€

the friend group. the squad. go say hi. πŸ’œ


✨ that's the whole page, bestie ✨ this little masterpiece was auto generated by spf13/cobra, dated Nov 2026, and she's the glab(1) manual β€” go forth and orbit responsibly πŸ›°οΈπŸ’…πŸŽ€

πŸ“¦ where this page comes from