Tesla FSD V12.4.1 Goes Out: Exploring No Nags and More [Video]

Tesla will now alert you when vision-monitoring isn't being used

@WifeDirtyTesla

With FSD V12.4.1 finally beginning its rollout to select customers as of last night. You’re probably wondering exactly how nags will – or won’t – work for the updated and much-hyped update.

No Steering Wheel Nags

Tesla’s current implementation of no steering wheel nags on V12.4.1 is pretty simple and straightforward. As long as you’re paying attention and looking at the road, you won’t be required to touch the steering wheel. You’ll see a green dot on the screen, letting you know that the enhanced driver monitoring system (DMS) and Vision-Based Attention Monitoring (VBAM) are active.

On the Model S and X, the green dot is on the instrument cluster screen, immediately next to the blue FSD/AP wheel icon. On the Model 3 and Model Y (and Cybertruck, in the future), the green dot indicator is on the top left of the screen, in between the battery indicator and the blue FSD/AP wheel.

However, there are some restrictions baked into this initial implementation. Your eyes cannot be obscured or occluded from the cabin camera. This means that legacy vehicles are ineligible for the new VBAM, along with anyone who installs a physical camera cover for privacy or other reasons.

For the privacy-conscious folks, Tesla has mentioned that cabin camera imagery will not leave the vehicle itself unless you enable data sharing, which is optional. Cabin camera imagery is also not available to view via the API, so third-party integrations cannot view your cabin camera either.

The green dot on the center display

Whole Mars Catalog

Restrictions

There are some other catches too. The cabin camera is currently unable to see through sunglasses due to the polarization. The car will display “Attention monitoring unavailable, sunglasses use detected” on the screen. This could change in the future as Tesla figures out how to best take advantage of its cabin cameras. However, it can see through regular glasses just fine – so eyeglass wearers, rejoice!

Attention monitoring unavailable, sunglasses use detected

Vehicles that do not have IR lights in the cabin will also not be able to take advantage of VBAM at night – as the cameras in vehicles without IR lights are unable to see at night. Tesla does offer a refit for vehicles to upgrade to IR-capable cameras – put in a service ticket if you’re interested through the Service Menu on the app.

If it cannot find your eyes due to any of these restrictions, the green light will not come on, and the regular wheel nags that you are used to will continue.

Warnings and Suspensions

If VBAM determines that you’re not paying attention – initially a screen warning will appear, telling you to pay attention to the road. This can be dismissed quickly by just reverting your attention to the road ahead of you. You won’t have to touch the steering wheel to dismiss the nag.

However, if you continue to not pay attention and the DMS detects improper usage, you will receive an Autopilot Strikeout, and FSD will disengage. Before a Strikeout occurs, there will be multiple auditory and visual warnings, ensuring you have a few moments to bring your attention back to supervising FSD.

You can receive up to 5 Strikeouts before the FSD becomes suspended. One strikeout will be lifted per 7-day period in which you do not receive a Strikeout. If you hit 5 Strikeouts, it could be up to 5 weeks before you clear all of them! If you receive another Strikeout within that 7-day period after an initial Strikeout, the 7-day period is reset.

Other Changes

Elon Musk has mentioned that V12.4 was supposed to be focused on user comfort, by reducing hard acceleration and braking. According to Musk, it should have a 5-10x improvement between user disengagements.

Early Access owners have mentioned that 12.4 tends to be more assertive and less hesitant when it comes to intersections, stop signs, and parking lots. Owners have also noticed improvements in the “lane dancing”, where FSD V12.3 would stray in between lanes for too long while changing lanes.

Of additional note is that Vision Autopark is slightly faster – but this is the same Vision Autopark speed increase that rolled out to customers who have already received the Spring Update. For everyone else, expect a 2-3x improvement in how fast Vision Autopark changes directions, and how fast it maneuvers in general. As of the Spring Update, it can now park in even tighter spaces.

Another much-appreciated feature is the ability to temporarily increase the sensitivity of Autowipers. As many have experienced, the Autowiper functionality doesn’t always work well. However, with the Spring Update, you can now temporarily increase the sensitivity of the Autowiper system by tapping once on the wiper stalk (or button on stalkless vehicles).

Missed Features

Sadly, some previously announced features were missed out on in this release of FSD V12.4.1. Namely, the key features of Banish Autopark and Park Seek. For the time being, users will still have to disengage FSD and then engage Autopark once they find their parking spot.

Banish Autopark, or “Reverse Summon” was thought to arrive in V12.4 as part of the comfort update according, allowing you to choose a parking spot type preference, exit the vehicle, and then have the car park itself.

Additionally, Park Seek – which would allow FSD to automatically find a parking spot in a parking lot, and then engage Autopark automatically, was initially a confirmed feature, but is not present in this release.

Finally, Hand Gesture recognition was supposed to come in an update “later in May” – but given that FSD V12.4 has missed previous deadlines – no surprise to people familiar with the “2 week policy” – there is no confirmation yet if that feature has made it into this build. It is very possible that the employee in question may have been referring to V12.5 – which is also expected to bring vehicle-to-fleet communication.

Expected Wide Release

