Skip to content
Briefings are running a touch slower this week while we rebuild the foundations.See roadmap
Iran Conflict 2026
30MAR

GitLab rewrites engineering around AI agents

4 min read
08:00UTC

GitLab CEO Bill Staples published 'GitLab Act 2' on 11 May 2026, cutting the company's country footprint by up to 30% and breaking R&D into approximately 60 smaller teams on the explicit premise that AI agents will plan, code, review, deploy, and repair software.

← Back to Trump wants Iran's oil; 3,500 Marines landJump to analysis ↓
ConflictDeveloping
Key takeaway

GitLab's Act 2 makes the CEO-signed case that AI agents replace engineering co-ordination, dissolving the management layer that connected them.

GitLab CEO Bill Staples published "GitLab Act 2" on Monday 11 May 2026, announcing a restructuring that cuts the company's country footprint by up to 30%, removes up to three management layers from some functions, and breaks R&D into approximately 60 smaller teams, nearly doubling the number of independent teams. The explicit justification in Staples's own words: "Software will be built by machines, directed by people. Agents will plan, code, review, deploy, and repair."

The 60-team structure concentrates individual-contributor output while stripping out the managers who previously co-ordinated across functions. In practice, individual engineers report into smaller pods with no manager between them and the AI tools they use to build product. A voluntary separation window closes 18 May; full restructuring completes by 1 June 2026. Financial impact lands on the 2 June earnings call, making it the first public headcount figure for the new structure.

GitLab did not arrive at this thesis alone. Salesforce CEO Marc Benioff applied the same structural argument to customer support: AI agents replaced roughly half the team, and no new engineers were hired in its fiscal year ending January 2026 . Meta applied it to engineering titles in April, replacing conventional engineering roles with AI-native designations . GitLab has now applied the thesis to engineering structure itself: not which roles exist, but how many engineers it takes to ship product. That progression from support functions to engineering titles to engineering organisation is what makes the May cluster a pattern rather than separate decisions by unrelated companies.

The voluntary separation window that closes 18 May avoids the immediate WARN Act filing that a simultaneous termination event would trigger. GitLab operates across dozens of countries with no single US site large enough to meet the WARN threshold in any single jurisdiction. Both structural facts sit alongside the public manifesto, which is arguably the most candid CEO-signed statement on AI displacement to appear from a major DevOps company in 2026.

Deep Analysis

In plain English

GitLab makes software that other software companies use to build their products. Think of it as the tool companies use to organise engineers, review code, and push updates. On 11 May 2026, GitLab's chief executive published a document saying the company itself would restructure around the assumption that AI would do most of the engineering work going forward. His argument: AI agents can now plan what to build, write the code, check it, push it to production, and fix problems. Humans direct the process rather than perform it. So GitLab is cutting the number of countries it employs engineers in, removing manager layers, and splitting its engineering organisation into roughly 60 small, autonomous teams. Why this matters beyond GitLab: GitLab is not a frontier AI lab predicting the future. It is a practical software tools company declaring that the future is already here in its own operations. When the company that makes the tools other engineers use restructures itself around AI-built software, it is saying something about where the whole software industry is heading.

Deep Analysis
Root Causes

GitLab's restructuring has two structural drivers that the fact does not name.

First, the GitLab product roadmap and the GitLab engineering structure have converged onto the same thesis. GitLab sells DevOps tooling including CI/CD pipelines, code review, and deployment orchestration. Its Act 2 document argues that AI agents will perform these functions.

If that thesis is correct for GitLab's customers, it must also be correct for GitLab's own engineering. The restructuring is therefore not a cost response to a revenue miss; it is the company applying its own product roadmap to itself.

Second, capital market pressure from the Harvard Business Review finding that only 2% of organisations announcing AI-related cuts have implemented AI that actually accounts for them creates a verification problem for companies that claim AI productivity gains.

GitLab, as a software tool company, has unusually direct access to internal metrics that can demonstrate AI productivity gains to investors. The 2 June earnings call is the first public test of whether those metrics materialise as disclosed.

What could happen next?
  • Precedent

    GitLab's 60-team R&D structure becomes the reference architecture investors ask other mid-cap DevOps companies to justify not adopting.

    Short term · 0.75
  • Consequence

    The 2 June earnings call is the first public test of whether declared AI productivity gains translate to financial disclosure; a miss would undermine the entire CEO manifesto genre.

    Immediate · 0.8
  • Risk

    Removing co-ordination layers without a proven AI substitute creates integration risk that surfaces only after the voluntary separation window closes 18 May.

    Short term · 0.7
Sources:GitLab (Bill Staples, CEO)
Mentions:GitLab →Bill Staples →Gartner →Boston →Marc Benioff →Meta →Amazon →Upwork →Hayden Brown →Salesforce →WARN Act →
First Reported In

Update #9 · GitLab signs the manifesto, Brussels backs out

GitLab (Bill Staples, CEO)· 15 May 2026
Read original →
Causes and effects
Caused by
Salesforce halves support staff using AI
Salesforce's AI agent customer support replacement established the same structural thesis GitLab now applies to engineering itself
Occurred 29 Mar 2026
Read story →
Meta codes its own org chart
Meta's engineering title replacement with AI-native roles in April preceded GitLab applying the thesis to engineering structure itself
Occurred 19 Apr 2026
Read story →
This Event
GitLab rewrites engineering around AI agents
GitLab's restructuring applies the AI-replacement thesis directly to engineering structure, rather than headcount alone, making it the most operationally specific CEO manifesto in the 2026 tech restructuring cycle.
Different Perspectives
IAEA
IAEA
Director General Rafael Grossi appeared in person at the UNSC on 19 May and warned that a direct hit on an operating reactor 'could result in very high release of radioactivity'. The session produced a condemnation record but no resolution, and the Barakah perimeter was already struck on 17 May.
Hengaw (Kurdish rights monitor)
Hengaw (Kurdish rights monitor)
Hengaw documented three judicial executions and the detention of Kurdish writer Majid Karimi in Tehran on 19 May, establishing Khorasan Razavi province as the newest geography in Iran's wartime judicial record. The organisation's Norway-based operation continues to surface a domestic repression track running in parallel with every diplomatic and military development.
India
India
Six India-flagged vessels conducted a coordinated cluster transit under PGSA bilateral assurances during the 17 May window, paying no yuan tolls. New Delhi's inclusion in Iran's state-to-state passage track insulates Indian energy supply without requiring endorsement of the PGSA's yuan-toll architecture or alignment with the US coalition.
Pakistan
Pakistan
Pakistan is the only functioning diplomatic bridge between Tehran and Washington. Its role is relay, not mediation in the settlement sense: it conveyed Iran's 10-point counter-MOU in early May, relayed the US rejection, and is now passing 'corrective points' in the third documented exchange of this sub-cycle without either side working from a shared text.
UK and France (Northwood coalition)
UK and France (Northwood coalition)
Twenty-six coalition members have published no rules of engagement eight days after the Bahrain joint statement; Lloyd's underwriters have conditioned war-risk reopening on written ROE from either Iran or the coalition. Italian and French mine-countermeasures deployments are operating on the in-water clearance task CENTCOM Admiral Brad Cooper's 90% mine-stockpile claim does not address.
Saudi Arabia
Saudi Arabia
Riyadh has not publicly commented on the Barakah strike or the 50-47 discharge vote. Saudi output feeds the IEA's $106 base case; the $5 Brent premium above that model reflects institutional uncertainty no Gulf producer can compress through supply adjustment alone.