News
Tesla implicated in foreign worker scandal after reports of visa violations
The San Jose Mercury finds that up to 140 low wage workers were used to build the new Tesla paint shop at the Fremont factory. They were supplied with phony B1/B2 visas by foreign companies.
Updated: Tesla has issued a response to the story which can be seen here.
Tesla is justly proud of its new state-of-the-art painting facility capable of scaling up to 500,000 vehicles per year at the Fremont factory, but a report coming from the San Jose Mercury published on May 15 says that underpaid foreign workers contributed to the construction of the paint shop violating terms of their B1/B2 visas.
The Mercury began its investigation after Gregor Lesnik, a native of Slovenia who worked on the expansion of Tesla’s multimillion dollar Fremont factory paint shop in 2015, filed suit against Tesla and several other defendants. Lesnik was seriously injured while working on the paint shop project after slipping on loose tile and falling three stories before breaking both legs, ribs, and sustaining a concussion.
The newspaper reports that in 2014, Lesnik was an unemployed electrician living with his mother in Velenje, Slovenia. His girlfriend was expecting their first child and money was tight. He saw an ad seeking workers placed by ISM Vuzen, a construction company located in Slovenia. Vuzem provides teams of Eastern European workers to build manufacturing plants in Europe and the U.S. Among its clients are Mercedes-Benz, Toyota, Volkswagen, Ford, and Saab.
In March, 2015, Tesla selected Eisenmann, a German-based manufacturer of industrial systems, to expand the Fremont paint shop. Eisenmann claimed it was the most valuable contract in its history at $100 million. Soon it began hiring subcontractors to fill out the work force for the project. It turned to Vuzen for some of those workers.
Vuzen helped Lesnik apply for a US visa. Eisenmann assisted. Robert Keller, its US purchasing manager based out of Chicago, was listed as Lesnik’s U.S. contact. After Lesnik filed his lawsuit, Eisenmann denied that it had any legal responsibility for him.
US immigration officials were told that Lesnik was a supervisor with specialized training who would be working at a paint shop for a BMW factory in South Carolina. Keller told INS in a letter that Lesnik was a “supervisor of electrical and mechanical installation. His assignment will involve multiple border entries,” Keller wrote, “but in no way adversely affect the employment of citizens of the United States.”
That couldn’t be further from the truth, says Rob Stoker, president of the Building and Construction Trades Council of Alameda County. “There’s definitely something wrong with this picture.” He claims a local company lost the bid on the Tesla project party because their labor costs were higher. The job would have meant tens of thousands of work hours and valuable training for local apprentices. “It killed us,” Stoker said. “We had so many people — ready, willing and able — needing this.”
For Lesnik and his fellow employees provided by Vuzen, the work in Fremont paid an average of $5 an hour with no benefits. They often worked 12 hour days, sometimes 7 days a week. He claims that Tesla employees who he worked side by side with were earning up to 10 times as much.
Tesla denies any responsibility for Lesnik, his injuries, or his immigration status. A company spokesperson told the Mercury, “Tesla expects all its contractors and their subs … to comply with all applicable pay laws.” Of course they do. But the real question is, how closely do they look at the status of people working at their facilities?
As with similar worker abuse issues that have beset other companies, such as Apple’s troubles with Foxconn, it is one thing to have high expectations. It is quite another to take adequate steps to ensure those expectations are met. All too often, it is easier to look the other way, especially when millions of dollars are involved.
Source and photo credit: San Jose Mercury
News
Tesla crosses major Unsupervised Self-Driving milestone
Tesla has reached a notable benchmark in its autonomous driving program after its Robotaxi fleet surpassed one million miles of unsupervised operation. The company made the announcement during its Cybercab event in Austin on September 3.
Tesla Vice President of AI Ashok Elluswamy told attendees he was happy to report the fleet had achieved one million miles of unsupervised Robotaxi operation as a testament to safety.
The new total marked a sharp increase from the 380,000 unsupervised miles Tesla disclosed during its second-quarter 2026 earnings update in late July.
In roughly six weeks, the company added about 620,000 miles. That acceleration followed Tesla’s decision to remove in-vehicle safety monitors from most of its operations outside the San Francisco Bay Area.

Credit: Tesla
Tesla first launched Robotaxi service in Austin in June 2025 with safety drivers present. It later began fully unsupervised rides and expanded into Dallas, Houston, Miami, Orlando, and Tampa. The San Francisco Bay Area remains the exception, where a safety monitor still rides in the vehicle under California permitting rules.
The company has not released a city-by-city breakdown of the one million unsupervised miles.
The milestone arrived as Tesla began offering public Cybercab rides in Austin. The purpose-built vehicle has no steering wheel or pedals and is designed only for autonomous ride-hailing. Production versions joined the existing fleet of modified Tesla vehicles already operating in the service.
Tesla’s unsupervised mileage is growing at a double-digit weekly rate according to earlier company comments, yet its fleet size remains modest compared with established competitors. Waymo has accumulated more than 200 million fully autonomous rider-only miles. Tesla has described its own unsupervised operations as having recorded zero notable incidents in the period leading up to the July update.
The one-million-mile figure reflects Tesla’s shift from supervised testing to broader driverless service in multiple states. It also highlights the company’s strategy of using both existing Model Y vehicles and the new Cybercab to scale its network.

