Tesla has shipped out an update for its vehicles that was caused specifically by a California lawsuit that threatened the company’s ability to sell cars because of how it named its driver assistance suite.

Tesla shipped out Software Update 2026.2.9 starting last week; we received it already, and it only brings a few minor changes, mostly related to how things are referenced.

“This change only updates the name of certain features and text in your vehicle,” the company wrote in Release Notes for the update, “and does not change the way your features behave.”

The following changes came to Tesla vehicles in the update:

• Navigate on Autopilot has now been renamed to Navigate on Autosteer
• FSD Computer has been renamed to AI Computer

Tesla faced a 30-day sales suspension in California after the state’s Department of Motor Vehicles stated the company had to come into compliance regarding the marketing of its automated driving features.

The agency confirmed on February 18 that it had taken a “corrective action” to resolve the issue. That corrective action was renaming certain parts of its ADAS.

Tesla discontinued its standalone Autopilot offering in January and ramped up the marketing of Full Self-Driving Supervised. Tesla had said on X that the issue with naming “was a ‘consumer protection’ order about the use of the term ‘Autopilot’ in a case where not one single customer came forward to say there’s a problem.”

This was a “consumer protection” order about the use of the term “Autopilot” in a case where not one single customer came forward to say there’s a problem.

Sales in California will continue uninterrupted.

— Tesla North America (@tesla_na) December 17, 2025

It is now compliant with the wishes of the California DMV, and we’re all dealing with it now.

This was the first primary dispute over the terminology of Full Self-Driving, but it has undergone some scrutiny at the federal level, as some government officials have claimed the suite has “deceptive” names. Previous Transportation Secretary Pete Buttigieg was one of those federal-level employees who had an issue with the names “Autopilot” and “Full Self-Driving.”

Tesla sued the California DMV over the ruling last week.

Tesla workers pushed back against unionization efforts at Gigafactory Berlin, and over the past few years, there has been a dramatic decrease in interest to unionize at the German plant.

Gigafactory Berlin Plant Manager André Thierig announced on Wednesday that IG Metall, the European union group, saw its share reduce from 40 to 31 percent in 2026 as employees eligible to vote on the issue. Instead, the Giga Berlin team, known as Giga United, received the most votes with more than 40 percent.

BREAKING! 🚨

IG Metall did not succeed in Giga Berlin‘s works council election earlier today. The union share was reduced from nearly 40% in 2024 to 31% in 2026!

This is a clear message by theGiga Berlin team towards an independent co-determination!

The list called Giga…

— André Thierig (@AndrThie) March 4, 2026

Thierig gave specific details in a post on X:

“IG Metall did not succeed in Giga Berlin‘s works council election earlier today. The union share was reduced from nearly 40% in 2024 to 31% in 2026! This is a clear message by the Giga Berlin team towards an independent co-determination! The list called Giga United, led by the current chairwoman, Michaela Schmitz, received the most votes with more than 40%! Good news for Giga Berlin!”

There were over 10,700 total employees who were eligible to vote, with 87 percent of them turning out to cast what they wanted. There were three key outcomes: Giga United, IG Metall, and other notable groups, with the most popular being the Polish Initiative.

The 37-seat council remains dominated by non-unionized representatives, preserving Giga Berlin as Germany’s only major auto plant without a collective bargaining agreement.

Thierig and Tesla framed the outcome as employee support for an “independent, flexible, and unbureaucratic” future, enabling acceleration on projects like potential expansions or new models. IG Metall expressed disappointment, accusing management of intimidation tactics and an “unfair” campaign.

The first election of this nature happened back in 2022. In 2024, IG Metall emerged as the largest single faction with 39.4 percent, but non-union lists coalesced for a majority.

But this year was different. There was some extra tension at Giga Berlin this year, as just two weeks ago, an IG Metall rep was accused by Tesla of secretly recording a council meeting. The group countersued for defamation.

Tesla Giga Berlin plant manager faces defamation probe after IG Metall union complaint

This result from the 2026 vote reinforced Tesla’s model of direct employee-management alignment over traditional German union structures, amid ongoing debates about working conditions. IG Metall views it as a setback but continues advocacy. Tesla sees it as validation of its approach in a competitive EV market.

This outcome may influence future labor dynamics at Giga Berlin, including any revival of expansion plans or product lines, which Musk has talked about recently.

Tesla Full Self-Driving v14.2.2.5 hit my car back on Valentine’s Day, February 14, and since I’ve had it, it has become, in my opinion, the most confusing release I’ve ever had.

With each Full Self-Driving release, I am realistic. I know some things are going to get better, and I know some things will regress slightly. However, these instances of improvements are relatively mild, as are the regressions. Yet, this version has shown me that it contains extremes of both.

It has been about three weeks of driving on v14.2.2.5; I’ve used it for nearly every mile traveled since it hit my car. I’ve taken short trips of 10 minutes or less, I’ve taken medium trips of an hour or less, and I’ve taken longer trips that are over 100 miles per leg and are over two hours of driving time one way.

These are my thoughts on it thus far:

Speed Profiles Are a Mixed Bag

Speed Profiles are something Tesla seems to tinker with quite frequently, and each version tends to show a drastic difference in how each one behaves compared to the previous version.

I do a vast majority of my FSD travel using Standard and Hurry modes, although in bad weather, I will scale it back to Chill, and when it’s a congested city on a weekend or during rush hour, I’ll throw it into Mad Max so it takes what it needs.

Early on, Speed Profiles really felt great. This is one of those really subjective parts of the FSD where someone might think one mode travels too quickly, whereas another person might see the identical performance as too slow or just right.

To me, I would like to see more consistency from release to release on them, but overall, things are pretty good. There are no real complaints on my end, as I had with previous releases.

In a past release, Mad Max traveled under the speed limit quite frequently, and I only had that experience because Hurry was acting the same way. I’ve had no instances of that with v14.2.2.5.

Strange Turn Signal Behavior

This is the first Full Self-Driving version where I’ve had so many weird things happen with the turn signals.

Two things come to mind: Using a turn signal on a sharp turn, and ignoring the navigation while putting the wrong turn signal on. I’ve encountered both things on v14.2.2.5.

On my way to the Supercharger, I take a road that has one semi-sharp right-hand turn with a driveway entrance right at the beginning of the turn.

Only recently, with the introduction of v14.2.2.5, have I had FSD put on the right turn signal when going around this turn. It’s obviously a minor issue, but it still happens, and it’s not standard practice:

How can we get Full Self-Driving to stop these turn signals?

There’s no need to use one here; the straight path is a driveway, not a public road. The right turn signal here is unnecessary pic.twitter.com/7uLDHnqCfv

— TESLARATI (@Teslarati) February 28, 2026

When sharing this on X, I had Tesla fans (the ones who refuse to acknowledge that the company can make mistakes) tell me that it’s a “valid” behavior that would be taught to anyone who has been “professionally trained” to drive.

Apparently, if you complain about this turn signal, you are also claiming you know more than Tesla engineers…okay.

Nobody in their right mind has ever gone around a sharp turn when driving their car and put on a signal when continuing on the same road. You would put a left turn signal on to indicate you were turning into that driveway if that’s what your intention was.

Like I said, it’s a totally minor issue. However, it’s not really needed, and nor is it normal. If I were in the car with someone who was taking a simple turn on a road they were traveling, and they signaled because the turn was sharp, I’d be scratching my head.

I’ve also had three separate instances of the car completely ignoring the navigation and putting on a signal that is opposite to what the routing says. Really quite strange.

Parking Performance is Still Underwhelming

Parking has been a complaint of mine with FSD for a long time, so much so that it is pretty rare that I allow the vehicle to park itself. More often than not, it is because I want to pick a spot that is relatively isolated.

However, in the times I allow it to pull into a spot, it still does some pretty head-scratching things.

Recently, it tried to back into a spot that was ~60% covered in plowed snow. The snow was piled about six feet high in a Target parking lot.

Tesla ends Full Self-Driving purchase option in the U.S.

A few days later, it tried backing into a spot where someone failed the universal litmus test of returning their shopping cart. Both choices were baffling and required me to manually move the car to a different portion of the lot.

I used Autopark on both occasions, and it did a great job of getting into the spot. I notice that the parking performance when I manually choose the spot is much better than when the car does the entire parking process, meaning choosing the spot and parking in it.

It’s Doing Things (For Me) It’s Never Done Before

Two things that FSD has never done before, at least for me, are slow down in School Zones and avoid deer. The first is something I usually take over manually, and the second I surprisingly have not had to deal with yet.

I had my Tesla slow down at a school zone yesterday for the first time, traveling at 20 MPH and not 15 MPH as the sign suggested, but at the speed of other cars in the School Zone. This was impressive and the first time I experienced it.

I would like to see this more consistently, and I think School Zones should be one of those areas where, no matter what, FSD will only travel the speed limit.

Last night, FSD v14.2.2.5 recognized a deer in a roadside field and slowed down for it:

🚨 Cruising home on a rainy, foggy evening and my Tesla on Full Self-Driving begins to slow down suddenly

FSD just wanted Mr. Deer to make it home to his deer family ❤️ pic.twitter.com/cAeqVDgXo5

— TESLARATI (@Teslarati) March 4, 2026

Navigation Still SUCKS

Navigation will be a complaint until Tesla proves it can fix it. For now, it’s just terrible.

It still has not figured out how to leave my neighborhood. I give it the opportunity to prove me wrong each time I leave my house, and it just can’t do it.

It always tries to go out of the primary entrance/exit of the neighborhood when the route needs to take me left, even though that exit is a right turn only. I always leave a voice prompt for Tesla about it.

It still picks incredibly baffling routes for simple navigation. It’s the one thing I still really want Tesla to fix.