GitLab Orbit

GitLab Orbit is GitLab's software-lifecycle context graph for AI agents and engineers, declared generally available on October 29, 2026 for Premium and Ultimate on GitLab.com (Self-Managed / Dedicated following). It connects code, merge requests, work items, pipelines, vulnerabilities and ownership into one continuously updated, permission-aware graph that Duo, Claude Code, Codex, Cursor and other MCP/CLI agents can query.

Official: about.gitlab.com/blog/gitlab-orbit-ga · Docs: docs.gitlab.com/orbit · X: @gitlab · Business Wire

Key points

1. GA this window: experiment → beta → GA in 19.5 era; Oct 29 blog + @gitlab post + Business Wire.
2. Problem it names: agents guessing from diffs/files alone ("artificial confidence"); Orbit answers with callers, owners, pipeline and vuln context.
3. Measured claims (GitLab testing): up to 45× fewer retries, 4.5× fewer tokens same model/tasks; Compare the Market reviewer study cited (~70% vs ~58% RAG).
4. Access paths: native on Duo Agent Platform; MCP or glab orbit setup for third-party agents; REST for custom tools; Data Explorer for humans.
5. Pricing: shared org query packs ($30 GitLab Credits / user / month → 1,000 queries); 30-day trial via account team.

Why it matters

Clear branded product (not a vague "GitLab AI") hitting GA with official channels this scan window.

How to try it

1. Premium/Ultimate on GitLab.com: ask your account team for a 30-day Orbit trial.
2. For Claude Code / Codex / Cursor etc.: glab auth login then glab orbit setup, or connect via MCP.
3. Ask graph questions (blast radius of a CVE, who owns a failing job) instead of grepping every repo.

Self-Managed and GitLab Dedicated GA is staged over the following weeks.