Given that it just rolled out to employees yesterday, and then to “OG” FSD Beta owners today, we could expect 2024.15.5 – the version that contains V12.4.1 – to hopefully continue rolling out to customers next week. Everyone with an update under 2024.15.5 - so users on 2024.3.25, 2024.8.9, and 2024.14.11 – should be eligible to receive this update. The very few vehicles already on 2024.20 with the Adaptive Headlights functionality will have to wait a bit longer!

Follow

Follow

Follow

Tesla’s Robotaxi Easter Egg: Surprise Tip

BLKMDL3

Tesla has always embraced whimsy in its software, packing it with playful Easter eggs and surprises. From transforming the on-screen car into James Bond’s submarine to the ever-entertaining Emissions Testing Mode and the fan-favorite Rainbow Road, these hidden features have become a signature part of Tesla’s software.

Of course, launching a new product like Robotaxi wouldn’t be complete without a fun little easter egg of its own. The end-of-ride screen in the Robotaxi app presents a familiar option “Leave a tip.”

For anyone pleased with their Robotaxi ride, they may be tempted to leave a tip. However, tapping the button presents our favorite hedgehog instead of a payment screen.

The app displays a message, alongside the familiar Tesla hedgehog, that simply states “Just kidding.”

While it's a fun prank, it’s also a nod to what Tesla really wants to do. They want to reinforce the economic advantage of an autonomous Robotaxi Network. Without a driver, there is simply no need to tip. The gesture is playful, but it’s a reminder of what Tesla’s real aim is here.

Had to been done lol https://t.co/SnZ3afXXzB

— Elon Musk (@elonmusk) June 22, 2025

Even Elon is in on the joke. It is a small detail, but it’s all about those small details with Tesla.

Follow

Follow

Follow

First Recorded Tesla Robotaxi Intervention: UPS Truck Encounter [VIDEO]

@BLKMDL3 on X

Over the last few days, we’ve seen some exceptionally smooth performance from the latest version of FSD on Tesla’s Robotaxi Network pilot. However, the entire purpose of an early access program with Safety Monitors is to identify and learn from edge cases.

This week, the public saw the first recorded instance of a Safety Monitor intervention, providing a first look at how they’re expected to stop the vehicle.

The event involved a complex, low-speed interaction with a reversing UPS truck. The Safety Monitor intervened to stop the Robotaxi immediately, potentially avoiding a collision with the delivery truck. Let’s break down this textbook case of real-world unpredictability.

The Intervention [VIDEO]

In a video from a ride in Austin, a Robotaxi is preparing to pull over to its destination on the right side of the road, with its turn signal active. Ahead, a UPS truck comes to a stop. As the Model Y begins turning into the spot, the UPS truck, seemingly without signaling, starts to reverse. At this point, the Safety Monitor stepped in and pressed the In Lane Stop button on the main display, bringing the Robotaxi to an immediate halt.

This is precisely why Tesla has employed Safety Monitors in this initial pilot. They are there to proactively manage ambiguous situations where the intentions of other drivers are unclear. The system worked as designed, but it raises a key question: What would FSD have done on its own? It’s not clear whether the vehicle saw the truck backing up, or what it would do when it finally detected it. It’s also unclear whether the UPS driver recognized that the Robotaxi was pulling into the same spot at the exact same time.

It’s possible this wouldn’t result in a collision at all, but the Safety Monitor did the right thing by stepping in to prevent a potential collision, even one at low speed. Any collision just a few days after the Robotaxi Network launch could result in complications for Tesla.

Who Would Be At Fault?

This scenario is a classic edge case. It involves unclear right-of-way and unpredictable human behavior. Even for human drivers, the right-of-way here is complicated. While a reversing vehicle often bears responsibility, a forward-moving vehicle must also take precautions to avoid a collision. This legal and practical gray area is what makes these scenarios so challenging for AI to navigate.

Would the Robotaxi have continued, assuming the reversing truck would stop?

Or would it have identified the potential conflict and used its own ability to stop and reverse?

Without the intervention, it’s impossible to say for sure. However, crucial context comes from a different clip involving, surprisingly, another UPS delivery truck.

A Tale of Two Trucks

In a separate video posted on X, another Robotaxi encounters a remarkably similar situation. In that instance, as another UPS delivery truck obstructs the path forward, the Robotaxi comes to a stop to let its two passengers out just a few feet from their destination.

Once they depart, the Robotaxi successfully reverses and performs a three-point turn to extricate itself from a tight spot. That was all done without human intervention, by correctly identifying the situation. 

This second clip is vital because it proves that the Robotaxi's FSD build has the underlying logic and capability to handle these scenarios. It can, and does, use reverse to safely navigate complex situations.

RUN THE CLIP!

UPS Truck vs Tesla Robotaxi https://t.co/GLc86BS5bc pic.twitter.com/O2c8c2KRB2

— Bradford Ferguson (@bradsferguson) June 25, 2025

A Valuable Data Point

Far from being a failure, this first intervention should be seen as a success for Tesla’s safety methodology. It shows the safety system is working, allowing monitors to mitigate ambiguous events proactively.

More importantly, this incident provides Tesla’s FSD team with an invaluable real-world data point.

By comparing the intervened ride with the successful autonomous one, Tesla’s engineers can fine-tune FSD’s decision-making, which will likely have a positive impact on its edge case handling in the near future.

This is the purpose of a public pilot — to find the final edge cases and build a more robust system, one unpredictable reversing truck at a time.

Follow

Follow

Follow