This is the inevitable consequence of the ‘cloud-telemetry-first’ approach to AI developer tools. If your AI coding assistants or workflow agents are logging your terminal history, active files, or screen activity back to a centralized cloud database for ‘orchestration’ or ‘training,’ you have essentially installed corporate spyware. It doesn’t matter if it’s Meta, Microsoft, or a startup—a single misconfigured pipeline or data breach will expose trade secrets, API keys, and private credentials. AI agents must have hard local boundaries. Tool execution (reading files, executing shell commands, querying local databases) must happen entirely locally under a zero-knowledge architecture, and every single execution must require explicit user-consent dialogs. Sending execution telemetry back to the cloud is a massive security hazard that corporations are only beginning to realize.
Seems like a great time to realize you work at one of the worst companies in the world, and leak all that discovered data to the press…
They won’t. It is a golden cage. Shit ton of money and if they do, it won’t be the exodus you expect it to be. Source: ex-colleagues in similar companies.
Haha so true, especially after your best friend just got laid off ;)
I’m just imagining the keylogs for meta video editors looking like pages upon pages of
Lklk⇧cllllkjk⇧cvalk⇧clllllllkjjk⇧cv…
Man, I know Meta is too big to fail and all that, but this really reads like the company is falling apart…
