Tesla investors currently have the chance to vote on a number of proposals for the company’s upcoming shareholder’s meeting, with CEO Elon Musk’s 2018 pay package hanging in the balance after it was struck down by a Delaware judge. In recent weeks, a number of Teslarati readers have shared how they voted or plan to vote on the proposal, with about a month left to go until the meeting.
After Delaware Judge Kathaleen McCormick voided the previously approved $56 billion pay package for Musk in January, both Musk and the company have appealed the decision, and the board of directors has launched a vote on ratifying the package for the stockholder’s meeting next month. Voting has been open for the past few weeks, and following our recent story detailing one of Tesla’s largest shareholders as he criticized Musk and suggested voting “no” on the measure, many have said they voted in favor of the proposal.
Tesla also launched a website dedicated to explaining how shareholders can vote, and detailing the board’s voting recommendations. Crucially, the board has recommended “yes” votes on both proposals three and four, which concern Tesla’s potential move to re-incorporate in Texas instead of Delaware, and the pay package vote for Musk, respectively.
The annual shareholder’s meeting will be held on June 13, and shareholders can continue to vote on the proposals between now and then. Tesla has also shared a video on social media encouraging investors to vote in favor of this, and the company’s incorporation move from Delaware to Texas.
We have put forward two especially important proposals for our Annual Meeting of Stockholders—and we need your vote.
Protect your rights as stockholders & protect the value of your investment by voting FOR the ratification of the 2018 CEO Performance Award & FOR Reincorporating… pic.twitter.com/ONmB7oZfyM
— Tesla (@Tesla) May 20, 2024
How Teslarati readers are voting on Musk’s 2018 pay package (so far)
Following our recent stories, 88 respondents have reached out and told us how they were voting, or planned to vote, on proposal three regarding Musk’s previously approved pay package. Of them, about 66 percent said they had voted or would vote in favor of ratifying Musk’s 2018 compensation plan, while around 30 percent said they voted or would vote against it. The remaining respondents, representing just over 3 percent, said that they were still undecided on the vote.
Those who responded varied in their number of shares; while most did not include how many shares they were voting for, others ranged from having just a few shares to over 7,000 shares.
To be sure, this is an extremely small sample size, especially given the sheer number of shareholders and Tesla shares out there. This also does not take into consideration the number of shares owned by each respondent, though it gives a small overview of how individual Tesla shareholders (who took the time to respond to recent stories) voted on proposal three. In addition, shareholders still have a few weeks left to cast their votes, and many could still be mulling over their vote on the proposal.
The board explains its recommendation for shareholders to vote “yes” by citing the fact that Musk already performed the work needed to earn the previously approved pay package. Some have noted that the CEO isn’t currently being paid for his past several years with the company, as a result of the package being struck down. Others have criticized Musk and Tesla for recent layoffs and his sharing of political views, which they say is why they would vote “no” on the proposal.
“Elon has not been paid for any of his work for Tesla for the past six years… That strikes us, and the many stockholders from whom we already have heard, as fundamentally unfair,” wrote Board Chair Robyn Denholm on the subject last month.
“We do not think that what the Delaware Court said is how corporate law should or does work. If it is legally advisable, we suggest simply subjecting the original 2018 package to a new shareholder vote.”
Musk also defended his pay package following the January decision, as well as his hopes for more voting control amidst the rapid development of artificial intelligence (AI) products.
Note: This article will be updated periodically up until Tesla’s Annual Stockholder Meeting on June 13. Last updated 6/4/24.
Musk responds to pay case lawyers requesting $6 billion in Tesla shares
What are your thoughts? Have you voted on proposal three of the upcoming meeting, and if so, how did you vote? Let me know at zach@teslarati.com, find me on X at @zacharyvisconti, or send us tips at tips@teslarati.com.
News
Tesla briefly offered this Robotaxi part for your personal car
Tesla briefly offered one Robotaxi part in its Parts Catalog for your personal car, only to remove it just a short time after it was first noticed.
Tesla’s Robotaxi camera washer apparatus was briefly available for purchase on the company’s Online Parts Catalog. The camera washer was first noticed on Model Y Robotaxi vehicles about six months ago in Austin.
🚨 Tesla looks to have installed Camera Washers on the side repeater cameras on Robotaxis in Austin
pic.twitter.com/xemRtDtlRR— TESLARATI (@Teslarati) January 23, 2026
First noticed by Not a Tesla App, the Camera Washer entries appeared for the new “Juniper” Model Y under a category called “Halo,” which has also now disappeared. Interestingly, Halo probably is related to Tesla’s internal “Project Halo,” which was a project that aimed to retrofit customer-owned Model Ys into functional Robotaxis.
This hardware addition would likely be required for the vehicle to operate as a Robotaxi, as the Camera Washer seems to be a non-negotiable part of the vision-based system Tesla utilizes for self-driving efforts.
However, this part has since been removed and is no longer visible on the EPC.
Now the true question lingers: Why would Tesla add this Camera Washer to the Model Y parts catalog? Is it planning to make it available for owners to utilize on their own cars for personal use, or will it become a prerequisite for Robotaxi operation in customer-owned cars?
While discussing the upgrade options for Hardware 3 vehicles during the Q1 Earnings Call, Tesla CEO Elon Musk had said that the company could establish small, satellite shops that would upgrade cameras and self-driving computers. Perhaps this same strategy could be utilized for vehicles that want to be included in Robotaxi but do not have the correct hardware.
AI4 is currently represented as capable of unsupervised self-driving, and the same was said about HW3 at one point, only for Tesla to admit last quarter that it would, unfortunately, not be possible. Perhaps AI4 vehicles might need this camera washer as a prerequisite, just as HW3 cars will need that camera and computer upgrade.
This could be the first hint of that’s where we are headed.
News
Tesla Robotaxi gets sweeping but polarizing change
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.
News
Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots
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.

