News
Tesla responds to allegations of unjust pay and visa violations
Tesla has issued a response to this weekend’s report that a factory worker who worked on the company’s high-volume paint shop at Fremont, CA plant was part of a group of foreign workers that were paid $5/hr and operated outside the terms of their visas.
The story has gained attention after the San Jose Mercury published a report of its recent investigation on Gregor Lesnik’s suit against the electric vehicle maker and several other defendants for unfair treatment in a workplace. The Mercury reports that a Slovenian company called ISM Vuzem flew Lesnik and a group of foreign workers to the U.S. while housing them in “nondescript apartments” where they would be shuttled from and to the Tesla plant to work six to seven days a week at low wages.
Among the claims in the lawsuit via the Mercury:
- Eisenmann USA wrote letters to the U.S. Embassy on behalf of Lesnik and as many as 200 foreign workers stating they would supervise employees at a U.S. auto plant. Most of the Vuzem workers were nonsupervisory laborers and tradesmen.
- Tesla issued company security badges to the foreign workers, recorded their time on site and shared responsibility for setting safety conditions.
- Vuzem required foreign employees to regularly work between 60 and 70 hours a week. Vuzem paid Lesnik an average of 800 euros per month, or about $900, for a rate of less than $5 per hour. Lesnik was promised an equal amount when he returned home, but the company never paid the balance.
- The companies violated wage and employment laws and benefitted from the cheap labor of foreign workers. Workers were promised $12.70 an hour based on a standard workweek. The suit estimates they are due $2.6 million in overtime and premium pay.
Tesla has issued a response to the story defending their stance that the company operated within legal limits stating that Lesnik’s claim is a moral issue at heart, but the company will see to it that the right thing happens and all are treated fairly should the claims be true.
According to Tesla’s issued response, Lesnik’s accident as a result of slipping on loose tile and falling three stories while working on the company’s high-volume paint shop, was investigated by the government regulator that oversees workplace accidents (Cal/OSHA) and found to be not at fault of the company. Tesla’s statement says, “When Mr. Lesnik brought a workers compensation case, Tesla was dismissed from the case because the judge concluded that we had no legal responsibility for what occurred.”
Here’s a copy of Tesla’s full response to the story.
“At Tesla, we aspire to operate on the principles of hard work and exceptional performance, but always tempered by fairness, justice and kindness. There are times when mistakes are made, but those are the standards to which we hold ourselves. With respect to the person at the center of this weekend’s article in the Mercury News, those standards were not met. We are taking action to address this individual’s situation and to put in place additional oversight to ensure that our workplace rules are followed even by sub-subcontractors to prevent such a thing from happening again.
Gregor Lesnik was brought to the Tesla factory by a company called ISM Vuzem, a sub-contractor brought in by Eisenmann, the firm that we hired to construct our new, high-volume paint shop. We contracted with Eisenmann for the simple reason that we do not know how to build paint shops and they are regarded as one of the best, if not the best, in the world. In our dealings with them, we have found them to be an excellent company, run by good people.
-
-
The article describes how Mr. Lesnik came to this country, the conditions under which Vuzem employed him and others to do their work, and how Mr. Lesnik ended up being injured while on the job. Assuming the article is correct, we need to do right by Mr. Lesnik and his colleagues from Vuzem. This is not a legal issue, it is a moral issue. As far as the law goes, Tesla did everything correctly. We hired a contractor to do a turnkey project at our factory and, as we always do in these situations, contractually obligated our contractor to comply with all laws in bringing in the resources they felt were needed to do the job.
Regarding the accident that resulted in Mr. Lesnik being injured, Cal/OSHA (the government regulator that investigates workplace accidents like these) came to our factory, investigated the incident and found that Tesla was not responsible. When Mr. Lesnik brought a workers compensation case, Tesla was dismissed from the case because the judge concluded that we had no legal responsibility for what occurred.
All of that is fine legally, but there is a larger point. Morally, we need to give Mr. Lesnik the benefit of the doubt and we need to take care of him. We will make sure this happens. We do not condone people coming to work at a Tesla facility, whether they work for us, one of our contractors or even a sub-subcontractor, under the circumstances described in the article. If Mr. Lesnik or his colleagues were really being paid $5 an hour, that is totally unacceptable. Tesla is one of the highest paying hourly employers in the US automotive industry. We do this out of choice, because we think it is right. Nobody is making us do so.
-Tesla will be working with Eisenmann and Vuzem to investigate this thoroughly. If the claims are true, Tesla will take action to ensure that the right thing happens and all are treated fairly.
Creating a new car company is extremely difficult and fraught with risk, but we will never be a company that by our action does, or by our inaction allows, the wrong thing to happen just to save money.”
Tesla released Full Self-Driving version 14.3.7 yesterday, and after about 90 miles of testing today, it is evident there are some definite fixes from version 14.3.6, which I wrote about last week and called a regression.
Within the first 40 minutes of my drive on v14.3.7, it saved me from getting into an accident with an unaware Dodge Charger driver, and some of the things Tesla seemed to miss in v14.3.6 were definitely improved. All in all, the release so far has some really great performance, and I’m looking forward to testing it further.
For now, here’s everything I noticed with v14.3.7:
Overall Improvement
Just generally speaking from a ride perspective, this was a really great experience. A lot of the hesitancy I experienced on v14.3.6 was gone. There were no instances of brake-stabbing, wheel-jerking, or any uncertain or unconfident movements. It was void of anything that I felt made it timid with v14.3.6.
The one thing I do hope to see down the road is a smaller need to adjust Speed Profiles so often. Because Tesla calls FSD “Supervised,” I’m okay with needing to hit the scroll wheel a few times a drive.
However, I hope that things can be incrementally improved upon with speed. Sometimes it’s too fast; other times it’s too slow. It’s a difficult thing to hone in and refine, but I hope it eventually gets there.
I didn’t notice any significant left lane camping or any behaviors that were completely out of line. I am hopeful that this opinion does not change, but after driving a few days with this version and putting it in a variety of different situations, you are exposed to more behaviors, some of which are not necessarily what I’d prefer.
-
The big things to notice, at least in my experience thus far, are that the major issues with previous versions — meaning the braking stabbing and wheel jerking — simply weren’t there. That’s enough to already consider this progress compared to .6.
Manual Signal Override is More Responsive
On .6, I had quite a few issues with FSD ignoring my manually input turn signals. If Tesla wants to call it “Supervised,” then the car should not ignore any input the driver gives. If I touch the accelerator on FSD, the car speeds up.
🚨 Tesla FSD v14.3.7 obeying manual turn signals https://t.co/6eqToXpQfC pic.twitter.com/vHBlFQ4PDV
— TESLARATI (@Teslarati) August 2, 2026
The car did a great job of obeying my turn signals when I wanted it to change lanes, which is welcome.
Parking Lot Performance
Before .6, I traditionally took over in nearly every parking lot my car entered, because I knew it would not park somewhere that I wanted, and usually, it was just a tad too timid in this setting.
The one bright spot of .6 was how well it handled parking lots. This continued with v14.3.7:
-
I’m always really happy to see progress at all, but once parking preferences come to FSD, as long as this performance is still around, that could potentially be the biggest improvement I’ve seen in FSD in the year I’ve been using it personally on a daily basis.
Full Self-Driving Averts Disaster
A Dodge Charger changed into my lane without checking if I was there, running me off the road. FSD made the initial avoidance maneuver; I grabbed the wheel out of instinct, looked in my side mirror to ensure I had nobody following closely behind, hit the brake, and straightened the car back up to avoid a curb:
🚨 Guys this is why you all NEED to stay vigilant behind the wheel, even on Tesla Full Self-Driving
Human drivers are UNHINGED and have no idea what they’re doing anymore. This was a kid obviously younger than 20 years old with zero awareness.
First drive with v14.3.7 https://t.co/1vTbCMpCn8 pic.twitter.com/lz7KKEF6bj
— TESLARATI (@Teslarati) August 2, 2026
-
There have been quite a few responses to this video stating that I should never have grabbed the wheel. To be honest, I really wish I had not done so, because I do believe FSD would have avoided any sort of collision with anything, including the car or the curb.
However, this was the first time I had ever been this close to being hit while using FSD. My natural reaction was to take over. I think if I had had something like this happen before, my reaction might have been different.
Hitting the brake avoided hitting the curb, while FSD swerved to avoid the car. My concern after the car was clear of my front end was the curb. All in all, I’m really happy with how things turned out, and I think anyone could be a critic of how I handled it. I only had a split second to really make a decision, and thankfully, any damage was avoided.
It is clear FSD managed to avoid the car coming down before I was able to. I truly credit FSD for avoiding the collision.
What Needs to Improve
Better Recognition of Potholes, Uneven Roads, Sharp Changes in Roadway/Bumps
On Friday, my Fianceè and I were in the car, and FSD was driving us. We crossed over a roadway that has a traffic light, and FSD was traveling at 40 MPH on Standard, 5 MPH over the speed limit. Everything was more than reasonable.
However, the road we were crossing at the light has a major bump both as you start and finish crossing it. Without a speed reduction, your car can go airborne. The Tesla did just this on Friday on v14.3.6; it was an uncomfortable bounce that pretty much confirmed I would not ever let FSD go over again unless we were sitting at that intersection when there is a red light.
I even tried scrolling down into Sloth quickly, but I ended up just taking over:
-
This is that big bounce that I mentioned in the quoted post.
It’s just a tad too drastic to take at the speed FSD wants to go over it. You can see me quickly swipe down into Sloth, but I intervened. https://t.co/K20PK9ysBg pic.twitter.com/81Oc82ZJcZ
— TESLARATI (@Teslarati) August 2, 2026
A few people have said it remains related to the vision-based approach and its difficulty comprehending 3D. This is a huge issue because this can cause serious damage at certain speeds.
Navigation
Nothing new here. I still turn off “Online Routing” quite frequently to get the car to take logical routes from time to time.
Auto Wipers
Auto Wipers are just plain bad. I really hope Tesla just uses a rain sensor. I thought they had improved at one point, but I still get dry wipes, Speed 4 on a drizzle, and Speed 2 on a steady rain. In reality, these should be switched.
You can watch our full review of Tesla Full Self-Driving v14.3.7 below:
-
🚨 Tesla Full Self-Driving v14.3.7 saved me from an accident! FULL REVIEW: https://t.co/1vTbCMpCn8 pic.twitter.com/9mHmKVoMVA
— TESLARATI (@Teslarati) August 2, 2026
SpaceX will report second quarter results after the market closes on Tuesday, August 4, marking the first time the company has opened its books to the public since its record IPO in June. Management will host a live audio only webcast at 4:30 p.m. ET, streamed on X, with no dial in option.
The debut carries more weight than a typical first quarter as a public company. Two trading days after the release, on August 6, the first tranche of SpaceX’s lockup expires, freeing roughly 911.5 million insider and employee shares, worth well over $100 billion at current prices and the largest such release in Wall Street history. A second, larger tranche tied to the stock trading 30 percent above its $135 IPO price never triggered, since shares have spent most of July trading below that price.
Wall Street’s models point to revenue near $6.9 billion for the quarter, up sharply from the $4.69 billion SpaceX reported in the first quarter, with a narrower per share loss than the $1.27 posted three months earlier, according to estimates compiled by Motley Fool. Those numbers will be the first look at how SpaceX’s three segments, Starlink, launch and AI, are performing independently.
SpaceX scores another massive Pentagon deal to support military satellites
Investors heading into the call have a specific list of questions. How many net new Starlink subscribers did SpaceX add after ending March with 10.3 million, and is average revenue per user holding up as the service expands into lower income markets. How much of the AI segment’s revenue reflects contract signings with Anthropic, Google and Reflection AI this year, deals that combined could annualize to nearly $28 billion if fully ramped. Whether capital expenditures, which nearly doubled in the AI segment alone between 2024 and 2025, are still accelerating or starting to plateau. And whether management offers any forward guidance at all, something SpaceX has never done publicly.
The report will also land days after Elon Musk publicly denied a Wall Street Journal report describing internal planning to separate Tesla’s China business ahead of a potential Tesla-SpaceX merger. Whether Musk or SpaceX executives address that speculation on the call, even indirectly, maybe something investors will be listening for on Tuesday.
As Teslarati reported after Musk’s own warning to short sellers last week, the CEO has made clear he expects skeptics to be proven wrong over time. Tuesday will be the first chance for the numbers themselves to make that case.
-
Elon Musk
SpaceX’s Starship just got filmed by its own cargo
SpaceX released new footage of Starship in space captured by the Starlink satellites it deployed.
SpaceX released a new video Friday evening showing Starship from an angle showcased by its own Starlink satellites, watching the rocket drift away in orbit.
The 65 second clip, posted on X, stitches together footage from four cameras mounted on a single Starlink V3 satellite. It opens with a close view of Starship’s 171 foot upper stage, still catching sunlight, then pulls back as the two spacecraft separate.
The footage comes from Starship’s 13th flight test, which launched July 24 from Starbase after a scrubbed attempt and an abort caused by an engine issue the week before. When Flight 13 finally flew, it carried the first batch of functional Starlink V3 satellites Starship has ever deployed, twenty of them, with six equipped with cameras meant to scan the ship’s heat shield during reentry.
View of Starship in space from a Starlink V3 satellite on Flight 13.
This composite is made of imagery from four separate cameras on a single satellite. Six of the satellites were equipped with cameras to scan Starship’s heat shield and transmit imagery down to operators to… pic.twitter.com/sNTHHz5vLr
— SpaceX (@SpaceX) July 31, 2026
Flight 13 checked most of its boxes. Starship deployed all 20 satellites, relit a Raptor engine in space, and splashed down softly in the Indian Ocean off Western Australia. Musk’s longer term plan calls for a Starlink V3 constellation of 100,000 satellites, according to a recent FCC filing, with Starship as the only vehicle capable of launching them at the volume that requires. Each Starship flight is designed to carry up to 60 V3 satellites once the vehicle reaches routine service, well beyond what Falcon 9 can carry in a single mission.
-
Starship is next expected to fly with an attempt at catching the ship itself with the launch tower’s mechanical arms, a maneuver SpaceX has so far reserved for the Super Heavy booster.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
SpaceX’s biggest test yet arrives this week and it’s not a rocket launch
