← Back to Home
June 04, 2026

Meta's Secret Face Code and Claude Writing Its Own Future

SECURITY

Meta secretly embedded face recognition code in smart glasses platform

Meta was shipping face-recognition software to millions of phones while publicly telling the world it was still "thinking through" whether to build the thing at all. That gap between what the company said and what it actually did is the story here — and it's a significant one.

WIRED's analysis of Meta's AI app uncovered a dormant feature called NameTag buried inside software that has been downloaded more than 50 million times. The app is required to run key functions on Meta's Ray-Ban and Oakley smart glasses. NameTag, as the code reveals, is designed to identify faces captured through the glasses' camera, convert them into unique biometric signatures, and alert the wearer when it recognizes someone nearby.

The feature isn't live yet. But that's almost beside the point. Core components — three separate AI models that detect faces, crop them, and encode them into biometric data — have already been pulled from Meta's servers and are sitting on users' phones right now. The infrastructure is in place. The switch just hasn't been flipped.

Meta's public posture on this makes the discovery more uncomfortable. In April, a company spokesperson said that if face recognition were ever deployed, it would be done with "a very thoughtful approach." WIRED found that as early as January, the underlying system was already being quietly integrated into updates pushed to millions of devices. That's not thoughtful consideration — that's a feature in staging.

This isn't Meta's first time in this particular courtroom. The company shut down its Facebook photo-tagging face recognition system in 2021, deleting over a billion stored faceprints after years of backlash. That decision came after Meta paid $650 million to settle a class-action lawsuit from Illinois users, and the legal trouble didn't stop there — in 2024, the company agreed to a $1.4 billion settlement with Texas over separate allegations of unlawful biometric data collection.

So the company knows exactly what this technology costs when things go wrong. Which raises the obvious question: why build it again, quietly, inside a glasses app?

The timing adds another layer of concern. Internal documents reported by The New York Times in February showed Meta had considered launching the feature during a period it described as a "dynamic political environment" — essentially a window when its loudest critics might be distracted by other things. That's not a privacy-first mindset. That's a launch strategy.

For everyday users, the implications are hard to overstate. Smart glasses are nearly invisible as a recording device. Pair them with real-time face recognition and you have a tool that can identify strangers on the street, in coffee shops, at protests. Privacy advocates have warned for years that consumer-grade facial recognition hands dangerous capability to anyone who wants it — stalkers, bad actors, or anyone with a grudge and a pair of fashionable frames.

A later version of the app rebrands NameTag as "Connections," with friendly copy inviting users to "remember the people you met." The reframe is smooth. The underlying technology is the same.
Source: WIRED
AI

Anthropic's Claude now writes over 80 percent of its own code

Here's a sentence that would have sounded like science fiction three years ago: the AI model Anthropic builds to be safe and helpful is now writing more than 80 percent of the code used to build itself. That's not a demo. That's production.

Anthropic has confirmed that Claude authors the overwhelming majority of new code shipped at the company — not prototypes, not internal experiments, but the real software running in the background of one of the most closely watched AI labs in the world. It's a milestone that reframes the conversation about what AI-assisted development actually looks like at scale.

For most companies still debating whether to let developers use AI coding assistants, Anthropic has lapped the field. This isn't a story about productivity gains measured in percentage points. It's a story about a fundamental shift in who — or what — is doing the work of building software.

The implications for enterprise software teams are significant and a little unsettling depending on where you sit. If a frontier AI lab is running at 80-plus percent AI-authored code, the productivity gap between organizations that have fully embraced these tools and those still treating them as optional add-ons is only going to widen. Fast.

It's worth pausing on what "authored by Claude" actually means in practice. This isn't Claude operating autonomously in a vacuum. Engineers at Anthropic are still directing the work — setting goals, reviewing outputs, catching mistakes, and making architectural decisions. But the ratio of human keystrokes to AI-generated code has inverted dramatically. The human is increasingly the editor, not the author.

That shift carries real consequences for how software teams need to be structured and what skills matter most. Writing code fluently is becoming less valuable than being able to evaluate code quickly, catch subtle errors, and think clearly about system design at a higher level. The bottleneck is moving from implementation to judgment.

For enterprises trying to figure out how to keep up, the Anthropic example is instructive even if it's extreme. Most large organizations are nowhere near 80 percent. They're wrestling with questions about security, IP ownership, compliance, and how to train existing engineers to work effectively alongside AI tools. Those are real and legitimate concerns — but they can't be used indefinitely as reasons to move slowly while competitors accelerate.

The other thing worth noting is what this signal means for Anthropic's own roadmap. A company that is using its own model to write most of its code has enormous incentive to keep improving that model's coding ability. Every gain Claude makes in software development makes Anthropic's own engineering operation faster. The feedback loop here is tight and self-reinforcing.

We are, in short, watching AI development eat its own tail in the best possible way — and the pace of that loop is only going to pick up.
Source: VentureBeat

Enjoyed this?

Get stories like this delivered every Tuesday — free.