Meta's MCI Tool Captures Employee Interactions for AI Training

What Meta's MCI Tool Does
Meta is deploying the Model Capability Initiative (MCI) tracking software on U.S.-based employee computers. The tool captures:
- Mouse movements
- Keystrokes
- Clicks
- Occasional snapshots of screen content
The software runs on work-related apps and websites. According to internal memos, the purpose is to improve AI models in areas where they struggle to replicate human-computer interactions, specifically mentioning "choosing from dropdown menus and using keyboard shortcuts."
How the Data Will Be Used
Meta spokesperson Andy Stone confirmed MCI data will be used for model training only, not for performance assessments. The company states safeguards are in place to protect "sensitive content," though specific exclusions aren't detailed.
Stone explained: "If we're building agents to help people complete everyday tasks using computers, our models need real examples of how people actually use them — things like mouse movements, clicking buttons, and navigating dropdown menus."
Broader AI Workforce Context
This initiative is part of Meta's "Agent Transformation Accelerator" (ATA), previously called "AI for Work." CTO Andrew Bosworth described the vision as "one where our agents primarily do the work and our role is to direct, review and help them improve."
Meta is simultaneously:
- Planning to lay off 10% of its global workforce starting May 20
- Creating a new Applied AI (AAI) engineering team
- Transferring "strong" software engineers into AAI
- Exhorting staff to use AI agents for coding and other tasks
- Wiping out distinctions between certain job functions in favor of "AI builder" titles
The company aims to build AI agents that can "perform the bulk of the work to build, test and ship future products and infrastructure at Meta."
📖 Read the full source: HN AI Agents
👀 See Also

OpenClaw contributor criticizes project's focus on pixel-perfect parity over modern features
A Reddit post from r/openclaw details how a contributor's PR addressing resolution scaling and high-refresh-rate support was rejected for deviating from the original engine's visual constraints, sparking debate about the project's direction.

Claude Code Opus Fails with Rate Limit Error Despite Available Weekly Capacity
A Claude Max subscriber reports that Claude Code Opus returns 'API Error: Rate limit reached' even though their usage dashboard shows 97% of their weekly 'All models' capacity remains unused. The issue occurs specifically in Claude Code while Opus works normally on claude.ai from the same account.

MCP vs Skills Debate: Understanding the Roles and the Real Problem of Context Rot
A Reddit post clarifies that MCP provides tools, authentication, and context steering for AI agents, while Skills are reusable prompts that define agent behavior. The author argues both are needed and identifies context rot as a critical issue where agents forget instructions.

Why One Developer Leaves AI Co-Author Tags in Commits
A developer explains why they deliberately include 'Co-Authored-by: Claude' in their Git commits, comparing it to EXIF data in photography and discussing the challenges of surgical AI-assisted code changes.