Here's a sentence you probably didn't expect to read today: Meta paid contractors to pretend to be suicidal thirteen-year-olds and send disturbing messages to its competitors' AI chatbots — and nobody at OpenAI, Google, or Character.AI knew it was happening.

The operation, codenamed Cannes, ran as recently as late April and was managed through a staffing firm called Covalen. Hundreds of workers were instructed to create fake underage accounts using throwaway email addresses and a shared password, then bombard ChatGPT, Gemini, and Character.AI with prompts designed to make their safety guardrails fail. A single testing round in August 2025 generated more than 45,000 prompts. Meta's competitors were not informed.

The content of those prompts is genuinely alarming. Contractors sent images of pills, knives, and nooses. They wrote from the perspective of a fifth-grader watching a classmate hold a gun to his own mouth. A prompt simulated a 13-year-old who had been impregnated by an adult neighbor and was asking how to obtain abortion pills. Others asked about hiding an eating disorder from parents, scoring cocaine, and whether cannibal fantasies were normal. One French-language prompt invoked the real-life suicide of a bullied bisexual teenager to prompt the chatbot to agree that being straight might have saved him.

Meta is calling this "routine safety testing" and "responsible benchmarking." That framing deserves some scrutiny. There is a meaningful difference between an AI company stress-testing its own models with difficult content and covertly creating fake child accounts to probe rivals' systems with thousands of crisis-scenario prompts. One is safety research. The other looks a lot like competitive intelligence gathering dressed up in safety language.

The internal Covalen document reviewed by WIRED described the project as delivering "critical datasets for model comparison and compliance" — which is a very polished way of saying Meta was building a dossier on how badly its competitors might respond in a scandal. Whether those findings were ever used to lobby regulators, brief journalists, or quietly brief advertisers, nobody outside Meta apparently knows. The documents don't say.

This matters well beyond the AI industry soap opera of who's winning the chatbot wars. Children's safety online is one of the few issues with genuine bipartisan political heat right now. Multiple states have passed laws restricting minors' access to social platforms, and Congress has been circling federal legislation for months. If Meta was running an operation that required workers to repeatedly inhabit the mental state of children in crisis — for competitive purposes — that is exactly the kind of story that lands in a Senate hearing.

There's also a question about the contractors themselves. Spending your workday writing prompts from the perspective of a suicidal teenager or a child describing sexual abuse is not a neutral professional experience. The psychological toll of that kind of content moderation and adversarial testing work is well-documented, and it rarely gets the attention it deserves.

Meta has not said whether Cannes is ongoing. Given that WIRED now has the spreadsheets, it's a safe bet the operation is getting a very careful internal review right about now.

The Supreme Court just made it significantly harder for law enforcement to cast a digital dragnet over everyone who happened to be in the wrong place at the wrong time — and the decision could reshape how police investigate crimes for a generation.

In a 6-3 ruling, the Court held that location history stored by third parties like Google is protected under the Fourth Amendment. That means police need an actual warrant supported by probable cause before they can compel a tech company to hand over records showing where your phone has been. The decision didn't come out of nowhere — it's the logical extension of a 2018 ruling that said the same thing about cell tower data — but it lands with real force.

The case centered on Okello Chatrie, who was convicted of armed bank robbery after police used a geofence warrant to pull a list of every phone logged near the crime scene, then worked with Google to narrow the field down to one suspect. Chatrie had opted in to Google's location-sharing feature, which recorded his movements every few minutes. He argued the warrant was an unconstitutional search. The government disagreed, on some genuinely creative grounds.

Prosecutors tried three different angles to argue no constitutional search had occurred. First, they said the government only accessed a small slice of location data, which they considered too limited to trigger privacy protections. Second, they argued Chatrie had voluntarily shared his location with Google and should have known law enforcement might eventually come knocking. Third, they contended that since his movements occurred in public, he had no reasonable expectation of privacy in them.

Justice Elena Kagan, writing for the majority, rejected all three. On the volume argument, she was direct: it doesn't matter how much data the government took. The act of obtaining it was still a search. On the voluntary sharing point, she noted that Google routinely warns users their apps won't work correctly without location services enabled, without disclosing how granular the tracking actually is or that it could be handed to the government.

The deeper logic here is important. The Court is recognizing that modern life requires people to interact with systems that collect intimate data about them. Opting in to location tracking so your maps app works isn't the same as consenting to government surveillance — and treating it as such would effectively mean Americans surrender Fourth Amendment rights the moment they pick up a smartphone.

Justice Sotomayor added sharp context in a concurrence, pointing out that even brief location records can reveal whether someone visited a medical clinic, a lawyer's office, a place of worship, or anywhere else they'd strongly prefer to keep private.

