Recently, reports emerged stating that General Motors’ self-driving unit, Cruise LLC, was dismissing nine top executives amid an ongoing probe. A memo from Cruise President Mo Elshenawy, which was shared by the self-driving unit online, shows that the nine executives were but the tip of the iceberg in the company’s efforts to strategize its operations.
Cruise has had a very eventful year. In August, Cruise received approval to deploy its self-driving robotaxis 24/7 in San Francisco. Following an incident when one of the company’s self-driving robotaxis crashed into a firetruck, however, the California Department of Motor Vehicles (DMV) advised Cruise to cut its fleet in the city by 50%.
Things took a turn for the worse in October when a pedestrian, a woman, was initially struck by a human-driven car. The impact was so notable that the woman was thrown into the path of a Cruise robotaxi, which ended up running over the pedestrian. The Cruise robotaxi detected a collision and proceeded to pull over, dragging the woman about 20 feet further. The pedestrian was taken to SF General Hospital with serious injuries.
By late October, the California DMV advised Cruise to halt all its operations in San Francisco. Since then, Cruise has implemented a number of changes. Leaders such as former Chief Executive Officer (CEO) Kyle Vogt and Chief Product Officer Daniel Kan also left the company.
In his memo, Cruise President Mo Elshenawy noted that the company has now updated its operating plans. These updates include a workforce reduction that affects about 24% of the company’s staff. Bloomberg News estimated that Cruise’s workforce reduction efforts would likely affect about 900 full-time workers. Most of the ones affected will be from operations, though some technology positions will also be affected. Engineers, however, will mostly be safe.
Following is Elshenawy’s memo to Cruise staff, as shared by the GM self-driving unit in its official blog. The document covers the company’s decision behind its workforce reduction, as well as what those affected by the update could expect in the coming months.
In October, Cruise paused operations to take time to examine our processes, systems and tools and improve how we operate. While we remain committed to commercialization, we will approach it within a thoughtful and achievable time frame—with safety as our north star.
-
As a result of our updated operating plans, today Cruise shared the difficult news that we are making staff reductions impacting 24% of full-time Cruisers. This reflects our new future and a more deliberate go-to-market path, meaning less immediate need for field, commercial operations and corporate staffing.
As we look forward, the road to successful commercialization is dependent on defining and meeting an exceptional performance and heightened safety bar. Cruise is committed to playing a key role in defining these standards with the input of our regulators, our communities and other AV industry leaders.
We are extremely grateful to the departing employees who have helped further our mission, and the remaining Cruisers who will carry that mission forward in our next chapter.
Below is a letter from Mo Elshenawy, President and CTO of Cruise, that went to all employees today:
Cruisers:
We knew this day was coming, but that does not make it any less difficult—especially for those whose jobs are affected.
Today, we are making staff reductions that will affect 24% of full-time Cruisers, through no fault of their own. We are simplifying and focusing our efforts to return with an exceptional service in one city to start with and focusing on the Bolt platform for this first step before we scale. As a result, we are reducing our employee counts in operations and other areas. These impacts are largely outside of engineering, although some Tech positions are impacted also. As you might have learned, yesterday, we took action to part ways with several SLT members.
-
Craig and I believe this is a necessary step, and our leadership team and the board are fully aligned with how our go-forward U.S. staffing needs will map to the priorities ahead of us, and set up Cruise for the long term. We have also ended additional assignments of contingent workers who support our driverless operations, as we refined our go forward plans.
In a few moments, you will receive an email letting you know whether or not you are affected by this staffing reduction. If you are impacted, you will get details about what happens next in a subsequent email.
Please know that our first priority is to treat departing Cruisers with fairness, and I will describe more about how we are doing that below.
I also want to explain why we are making these reductions, and what this means for Cruise moving forward.
Cruise today vs Cruise moving forward
As we’ve shared, our goal is to focus our work on a fully driverless L4 service that meets a new AV performance bar, prioritize the Bolt platform, relaunch ridehail in one city to start, and enhance our safety standards and processes before we scale. We are ceasing work on the Origin MY24 but not losing sight of our work on future programs. This is very different from our prior plans to expand into more than a dozen new cities in 2024.
As a result of our decision to slow down commercialization, we are restructuring to focus on delivering the improvements to our tech and vehicle performance that will build trust in our AVs.
-
Many of you will be impacted because we aren’t commercializing as quickly, and therefore don’t need support in certain cities or facilities. In other cases, we restructured teams based on the work we’re prioritizing. We didn’t take any of these decisions lightly, though I know that isn’t much of a consolation if you’re someone affected by the actions we are taking today.
How we’re helping departing employees
We know there’s no “good” way to lay off employees, but treating people fairly on their way out was a key principle that guided our approach, and our top priority was determining how we could provide a strong severance package, while treating departing Cruisers with respect. In short, we are offering departing Cruisers pay, at minimum, through April 8, 2024 (approximately 16 weeks), plus continued subsidized health benefits, RSU vesting, the January 5 bonus, and additional immigration support for those holding work visas.
Severance details include:
- Severance pay: Departing employees will remain on payroll through Feb. 12 and are eligible for an additional 8 weeks of pay, with long-term employees offered an additional 2 weeks’ pay per every year at Cruise over 3 years.
- Bonus: All impacted employees will receive their 2023 bonus (eligible target payout) on Jan. 5, 2024.
- Medical, Dental, Vision: we will provide Cruisers and their dependents who are currently enrolled in Cruise benefits the option to receive Cruise-subsidized medical, dental and mental health/EAP benefits through the end of May.
- Perks Wallet: We will give Cruisers two months to access the perks most important to them via our Perks Wallet.
- 401(k): We will give Cruisers two months to continue contributions into their 401(k) plan, including our employer match.
- RSU vesting: All Cruisers, including those impacted and those remaining, will receive their January 15th RSU vest. In addition, we will provide liquidity for all of these January 15th shares in Q1 based on an updated 409A fair market valuation that we will conduct in the first quarter. Tax obligations for these January 15th vested shares will not be incurred until we provide you liquidity for these shares.
- Career support: Departing employees will receive a year-long subscription to LinkedIn Premium, and we will create an opt-in alumni directory to connect potential employers with impacted Cruisers. Cruise Talent Acquisition will also run workshops on resume building, networking, and interview prep with departed Cruisers in the new year.
- Immigration support: We are offering continued time on payroll through March 24 in lieu of a lump-sum severance payment to allow visa holders additional time to help transition and manage their immigration status. Eligibility for the Perks Wallet and 401(k) contributions and match will also continue through this time. We also have dedicated support lined up to help Cruisers based on their needs.
Our message to other employers in the market is that each departing Cruiser is a talented, driven, and mission-focused team member who will contribute and achieve great things elsewhere. They are departing us through no fault of their own. Other companies will be privileged to have these professionals on their teams, as we were privileged to have them here during their time at Cruise.
What’s next
As mentioned, in a few moments, you will receive an email letting you know whether or not you are affected by this staffing reduction, and if you are impacted, you will get details about what happens next. I am so sorry we have to do this by email, as I would prefer that we have a conversation with each of you. Unfortunately, given the scale of this change, this approach allows us to communicate to those who are impacted at the same time. We know you will want to say goodbye to your colleagues, so you will have access to Cruise email and Zoom for the next couple of hours (until 10am PT).
This is one of the hardest days we’ve had so far because so many talented people are leaving. I’m thankful we had the chance to work together, and I know I speak on behalf of so many Cruisers who will be reaching out to those departing to help with our professional networks and references. On behalf of the SLT, the Cruise Board and GM, I’m truly grateful to everyone who has played a role in building Cruise and who has poured so much into the promise of making our roads safer and our world better.
-
Mo
Don’t hesitate to contact us with news tips. Just send a message to simon@teslarati.com to give us a heads up.
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.
Elon Musk’s massive Terafab project, which will be the first true conglomeration between each of his major entities, is set to get its final location soon, the CEO said on Tesla’s recent earnings call.
“The Terafab, we expect to announce a location soon, and provide more details about our plans in that regard. We’ll leave that to the product, the launch announcement rather than try to squeeze it into an earnings call,” Musk said last Wednesday.
Tesla Terafab set for launch: Inside the $20B AI chip factory that will reshape the auto industry
Terafab was announced by Musk back in March and was essentially a massive, vertically integrated semiconductor manufacturing project that would provide all the chips the three companies needed for their AI initiatives without needing third-party companies.
The plant will produce over 1 terawatt of AI compute each year, and will help back up projects like Optimus, Full Self-Driving, and other AI-based projects that Musk’s companies are working on.
In April, less than a month after the project was launched, Intel announced it would join the project, contributing manufacturing expertise and consulting to Terafab as a whole. Intel is one of three chip manufacturers that produce sub-5 nanometer chips at scale. TSMC and Samsung are the other two.
However, there was no true indication of where Terafab would end up, but most believe it will likely be somewhere in Texas. Business Insider has reported that SpaceX plans to build out Terafab in Grimes County, Texas, but this is unconfirmed.
Musk confirmed recently that it would not be on Giga Texas property, as it is simply too large.
The sheer scale of TERAFAB is going to be insane.
Elon said it wouldn’t be suitable for anywhere on Giga Texas property because it’s too big:
“We couldn’t possibly fit the Terafab on the GigaTexas campus. It will be far bigger than everything else combined there.
Several… pic.twitter.com/79GbhNNuf4
— TESLARATI (@Teslarati) March 23, 2026
Terafab holds much of Musk’s grand ambitions for the future within its construct. It holds so much responsibility for the future and the biggest projects that Musk’s companies can imagine.
“I think this is a very big announcement and it deserves to have its own day in the spotlight and not be squeezed into an earnings call,” he said. “I do think Terafab is going to be an amazing initiative and a necessary one, and one without which we will be constrained in our ability to scale Optimus production, because we simply won’t have enough AI chips.”
He continued by stating that Terafab is necessary for scaling Optimus, which Musk said could be the biggest product of any kind of all time. “It’s crucial to solve that, and we’ll have to solve memory, logic, and packaging in order to scale Optimus.”
SpaceX performed a secret test on a specific portion of Starship with its recent 13th test flight last week, CEO Elon Musk revealed.
Starship’s 13th test flight took place last Friday, and in many aspects, it was one of the most overwhelmingly successful launches in the project’s history.
All of the mission objectives were met without incident, both the Super Heavy Booster and Ship managed to perform safe splashdowns in the Gulf of America and the Indian Ocean, respectively, and the deployment of Starlink satellites came and went without any complications.
— Elon Musk (@elonmusk) July 25, 2026
However, there was more on the agenda for SpaceX with Flight 13. Musk revealed an internal test of the ship’s heat shield tiles, as the space exploration company wanted to push them to the limits after previous issues.
Many noticed that Starship’s initial launch seemed to be more accelerated than normal, and that was not a mistake. Musk revealed that SpaceX decided to give Flight 13 an intentionally aggressive acceleration rate in an effort to test how well the tiles would remain attached to the ship:
This flight intentionally had much higher acceleration to test how well the heat shield tiles would remain attached at high dynamic pressure.
Test was successful.
— Elon Musk (@elonmusk) July 25, 2026
SpaceX had issues with some of the heat shield tiles remaining attached early on in the Starship program. The first six test flights presented some kind of anomaly with them, so the company’s big focus with them was to figure out a way to keep them intact through the duration of the flight.
Things truly improved as Flight 10 showed that ceramic tiles generally stayed attached to the ship far better due to refined attachment, as SpaceX utilized pins instead of adhesives. Flights 10 through 13 truly showed some clear progress with the heat shield tiles, and this latest test seems to be where some real progress was noticed, especially by Musk.
The 13th Starship launch last Friday was the second with Starship V3, SpaceX’s latest and greatest iteration of the spacecraft. Goals and ambitions are getting even grander as the project continues to progress. Musk has already hinted that SpaceX will likely try to catch Starship with Flight 14.
Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots
Musk’s massive Terafab project will get final location soon
