Coding agents are stuck choosing between RAG or knowledge graphs. Both come with tradeoffs. GitLab connected the whole pipeline instead, one live graph, updated on every push. Try it with MCP in Claude Code, Codex, or GitLab directly.

gitlab worries me with the dei they hire

A live graph updated on every push is far more useful than stale retrieval over yesterday’s codebase.

one live graph updated on every push is the move. agents shouldn't pick between two half-maps.

GitLab’s “one live graph, updated on every push” got us wondering: how can an agent tell whether its answer covers an unmerged change? We asked an agent to work through a branch comparison in a SmallDoc:

one live graph updated on every push beats picking rag vs kg. the refresh loop is the hard part.

Maybe fix official gitlab endpoint to work using oauth or add PAT support first? Devin support is not ideal, and in Mistral it flat out terminates connection.

So you're saying AI needs to get off the RAG? Claude certainly does.