Tesla App Code Points to Cabin-Camera Driver Check for FSD

Strings buried in Tesla's latest app build describe a cabin-camera identity check that would confirm an authorized driver before letting Full Self-Driving engage.

3 min read
Tesla App Code Points to Cabin-Camera Driver Check for FSD

AUSTIN, Texas — Tesla appears to be building a new layer of access control for Full Self-Driving, one that would use the in-car cabin camera to confirm who is behind the wheel before the system will turn on. Code uncovered in the company's latest iOS app update describes a driver-identity check that blocks FSD and surfaces a failure message when the face in the seat does not match an authorized profile.

The findings come from a decompile of Tesla app version 4.58.5, built June 27, surfaced by an account that tracks new releases of the Tesla and Robotaxi apps. Two strings stand out: fsdIdentityCheckFailedTitle and showFsdIdentityCheckFailedDialog. Together they sketch a flow in which the cabin camera performs an identity check and, on a mismatch, refuses to engage FSD and throws an error dialog to the phone.

From Attention Monitoring To Identity Gate

This would not come out of nowhere. Tesla first activated cabin-camera driver monitoring in 2021 and has steadily expanded what the camera watches for, from drowsiness to eye and head position. Since FSD v12.4 in 2024, the camera above the rearview mirror has been the primary attention monitor, tracking a driver's face and eyes rather than leaning on steering-wheel torque. That same hardware now underpins a growing share of Tesla's autonomy stack, which recently passed 10 million vehicles in its self-driving fleet.

An identity check is a different job than an attention check. Attention monitoring asks whether the driver is watching the road. Identity verification asks whether this specific person is allowed to switch the system on at all, a permission gate rather than a safety nag. As Electrek noted in its report on the app code, that distinction is what makes the feature notable.

Tesla App Code Points to Cabin-Camera Driver Check for FSD — additional image

Why Tesla Would Want It

The clearest use case is access control. With FSD now sold as a subscription tied to an account, matching activation to an authorized profile keeps a paid feature locked to the right person. That matters for rentals, shared and fleet vehicles, and for preventing teen or unauthorized drivers from flipping on a driver-assistance system without permission.

There is also a robotaxi angle. Tesla's driverless ambitions lean heavily on the cabin camera, and matching the person in the seat to the person who booked the ride is exactly the kind of check a ride-hailing fleet needs as it expands, following the recent Miami robotaxi launch that opened a third state.

Code Today, Feature Tomorrow

The usual caveat applies: these are strings in an app build, not a shipped feature. App code often precedes a public rollout by weeks or months, and a live version would also require a matching vehicle firmware update, since the app is only half of the equation. The cabin camera is a standard RGB sensor rather than an infrared depth system, so it is better suited as a permission layer than a hardened biometric lock.

Still, the direction is telling. Tesla keeps finding new uses for the sensor suite already sitting inside every recent car, turning a camera that once only checked for drowsiness into a flexible tool for security, personalization and fleet management. If the identity check ships, it would be another step toward a future in which the car knows exactly who you are the moment you sit down, and tailors what it will do accordingly.