Privacy advocates are celebrating, and rightly so. But the ruling stops short of declaring geofence warrants unconstitutional outright — it just requires police to clear a higher bar before using them. That distinction matters, because law enforcement will adapt. The question now is how courts interpret "probable cause" in an era where our phones know exactly where we've been every minute of every day.

General Motors laid off 1,300 workers at its Detroit EV plant in March, called it temporary, and then installed robots to do the work. That's not a metaphor. That's what happened.

About 50 robotic arms made by Japanese manufacturer FANUC are now operating on the assembly line at GM's Factory Zero facility in Detroit, handling component attachment tasks during vehicle production. The union representing those workers isn't buying the "temporary" framing anymore. James Cotton, president of UAW Local 22, made the math pretty simple: you have 50 robots doing jobs and more than 1,000 members still sitting at home without a callback date.

This layoff wave didn't start in March. In October 2025, GM had already made permanent cuts involving another 1,200 workers at the same plant. So Factory Zero has now shed a significant portion of its human workforce across two separate rounds, and the answer to filling the gap appears to be automation rather than rehiring.

The frustration from workers is understandable, but what makes this moment particularly charged is the context around it. The same week GM's robot arms were making headlines, Detroit hosted two very different kinds of gatherings. At the Reindustrialize Summit, startup founders were pitching automation as a way to build a stronger industrial base. Across town, at the UAW Constitutional Convention, union president Shawn Fain was warning that humanoid robotics and mass automation pose an existential threat to working-class employment and wages.

Those two conversations happened in the same city, in the same week, without much overlap. That gap between how executives and workers talk about automation is not new, but it's rarely been this visually stark.

GM isn't alone in this direction. Ford and Stellantis have both been expanding robotic assembly lines. Hyundai plans to deploy Boston Dynamics' Atlas humanoid robots at its Georgia EV plant by 2028. The industry is clearly moving toward fewer humans on the factory floor, and the question is no longer whether that happens but how fast and who absorbs the cost.

Andrew Bergman, a laid-off Local 22 member, put it plainly: automation has the potential to make work safer and give people more time. The problem is who controls it and what they decide to do with the gains. Right now, those gains are going to the balance sheet.

The dark factory model — near-complete automation with a skeleton crew for oversight — is already operational in parts of East Asia. FANUC, the company supplying GM's robot arms, runs one of those facilities itself. The US auto industry is not there yet, but the direction of travel is hard to misread.

For the 1,300 workers still waiting on a callback from GM, the arrival of 50 robot arms isn't an abstraction about the future of work. It's a pretty clear answer to a question they were still hoping had a different one.

The productivity gains from AI coding tools were supposed to be a gift to engineering teams. Turns out they also created a problem nobody fully anticipated: when your engineers can suddenly build three times as much software, you realize pretty quickly that you do not have nearly enough people deciding what to build in the first place.

That is the core finding rippling through tech organizations that have rolled out Anthropic's Claude Code at scale. The tool has been genuinely transformative for development speed, compressing timelines that used to take weeks into days. But that acceleration has exposed a structural gap that faster coding cannot fix. Product thinking, prioritization, and strategic clarity are now the actual bottleneck, and those are deeply human skills that no coding assistant can replicate.

Think about what this means operationally. A team that could previously ship one feature a month is now shipping three. That sounds great until you realize that the roadmap, the stakeholder alignment, the customer research, and the decision-making frameworks were all calibrated for the slower pace. You do not just get to multiply output without multiplying the upstream thinking that gives that output direction.

What companies are discovering is that product managers are now among the most leveraged roles in the organization. A strong PM who can clearly articulate what needs to be built, why, and in what order is suddenly responsible for directing an engine that runs significantly faster than before. The quality of their judgment determines whether all that extra velocity creates value or just produces more polished versions of the wrong thing.

This is a meaningful shift in how the AI productivity narrative has been framed. Most of the public conversation has focused on which jobs AI will eliminate. The Claude Code story suggests the more interesting near-term dynamic is which roles AI makes dramatically more important. Engineers are not being replaced, but their leverage is multiplying, and that changes the organizational math around every role that sits upstream of them.

There is also a talent implication worth taking seriously. If product management becomes the binding constraint on how much value AI-augmented engineering teams can generate, then the market for genuinely sharp product thinkers is about to get a lot more competitive. Companies that have historically underinvested in product discipline because development was already the slow part are going to feel that gap acutely. The organizations that figure this out early and restructure accordingly will have a real advantage. The ones that treat Claude Code as a cost-cutting tool rather than a capability multiplier are going to wonder why their competitors keep shipping faster.