Tesla released Full Self-Driving v14.2.1.25 on Friday night to Early Access Program (EAP) members. It came as a surprise, as it was paired with the release of the Holiday Update.

We were able to go out and test it pretty extensively on Saturday, and the changes Tesla made from the previous version were incredibly impressive, especially considering it seemed to excel where it last came up short.

Tesla supplements Holiday Update by sneaking in new Full Self-Driving version

With Tesla Full Self-Driving v14.2.1, there were some serious regressions. Speed Profiles were overtinkered with, causing some modes to behave in a strange manner. Hurry Mode was the most evident, as it refused to go more than 10 MPH over the speed limit on freeways.

It would routinely hold up traffic at this speed, and flipping it into Mad Max mode was sort of over the top. Hurry is what I use most frequently, and it had become somewhat unusable with v14.2.1.

It seemed as if Speed Profiles should be more associated with both passing and lane-changing frequency. Capping speeds does not help as it can impede the flow of traffic. When FSD travels at the speed of other traffic, it is much more effective and less disruptive.

With v14.2.1.25, there were three noticeable changes that improved its performance significantly: Speed Profile refinements, lane change confidence, and Speed Limit recognition.

🚨 Many of you asked us to test highway driving with Tesla Full Self-Driving v14.2.1.25. Here’s what we noticed:

✅ Speed Profiles are significantly improved. Hurry Mode is no longer capped at 10 MPH over the speed limit, and now travels with the flow of traffic. This is much… pic.twitter.com/48ZCGbW0JO

— TESLARATI (@Teslarati) December 13, 2025

Speed Profile Refinement

Speed Profiles have been significantly improved. Hurry Mode is no longer capped at 10 MPH over the speed limit and now travels with the flow of traffic. This is much more comfortable during highway operation, and I was not required to intervene at any point.

With v14.2.1, I was sometimes assisting it with lane changes, and felt it was in the wrong place at the wrong time more frequently than ever before.

However, this was one of the best-performing FSD versions in recent memory, and I really did not have any complaints on the highway. Speed, maneuvering, lane switching, routing, and aggressiveness were all perfect.

Lane Changes

v14.2.1 had a tendency to be a little more timid when changing lanes, which was sort of frustrating at times. When the car decides to change lanes and turn on its signal, it needs to pull the trigger and change lanes.

It also changed lanes at extremely unnecessary times, which was a real frustration.

There were no issues today on v14.2.1.25; lane changes were super confident, executed at the correct time, and in the correct fashion. It made good decisions on when to get into the right lane when proceeding toward its exit.

It was one of the first times in a while that I did not feel as if I needed to nudge it to change lanes. I was very impressed.

Speed Limit Recognition

So, this is a complex issue. With v14.2.1, there were many times when it would see a Speed Limit sign that was not meant for the car (one catered for tractor trailers, for example) or even a route sign, and it would incorrectly adjust the speed. It did this on the highway several times, mistaking a Route 30 sign for a 30 MPH sign, then beginning to decelerate from 55 MPH to 30 MPH on the highway.

This required an intervention. I also had an issue leaving a drive-thru Christmas lights display, where the owners of the private property had a 15 MPH sign posted nearly every 200 yards for about a mile and a half.

The car identified it as a 55 MPH sign and sped up significantly. This caused an intervention, and I had to drive manually.

It seems like FSD v14.2.1.25 is now less reliant on the signage (maybe because it was incorrectly labeling it) and more reliant on map data or the behavior of nearby traffic.

A good example was on the highway today: despite the car reading that Route 30 sign and the Speed Limit sign on the center screen reading 30 MPH, the car did not decelerate. It continued at the same speed, but I’m not sure if that’s because of traffic or map data:

🚨 We listened to and read a lot of you who had a complaint of Tesla Full Self-Driving v14.2.1 incorrectly reading Speed Limit signs

This appears to be resolved in v14.2.1.25.

Here’s a breakdown: pic.twitter.com/TEP03xrMbt

— TESLARATI (@Teslarati) December 13, 2025

Advertisement

-->

A Lone Complaint

Tesla has said future updates will include parking improvements, and I’m really anxious for them, because parking is not great. I’ve had some real issues with it over the past couple of months.

Today was no different:

🚨 My lone complaint with my drive on Tesla FSD v14.2.1.25 was this strange parking instance.

FSD swung out wide to the left to pull into this spot and this is where it seemed to be stumped. I gave it about 10 seconds after the car just stopped moving for it to make some… https://t.co/ZEkhTHOihG pic.twitter.com/TRemXu5DLf

— TESLARATI (@Teslarati) December 13, 2025

Advertisement

-->

Full Self-Driving v14.2.1.25 is really a massive improvement over past versions, and it seems apparent that Tesla took its time with fixing the bugs, especially with highway operation on v14.2.1.

Tesla Optimus dramatically collapsed after a teleoperator mishap at the company’s “Future of Autonomy Visualized” event in Miami this past weekend.

It seemed blatantly obvious that whoever was controlling the Optimus robot from behind the scenes did not disconnect their ability to manipulate its movements, then left the controls, causing Optimus to collapse.

A video captured at the event shows Optimus doing a movement similar to taking a headset off, likely what the teleoperator uses to hear guest requests and communicate with other staff:

🚨 Tesla Optimus mishap at the Miami event

To be fair, don’t we all want to do this around the Holidays? pic.twitter.com/EJ5QKenqQd

— TESLARATI (@Teslarati) December 8, 2025

Advertisement

-->

After the headset removal motion was completed, Optimus simply collapsed backward, making for an interesting bit of conversation. While it was a mishap, it was actually pretty funny to watch because of the drama displayed by the robot in the situation.

