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.
News
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
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
Elon Musk
SpaceX’s biggest test yet arrives this week and it’s not a rocket launch
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.

