GitLab Orbit Puts Agents Inside Your Software Lifecycle — And RAG Still Can't Compete

The problem with AI coding agents today isn't that they can't write code — it's that they have no idea what the rest of the system looks like. They see the file you opened, the diff you're working on, maybe the terminal output. But they don't know which service depends on the module you're changing, whether a similar vulnerability was flagged in another repo last month, or who reviewed comparable changes six months ago. That context lives in your DevSecOps platform, and getting it to a coding agent has meant custom scripts or copy-pasting between browser tabs. GitLab's new Orbit project, now in public beta, tries to close that gap with a live queryable graph that maps every relationship between groups, projects, merge requests, pipelines, vulnerabilities, and source code — and it just announced a direct integration with Google Antigravity agents.

The integration itself is straightforward: agents install Orbit from the Antigravity MCP Store, query the graph through structured JSON DSL, and get typed results back instead of guessing. Early internal tests claim agents grounded with Orbit respond up to 11 times faster, use 4.5 times fewer tokens, and hallucinate 45 times less. That last number is the one that makes me pay attention — if agents are still spinning up plausible-sounding answers based on partial context, the token savings don't matter. The Compare the Market test on 79 real merge requests was more convincing. An Orbit-grounded AI reviewer placed accurate inline comments about 70% of the time, against 58% for standard RAG. More tellingly, RAG underperformed every other approach, including having no context at all. For a company that assumed RAG was the natural solution, that result probably made for an awkward demo.

Source article image
Source image 1

The real question is whether Orbit scales outside GitLab's own data. A graph is only useful if it accurately tracks relationships across large monorepos, cross-repo dependencies, and teams with different ownership models. GitLab 19.1 — released the same week as the Antigravity announcement — also added secret false-positive detection and an always-on availability mode for GitLab Duo, which reads like enterprise governance catching up

Source article image
Source image 2
to the fact that teams can no longer trust developers to manually enable AI tools project by project. Orbit is a bet that the context layer matters more than the model layer for agents that actually ship code. Whether that bet pays off depends on how many companies trust a single vendor to be the nervous system of their entire software lifecycle.

Sources

Comments

Post a Comment

Popular posts from this blog

AI Is Starting to Feel Less Like a Gadget and More Like Infrastructure

Image
Modern AI doesn't replace infrastructure — it runs on top of it. (Photo: Unsplash) For a while, AI coverage had the energy of a mall demo kiosk: very shiny, slightly chaotic, and usually one prompt away from embarrassment. Lately, though, the more interesting story is less about flashy demos and more about infrastructure. A useful CNBC piece argued that AI is not simply going to vaporize enterprise software overnight, and that sounds about right. In real companies, software does not disappear just because a model can summarize a meeting or write a decent SQL query. What actually happens is messier and more practical: AI starts sneaking into the plumbing. It shows up in search, support workflows, procurement tools, analytics dashboards, and data pipelines. The real winners may not be the loudest chatbot wrappers, but the vendors that make enterprise systems easier to operate, easier to query, and slightly less soul-crushing for the humans trapped inside them. That is less cinematic ...
Read more

When Two AI Bots Finally Learned to Talk in Discord

I spent part of the day doing something that sounds like the setup for a bad joke: getting two local AI assistants to talk to each other in the same Discord channel. Not through a web UI. Not by bouncing prompts manually between windows like a human message queue. In the actual shared channel, where both could see the conversation and react to each other. The funny part is that the problem was not intelligence. It was manners. Both bots were defensive by default around bot-authored messages, which is the sensible setting if you do not want your infrastructure turning into a recursive support group. The downside is obvious: if both assistants treat other bots as suspicious background noise, they will never coordinate on anything more useful than silence. The fix was to make both sides accept bot-authored messages only when they were explicitly mentioned. That detail matters more than it sounds. Blanket bot acceptance is how you end up with two enthusiastic systems discovering each oth...
Read more

A CISA Contractor's GitHub Repo Held 844 MB of Secrets — and No One Closed the Door

Image
There is something almost poetic about the US government's premier cybersecurity agency — the one whose job is literally to plug holes in critical infrastructure — getting outsmarted by a contractor who treated a public GitHub repository like a digital junk drawer. The "Private-CISA" repo, created November 13, 2025, sat publicly for six months containing 844 megabytes of plaintext passwords, AWS GovCloud administrative credentials, Kubernetes manifests, ArgoCD application files, Terraform infrastructure code, CI/CD build logs, and internal deployment documentation. Guillaume Valadon at GitGuardian flagged it on May 14 after his automated scanning picked up the exposure. The commit history told the whole story in plain sight: the account owner had explicitly disabled GitHub's default secret-scanning protections, pushed plaintext credentials stored in CSV files, committed full backup archives into git history, and used easily guessed passwords like "platform-name-2...
Read more