This was obviously a mistake made by the teleoperator, and does not appear to be a spot where we can put any sort of blame on Optimus. It would have likely just stood there and waited for controls to resume if the teleoperator had disconnected from the robot correctly.

However, details are pretty slim, and Tesla has not announced anything explaining the situation, likely because it seems to be a pretty face-value event.

Tesla Optimus shows off its newest capability as progress accelerates

The Tesla Optimus program has been among the most hyped projects that the company has been working on, as CEO Elon Musk has extremely high hopes for what it could do for people on Earth. He has said on several occasions that Optimus should be the most popular product of all time, considering its capabilities.

Obviously, the project is still a work in progress, and growing pains are going to be part of the development of Optimus.

In its development of Optimus Gen 3, Tesla has been working on refining the forearm, hand, and fingers of Optimus, something that Musk said is extremely difficult. However, it’s a necessary step, especially if its capabilities will not be limited by hardware.

All in all, Optimus has still been a very successful project for Tesla, especially in the early stages. The company has done an excellent job of keeping Optimus busy, as it helps with serving customers at events and the Tesla Diner, and is also performing tasks across the company’s manufacturing plants.

On Thursday, Tesla CEO Elon Musk said that Full Self-Driving v14.2.1 would enable texting and driving “depending on [the] context of surrounding traffic.”

Tesla CEO Elon Musk announces major update with texting and driving on FSD

We decided to test it, and our main objective was to try to determine a more definitive label for when it would allow you to grab your phone and look at it without any nudge from the in-car driver monitoring system.

I’d also like to add that, while Tesla had said back in early November that it hoped to allow this capability within one to two months, I still would not recommend you do it. Even if Tesla or Musk says it will allow you to do so, you should take into account the fact that many laws do not allow you to look at your phone. Be sure to refer to your local regulations surrounding texting and driving, and stay attentive to the road and its surroundings.

The Process

Based on Musk’s post on X, which said the ability to text and drive would be totally dependent on the “context of surrounding traffic,” I decided to try and find three levels of congestion: low, medium, and high.

I also tried as best as I could to always glance up at the road, a natural reaction, but I spent most of my time, during the spans of when it was in my hand, looking at my phone screen. I limited my time looking at the phone screen to a few seconds, five to seven at most. On local roads, I didn’t go over five seconds; once I got to the highway, I ensured the vehicle had no other cars directly in front of me.

Also, at any time I saw a pedestrian, I put my phone down and was fully attentive to the road. I also made sure there were no law enforcement officers around; I am still very aware of the law, which is why I would never do this myself if I were not testing it.

I also limited the testing to no more than one minute per attempt.

I am fully aware that this test might ruffle some feathers. I’m not one to text and drive, and I tried to keep this test as abbreviated as possible while still getting some insight on how often it would require me to look at the road once again.

The Results

Low Congestion Area

I picked a local road close to where I live at a time when I knew there would be very little traffic. I grabbed my phone and looked at it for no more than five seconds before I would glance up at the road to ensure everything was okay:

In full: the Low Congestion Area pic.twitter.com/6DqlBnekPn

— TESLARATI (@Teslarati) December 4, 2025

Looking up at the road was still regular in frequency; I would glance up at the road after hitting that five-second threshold. Then I would look back down.

I had no nudges during this portion of the test. Traffic was far from even a light volume, and other vehicles around were very infrequently seen.

Medium Congestion Area

This area had significantly more traffic and included a stop at a traffic light. I still kept the consecutive time of looking at my phone to about five seconds.

I would quickly glance at the road to ensure everything was okay, then look back down at my phone, spending enough time looking at a post on Instagram, X, or Facebook to determine what it was about, before then peeking at the road again.

There was once again no alert to look at the road, and I started to question whether I was even looking at my phone long enough to get an alert:

In full: the Medium Congestion Area pic.twitter.com/gnhIfBVe6Q

— TESLARATI (@Teslarati) December 4, 2025

Based on past versions of Full Self-Driving, especially dating back to v13, even looking out the window for too long would get me a nudge, and it was about the same amount of time, sometimes more, sometimes less, I would look out of a window to look at a house or a view.

High Congestion Area

I decided to use the highway as a High Congestion Area, and it finally gave me an alert to look at the road.

As strange as it is, I felt more comfortable looking down at my phone for a longer amount of time on the highway, especially considering there is a lower chance of a sudden stop or a dangerous maneuver by another car, especially as I was traveling just 5 MPH over in the left lane.

This is where I finally got an alert from the driver monitoring system, and I immediately put my phone down and returned to looking at the road:

In full: the High Congestion Area pic.twitter.com/K9rIn4ROvm

— TESLARATI (@Teslarati) December 4, 2025

Once I was able to trigger an alert, I considered the testing over with. I think in the future I’d like to try this again with someone else in the car to keep their eyes on the road, but I’m more than aware that we can’t always have company while driving.

My True Thoughts

Although this is apparently enabled based on what was said, I still do not feel totally comfortable with it. I would not ever consider shooting a text or responding to messages because Full Self-Driving is enabled, and there are two reasons for that.

The first is the fact that if an accident were to happen, it would be my fault. Although it would be my fault, people would take it as Tesla’s fault, just based on what media headlines usually are with accidents involving these cars.

Secondly, I am still well aware that it’s against the law to use your phone while driving. In Pennsylvania, we have the Paul Miller Law, which prohibits people from even holding their phones, even at stop lights.

I’d feel much more comfortable using my phone if liability were taken off of me in case of an accident. I trust FSD, but I am still erring on the side of caution, especially considering Tesla’s website still indicates vehicle operators have to remain attentive while using either FSD or Autopilot.

Check out our full test below: