Tesla has started rolling out a broader change to the ride experience for its Robotaxi fleet by silencing turn signals, but the change is certainly polarizing.

Tesla has generally made it clear that its purpose-built ride-hailing platform, Robotaxi, will cater to the rider in nearly every way possible. This includes having climate preferences, music, and other personal settings loaded up in the car as the rider enters.

But Tesla is taking it a step further by muting turn signal chimes altogether, a change that appears to be a way to make the ride more peaceful:

Tesla has finally turned off the blinker/turn signal noises in their Model Y Robotaxis.

This is a small update, but will definitely be noticeable for riders. It didn’t really make much sense to leave the turn signal sound on when it’s Unsupervised. pic.twitter.com/ITwx60PAMO

— Sawyer Merritt (@SawyerMerritt) July 27, 2026

However, there are a handful of people who are not thrilled about this change. Turn signals are a conditioned part of the human mind for those who ride in a car regularly.

Taking a turn without one feels strange and odd, and not hearing it click while activated could set off some alarms for riders, who might use the noise as confirmation that other drivers know of their intention to turn.

I kind of like it being on, threw me off when riding with Zoox who has had it disabled

— Dan Burkland (@DBurkland) July 27, 2026

Turn signal noises are still audible in customer cars, so if you use FSD in your personal vehicle, you will still hear the turn signal.

The move is certainly one that is unique, but not one that separates it from other ride-sharing services. In a normal car, the clicking sound confirms to the driver that the blinker is active. In a fully driverless Robotaxi, that feedback serves no purpose for passengers, other than peace of mind.

Tesla is asking a federal court to force a Cybertruck parts supplier to hand back manufacturing equipment the automaker says it owns, warning that production of the pickup could stop within days without it.

The company filed an emergency lawsuit in the U.S. District Court for the Western District of Texas, asking for a hearing on short notice to recover tooling used to stamp Cybertruck components at Giga Texas. According to the complaint, first reported by Bloomberg, the equipment sits inside a Troy, Texas plant run by Angstrom Automotive Group, which bought the facility from Anderton Casting last year and kept it on as a Tesla supplier. Case 6:26-cv-0477 is one of the more urgent supplier disputes Tesla has brought to court.

Tesla Cybertruck is officially the safest pickup, IIHS says

The dispute traces back to July 13, when Angstrom told Tesla it planned to close the Troy facility. The two sides then failed to agree on a plan to retrieve the die-cast tools, trim dies, fixtures, cutting tools, gauges and X-ray equipment that belong to Tesla. A shipment of 700 finished parts due out on July 17 never left the building, according to the filing. When Tesla sent representatives to the plant on July 21, accompanied by law enforcement, they were turned away.

Tesla’s complaint alleges Angstrom then asked for an extra $250,000 a week to keep the facility running, a demand the automaker calls an attempt to exert commercial pressure by holding its own property “for ransom.” Angstrom has not issued a public response.

The lawsuit states thousands of Cybertrucks already assigned to customers are tied to the parts in question, and that supply will run out “in mere days” without court intervention. Tesla says it is not asking the judge to resolve the underlying contract dispute or award damages, only to get physical access to equipment it already owns.

Tesla has also turned to the courts before to protect its supply chain, including its ongoing trade secret fight with former battery equipment supplier Matthews International, where a judge issued a permanent injunction against the company earlier this year.

A ruling on Tesla’s request for emergency relief is expected within days.

Tesla released Full Self-Driving version 14.3.6 last week, and after what was potentially one of the best FSD releases in v14.3.5, there has been a bit of a regression. While there are some bright spots, the changes made to v14.3.6 seem to have backtracked some behaviors.

Overall, it is hard to really complain about FSD in any sense; it has revolutionized how I travel literally anywhere. According to my self-driving app, the last time I went a day without using it was 59 days ago.

However, I think it’s also important to recognize when things are just plain bad with FSD. There are times it does truly mind-boggling things, and I’ll dive into those here. Additionally, I only had these issues on local roads, not on highways. Highway operation, generally, is always incredible other than the occasional complaint about speed or left lane camping.

