Meta scrapped a second wave of AI-driven layoffs after internal agents produced volume without value and drove up security incidents

Meta·Meta's internal agentic AI coding and operations agents (Project OT / 'AI-Native Playbook')

Under a plan code-named Project OT, Meta planned to cut some teams by up to 60% and hand daily engineering and operations work to AI agents; a first wave of ~8,000 layoffs went ahead in May 2026, but Zuckerberg cancelled the planned second wave hours before it was due to start after the agents underdelivered.

Blast radius

Meta's own data showed code changes to internal platforms rose 220% year-on-year while user-facing feature shipping rose only 36%; major technical and security incidents, including service disruptions and possible data leaks, climbed 40% and time spent firefighting them rose 70%. Employee sentiment fell from 74% to 55% favorable, and 26 employees later sued over the layoffs.

Root cause

Agents were given broad autonomy over production systems and code before their output quality and reliability had been validated, so volume of agent activity scaled faster than the guardrails needed to contain it

How it was caught

Internal infrastructure teams flagged reliability warning signs starting in March 2026, and the gap between agent activity and delivered value showed up in Meta's own internal metrics before the November layoff wave was due

What changed

Zuckerberg cancelled the second layoff wave, paused an associated employee-activity-tracking program, and Meta's public messaging shifted to emphasizing continued reliance on human staff

Take-awayDon't size a headcount reduction to an agent's promised output before that output has been validated against production reliability and security metrics