Meta pulls WIRED-identified face-recognition code from smart glasses’ Meta AI app

Meta has removed the face-recognition code WIRED identified from the latest version of its Meta AI companion app for its smart glasses. In other words: the feature WIRED traced is no longer in the current app build.

Meta is not saying why it deleted the code, and it is also not saying whether the face-recognition functionality will come back. For decision-makers, that combination matters more than the deletion itself. When a company removes code without public explanation, it signals uncertainty about compliance, user expectations, or internal product readiness, even if Meta never confirms which one.

To understand what is at stake, you have to remember how wearable intelligence products are judged. Smart glasses are not just “another app.” They are sensors strapped to your face and connected to everything around you. That makes features like face recognition especially sensitive because they can move from “convenient” to “pervasive surveillance” in the eyes of regulators, courts, and consumers, often faster than product teams can respond. Even if a feature is narrowly scoped, the mere presence of face recognition in a glasses ecosystem can trigger intense scrutiny about consent, data handling, and lawful use.

Wired’s report functions as an external forcing mechanism. Once a credible outlet points to specific code or a capability in a live product, companies face a choice: clarify and justify, patch and constrain, or remove. Here, Meta chose removal. The company will not confirm the reason or timeline, which leaves the market to infer, and in this category, inference is usually unforgiving.

From a governance perspective, this is the kind of event that shows up later in board discussions about risk management. The board question becomes: if something like face recognition was present and then vanished, what does that say about the org’s ability to anticipate regulatory exposure and public scrutiny? It also raises a related question for leaders at any company building AI-powered vision tools: are your safeguards tied to the product experience, or are they only tied to marketing language? WIRED identified code. Meta removed code. That sequence implicitly reframes how “what’s shipped” is evaluated.

There is also a competitive second-order effect. AR and wearable companies compete on features, but they also compete on trust, compliance readiness, and speed of iteration. If Meta retracts face recognition quietly, that can slow the category’s adoption of similar capabilities because competitors cannot rely on peers to normalize the risk. Even teams that are not touching face recognition may have to invest in audits, documentation, and clearer user controls simply to reduce the chance that an investigative report forces emergency edits.

For regulators, the lack of an explanation does not end the story. Removing code does not automatically mean a regulator will view the prior behavior as harmless, especially if the capability existed in a recent version and the company cannot articulate the compliance reasoning. In many privacy regimes, regulators care not only about current state but also about what happened, when it happened, and how the company handled user data. Meta’s silence creates more work for compliance teams, both inside Meta and at partners integrating Meta AI into their own experiences.

For investors and operators, the practical takeaway is that product risk in AI vision is not just about model accuracy. It is about governance, user expectations, and the public record. A feature can effectively become “removed from existence” for the user, but the organizational trail still matters for audits, partner relationships, and future approvals. In this case, the headline fact is clear: the WIRED-identified face-recognition code is gone from the latest Meta AI app companion to Meta’s smart glasses, and Meta has not said why or whether it will return.

The strategic stake for peers is straightforward. If you build AI-enhanced hardware or apps that perceive faces, your compliance and product roadmap can be overturned by external reporting and internal prioritization decisions, even without a formal announcement. The market is watching how quickly companies adapt under scrutiny, and how transparent they are when they choose to delete capability instead of defend it. For leaders, the question is no longer “can we build it?” It is “can we justify it, constrain it, and sustain it long enough to matter?”