With those things being said, my personal experience may not represent others’ experiences. A handful of people have said they have had a similar experience on v14.3.6, while others have said it is more than normal.

Turning Hesitancy, Inaccuracy

I’ve noticed more inaccuracy turning into multi-lane stretches of road than in any version I can remember. I’ve had at least three instances of FSD turning into a stretch of roadway that has two or more lanes, and not selecting a lane confidently as it has in past versions.

I think Tesla FSD v14.3.6 is a regression from previous .3 branches

This version in particular has been incredibly hesitant, jerky, and indecisive at times. There’s actually been two drives that I have decided to not used FSD for the remainder of the trip. These were local trips… pic.twitter.com/YobHDOKRS6

— TESLARATI (@Teslarati) July 26, 2026

Instead, the car will drive over one of the dashed road lines, and the steering wheel will jerk back and forth before picking the lane. It should be said that it has always picked the correct lane when choosing based on the navigation, but it is still very indecisive. The steering wheel jerking is reminiscent of some of the later versions of v13.

I admit I really hate to see the steering wheel jerking come back. However, I think when Tesla releases v14.3.7, it won’t be present. When there are occurrences of it in FSD versions, it is usually resolved by the following release.

FSD Disregards Manual Turn Signals

This is my biggest bone to pick with FSD other than Navigation issues, but this one seems like it would be such an easy fix.

If Tesla is going to put the word “Supervised” on the end of “Full Self-Driving,” then when I tell the car to do something, it should do it. If I input an increase in speed by pressing the accelerator, the car will immediately respond. It does not disregard my input because it feels it is traveling at the right speed.

FSD should never disobey and turn off turn signals that the driver inputs. Trying to direct the car into the correct lane, I had initiated the left turn signal not once, not twice, but three times, with the car turning it off all three times and continuing in a lane that would end in just one block. The only solution at this point would be to zipper merge.

This goes back to the fact that self-driving’s biggest bottleneck might be rider preference. A zipper merge might have been more than reasonable, might have saved me time that I spent sitting through an additional light cycle, and might be something many drivers would do. I was in no hurry, I traditionally do not try to zipper merge because it feels inconsiderate, and lastly, the car should have just followed my input.

This caused me to disengage and drive manually the rest of the way home. Sometimes I just do not need FSD to try to pass every car it can at intersections.

Bird Braking is a Thing of the Past

The big complaint with recent versions of Full Self-Driving has been what we’ve coined as “bird braking,” which is when the car will brake suddenly as a bird flies past.

There have been zero issues with this so far in v14.3.6, which is an excellent improvement.

FSD Might Already Be Taking Note of Driver Preferences

Another thing I have noticed over the past few days is that v14.3.6 seems to already be taking my preferences with navigation into account.

This is something that is supposed to be rolling out with the Summer Update, but I have a hunch it’s already present and might have been included in this v14.3.6 build. On Friday, FSD pulled into an entrance to a local convenience store that it had never attempted to go into before.

Typically, I manually pull into this entrance because it avoids heavy cross traffic at the main entrance. FSD has always chosen that congested main entrance.

I don’t want to get anyone excited but my Tesla running FSD v14.3.6 just:

✅ Pulled into an entrance at my local Sheetz that I routinely pull into manually but FSD never has entered

✅ Pulled into my assigned parking space at home despite many other spots being vacant https://t.co/ZUShvknTWO pic.twitter.com/83O5a2S0eh

— TESLARATI (@Teslarati) July 24, 2026

Additionally, FSD has pulled into my assigned parking spot at my townhouse community on multiple occasions with this release. This is something that used to happen ocassionally, but not consistently.

It also navigated back to the same convenience store last night, drove through crazy cars scrambling to gas pumps, navigated out of the parking lot correctly, drove me home, and, once again, parked in my assigned spot.

As previously stated, this release just seems to have a few things that need to be brought to Tesla’s attention, and also to make others who use FSD aware of some things that I’ve experienced. I look forward to the next release that will remedy these issues, just as Tesla has always done in the past.