Meta tracks US employee workflows to train AI agents

Meta has spent the last eighteen months signaling that training data is an asset class it will pay almost any price for. It committed up to $135 billion in 2026 capex for AI infrastructure, and separately took a 49% stake in Scale AI — the most prominent human-labeled-data vendor in the industry — for more than $14 billion. Buying half of the market leader in curated training data ought to solve the data problem. Yet here is Meta, weeks later, installing keystroke and mouse-movement loggers on the computers of its own US employees. That gap is the real story.

The implication is that for the specific class of model Meta is now trying to build — autonomous agents that can navigate real enterprise software, drive dropdown menus, handle keyboard shortcuts, and move through Gmail and internal tools like a human operator — Scale AI's core product is the wrong shape. Labeled images, ranked responses, and annotated text corpora do not teach a model what it feels like to use a computer. Mouse trajectories, click cadence, tab-switching patterns, and the small mechanical habits of knowledge work are a different data type, and they appear to be the actual bottleneck. Meta's willingness to spend $14B on one data source and still reach for its employees' telemetry says something uncomfortable about where the frontier is: the model architecture is less the constraint than a shortage of authentic human-computer-interaction data that vendors cannot manufacture to scale.

MCI is not a worldwide program. Meta drew the line at the US border, and the reason is regulatory. In Italy, tracking employees electronically for productivity purposes is banned outright. German courts have set a high bar, allowing keystroke logging only under exceptional conditions. Across the EU more broadly, GDPR would treat the continuous capture of mouse movements, keystrokes, and screenshots as processing of personal data that requires a legal basis the 'AI training' purpose is unlikely to satisfy. Valerio De Stefano, a labor-law professor at York University, has argued the European frameworks would likely prohibit a program like MCI and that the mere awareness of surveillance reshapes workplace power dynamics in favor of the employer.

The contrast with the US is stark. Yale law professor Ifeoma Ajunwa noted bluntly that federally there is no limit on worker surveillance. That asymmetry is not an accident of rollout — it is the entire economic argument for where MCI runs. Meta gets to harvest the exact kind of realistic knowledge-work telemetry its agents need to train on precisely because US workers have weaker legal protections than their European colleagues doing the same job. In effect, the geography of the program reveals the geography of worker power in the AI era: the richer the training data a company wants, the more attractive jurisdictions with thin labor privacy law become. That has implications well beyond Meta — any multinational building computer-use agents will face the same calculus, and Amazon's €32M GDPR fine for worker surveillance shows what happens when companies get the calculus wrong.

Meta's public line is that MCI data will not be used for performance reviews. The company's spokesperson, Andy Stone, framed the telemetry as nothing more than the raw material AI agents need to learn how humans actually use computers — the mouse movements, the dropdowns, the keyboard shortcuts. But the calendar is doing its own work. CTO Andrew Bosworth's memo articulating a vision where agents primarily do the work landed weeks before the Reuters exclusive on the keystroke tool; weeks after that, roughly 8,000 employees — about 10% of the global workforce — are scheduled to be laid off starting May 20, 2026. That sequence is what commentators on YouTube and Reddit keep returning to: the vision, the tool, then the cut.

The internal backlash follows directly from that timeline. Bosworth himself confirmed there is no opt-out on company-issued devices, which community voices have zeroed in on as the move that eliminates any meaningful consent. Reddit's r/technology discussion is overwhelmingly cynical, with 'training your replacement' the dominant framing and deep distrust of the performance-review pledge — users point out that continuous keystroke and mouse telemetry is exactly the data a company would need if it ever did want to flag 'mouse jiggler' users or quantify individual output. X sentiment skews the same way, with one viral satirical thread parodying a fictional 'Senior Director of Workforce Intelligence' — the joke lands because the distance between surveillance-for-agents and surveillance-for-management feels, to employees, like a policy choice Meta can quietly revise later rather than a technical impossibility today.

Beyond the labor and privacy framing, there is a dual-use implication that mainstream coverage has largely glossed over. A Reddit commenter on r/technology pointed out — correctly — that the exact kind of data MCI captures, continuous mouse-movement trajectories tied to real human sessions, is what bot-detection systems like reCAPTCHA use to distinguish humans from machines. Google's 'I'm not a robot' infrastructure, and every adjacent fraud-detection system, fingerprints humanity off these tiny unconscious patterns: how you drift the cursor before a click, how you pause, how you correct. A Meta-scale corpus of authentic human mouse trajectories is therefore not just agent training data. It is, structurally, a corpus that makes human behavior legible in both directions — easier to imitate, and easier to detect.

That second-order question — who else benefits from a high-fidelity human-interaction corpus, and what downstream defenses does it erode — has not surfaced in Meta's public explanation. The Reddit technical debate around MCI split along related lines: some commenters dismissed the program as cargo-cult data collection, while others cited vision-language-action models and argued mouse and keystroke trajectories are genuinely load-bearing inputs for computer-use agents. A separate contrarian thread, coming from an enterprise-AI-governance perspective, reframed the entire story as a systemic problem: every company deploying AI tools faces the same bidirectional data-leakage question, and singling Meta out obscures that the underlying norm — employers can train on whatever flows through company hardware — is now the default across the industry. The quieter implication is the one worth watching: once an agent has been taught to move a mouse like a human, the infrastructure built to tell the two apart becomes a lot cheaper to defeat.