Credit: Tesla
Whether the rapid recent growth continues will depend on further city expansions, regulatory approvals, and the performance of the purpose-built Cybercab in everyday paid rides. Tesla has not specified how many of the latest miles involved the new vehicle versus the rest of the fleet.
The announcement underscores Tesla’s progress toward a larger robotaxi network while illustrating the remaining gap in total autonomous experience relative to longer-operating rivals.
News
Tesla Robotaxi will be a 24/7 service: here’s when
Tesla AI lead Ashok Elluswamy said this week that 24-hour Robotaxi service is close. Replying on X to a rider who wanted Cybercab trips all night, he wrote that the capability would arrive “next month or so” once “the next tech to merge on the v15 plan” is ready.
The comment landed on September 4, one day after Tesla opened public Cybercab rides in Austin. It is the clearest near-term timeline yet for overnight unsupervised operation. Tesla’s paid Robotaxi network currently runs from 6 a.m. to 10 p.m. seven days a week across Austin, Dallas, Houston, Miami, Orlando, and Tampa.
next month or so. the next tech to merge on the v15 plan will enable it.
— Ashok Elluswamy (@aelluswamy) September 4, 2026
That 16-hour window is shorter than the 6 a.m. to 2 a.m. schedule the company used for much of the prior year.
Elluswamy did not name the specific feature or say whether the change would apply first to purpose-built Cybercabs, the existing Model Y fleet, or both. He also offered no city-by-city rollout list. The link to Full Self-Driving v15 is nevertheless significant.
Tesla has described v15 as a step-change architecture with seven parallel improvement tracks and roughly ten times more parameters than earlier builds. Early versions of that software already operate on the Robotaxi fleet and contain about 40 percent of the planned gains.
By July 2026, the unsupervised fleet had logged more than 380,000 miles across six cities in two states with what the company called an impeccable safety record and no notable incidents caused by the vehicles themselves. Tesla has repeatedly argued that camera-based end-to-end neural networks, rather than extra sensors, are the core of the solution.
Overnight service would test that claim in lower-light conditions and would also raise vehicle utilization, a key variable for Robotaxi unit economics. The company has already begun using public Superchargers at night and is building dedicated Robotaxi charging sites.
Riders have asked why software must change if the cars already drive in the dark. The practical answer appears to be reliability and scale: Tesla has held back mass expansion until more of the v15 stack is merged, citing the need for higher confidence before putting thousands of unoccupied vehicles on streets around the clock.
If the next module arrives on the timetable Elluswamy sketched, 24-hour service could begin in October 2026 in at least some markets.
That would mark a shift from a daytime-bounded pilot to a service that can run whenever demand exists, including the late-night hours that have so far remained out of reach.
News
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
Tesla is beginning to roll out Full Self-Driving Supervised v14.3.9 with a new active safety layer that can take control even when the driver is operating the car manually.
Tesla AI said the software can activate FSD on the driver’s behalf when an imminent collision is detected and Automatic Emergency Braking may not be enough. It may also engage if the system detects heavy distraction or an accidental FSD disengagement.
FSD Supervised v14.3.9 starting to roll out shortly
This release includes a new active safety feature set: FSD Supervised can now activate on your behalf when an imminent collision is detected and Automatic Emergency Braking (AEB) may not be enough.
It may also engage if we…
— Tesla AI (@Tesla_AI) September 4, 2026
The capability is essentially Automatic Collision Evasion. However, unlike conventional AEB, which mainly applies the brakes in a straight line, this feature can use steering, braking, and acceleration together if the car calculates that stopping alone will not prevent impact and a safer path exists. The system may change lanes or move toward a shoulder when conditions allow, then continue driving after the immediate threat is handled rather than simply coming to a stop.
The intervention is meant as a last-resort safety net, not a replacement for attentive driving.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
Tesla’s own description still frames FSD as supervised assistance. Secondary reports on internal release notes say the feature can fire while the car is being driven manually if cabin-camera monitoring suggests the driver is not sufficiently attentive, such as reaching toward the back seat, or if FSD appears to have been turned off unintentionally.
After the emergency maneuver, the car is expected to alert the driver and request a return to manual control.
The safety case is straightforward. Many collisions happen in the last second because a driver is looking away, fumbles a control, or faces an obstacle that braking cannot fully solve. A system that can both recognize that AEB is insufficient and execute a coordinated evasive path can reduce those remaining high-severity events.
Re-engaging after accidental disengagement also addresses a practical failure mode: a small steering nudge that drops FSD at the worst moment. The advantage is a background safety net that uses the same vision stack already running in v14, instead of leaving the car solely to emergency braking once the driver is no longer in command.
The feature still depends on FSD being enabled and, according to reports, an active FSD purchase or subscription. It does not make the vehicle unsupervised. Drivers remain responsible, and Tesla has not published how often the system is expected to intervene or how it will handle false positives.
If the rollout is conservative and the false-alarm rate stays low, the update is a meaningful step: FSD is no longer only a feature the driver turns on. In the rare moments when disaster is already forming, it can step in.

