glab(1)

💖 glab(1) — the remote Orbit page, but make it make sense 💖

okay bestie, this is glab-orbit-remote: Interact with the remote GitLab Knowledge Graph. 🛰️✨ (and yes, it's EXPERIMENTAL — we'll get to that, hold on)

---

🌸 NAME 🌸

glab-orbit-remote — talk to the remote GitLab Knowledge Graph like it's your group chat. (EXPERIMENTAL, bestie. Emphasis on experimental.)

---

✨ SYNOPSIS ✨

glab orbit remote  [flags]

---

🦋 DESCRIPTION 🦋

So here's the vibe: you can query the remote GitLab Knowledge Graph — product name is Orbit, iconic — straight from your CLI. No browser, no vibes-based clicking, just you and the graph. 🪐

Important deets: all the endpoints are user-scoped, NOT project-scoped. So don't come at them with project energy, they will not respond. And every single one is gated behind the knowledge_graph feature flag. 🚪🔒

🎀 start here, fr fr

These discovery commands are your entry point — they hand you the authoritative ontology and the query DSL schema. Do not skip them, I'm begging. 🙏

glab orbit remote status                         # Is the service up?
glab orbit remote schema                         # What entities and edges exist?
glab orbit remote schema MergeRequest Project    # Show details for specific nodes
glab orbit remote dsl                            # Full query DSL JSON Schema
glab orbit remote tools                          # MCP tool manifest

Once you actually know the shape of the graph (the shape!! 🫶), then you run a query:

glab orbit remote query path/to/query.json
cat query.json | glab orbit remote query -

And if you wanna peek at indexing progress for a namespace or project:

glab orbit remote graph-status --full-path gitlab-org/gitlab

💀 exit codes (know them, love them)

• 1: Generic error. The classic. It's giving "something happened, idk what."
• 2: Orbit endpoint unavailable — HTTP 404, for example, when the feature flag is off. 👻
• 3: Not authenticated — HTTP 401. Who are you?? Stranger danger. 🙈
• 4: Access denied — HTTP 403, for example, when no Knowledge Graph enabled namespaces exist. 🚫
• 5: Rate limited — HTTP 429. Slow down, main character, you're not the only one here. 😭

⚠️ okay real talk for a sec: this feature is an experiment and is not ready for production use. It might be unstable, or it might get removed at any time. Like, any time. No warning. So please don't build your whole thing on it. 💅 For more info: https://docs.gitlab.com/policy/development_stages_support/

---

💅 OPTIONS INHERITED FROM PARENT COMMANDS 💅

• -h, --help[=false] — shows help for this command. Default is false, so it won't just pop up uninvited, don't worry. ✨

---

🔥 EXAMPLE 🔥

Discovery workflow — always start here, I said what I said:

# Discovery workflow (always start here)
$ glab orbit remote status
$ glab orbit remote schema
$ glab orbit remote schema User Project MergeRequest
$ glab orbit remote dsl
$ glab orbit remote tools

Run a query from a file, chef's kiss:

# Run a query from a file
$ glab orbit remote query ./query.json

Run a query from stdin with raw output, perfect for jq pipelines (the way that pipe hits 🧚):

# Run a query from stdin (raw output for jq pipelines)
$ echo '{"query":{"query_type":"traversal","node":{"id":"p","entity":"Project"},"limit":5}}' \
    | glab orbit remote query --response-format raw -

Inspect indexing progress, go off:

# Inspect indexing progress
$ glab orbit remote graph-status --full-path gitlab-org/gitlab

---

🌈 SEE ALSO 🌈

• glab-orbit(1)
• glab-orbit-remote-dsl(1)
• glab-orbit-remote-graph-status(1)
• glab-orbit-remote-query(1)
• glab-orbit-remote-schema(1)
• glab-orbit-remote-status(1)
• glab-orbit-remote-tools(1)

---

and that's the whole page, bestie 💖 this little icon was Auto generated by spf13/cobra, stamped Aug 2026, and it lives under the name glab(1). go query something iconic, mwah 🫶🎀