General Motors (GM) has announced plans to cut funding for its driverless robotaxi company Cruise, in a major pivot away from the commercial robotaxi business toward autonomy development in the company’s personal vehicles.
On Tuesday, GM announced plans to cut funding for Cruise and bring its autonomy development program in-house to its own vehicles, as detailed in a press release. In departing from commercial robotaxi development, the company will instead focus on building out Super Cruise, its “hands-off, eyes-on” driver assistance system, which it says is available in over 20 GM vehicles and logs more than 10 million miles per month.
“Consistent with GM’s capital allocation priorities, GM will no longer fund Cruise’s robotaxi development work given the considerable time and resources that would be needed to scale the business, along with an increasingly competitive robotaxi market,” GM writes in the post.
MORE ON CRUISE: GM’s self-driving arm Cruise hit with its latest fine over crash response
Currently, GM has a roughly 90-percent stake in Cruise, and it says it has agreements with other shareholders to bring that up to over 97 percent, before acquiring any remaining shares and restructuring.
“GM is committed to delivering the best driving experiences to our customers in a disciplined and capital efficient manner,” GM CEO Mary Barra said. “Cruise has been an early innovator in autonomy, and the deeper integration of our teams, paired with GM’s strong brands, scale, and manufacturing strength, will help advance our vision for the future of transportation.”
GM plans to work closely with the Cruise leadership team on restructuring and refocusing Cruise’s operations, which it says it expects will decrease spending by over $1 billion per year upon completion. The automaker also says it expects to complete the plan proposal within the first half of 2025, contingent upon the company’s repurchase of shares and Cruise board approval.
“As the largest U.S. automotive manufacturer, we’re fully committed to autonomous driving and excited to bring GM customers its benefits – things like enhanced safety, improved traffic flow, increased accessibility, and reduced driver stress,” says Dave Richardson, SVP of Software and Services Engineering at GM.
The news comes after the company in September said that it was aiming to re-launch paid driverless ride-hailing services with Cruise in the coming months, following an accident involving one of its robotaxis last October that brought with it mass staff shake-ups and legal trouble.
Cruise Founder Kyle Vogt, who resigned from the company after the aforementioned accident last October, responded to the news of GM cutting funding in a post on X:
In case it was unclear before, it is clear now: GM are a bunch of dummies.
It also comes amidst competition from Google-owned Waymo, Amazon’s Zoox, and others in the emerging driverless ride-hailing industry, as well as Tesla, which unveiled the Cybercab robotaxi in October, set to be based on its Full Self-Driving (FSD) software.
Will Tesla license FSD to GM, BMW, and others?
For years now, many in the Tesla community have suggested that the company could someday license its FSD software to other automakers, once it shifts from Supervised to Unsupervised. It’s interesting to see GM pivot toward an autonomy development model that prioritizes data from customer vehicles, especially following Tesla’s long-anticipated launch of its own robotaxi platform, the Cybercab.
Elon Musk has said many times that the company could and would license FSD to other automakers, though no such partnerships have yet been disclosed. Following a recent video posted on X of the latest version of FSD Supervised, v13.2, the official BMW account responded to another user, affirming that the video was “very impressive.”
https://twitter.com/BMW/status/1866548798798844297
The quote elicited a response from Tesla’s main account, and it has reignited discussions around whether the company would license FSD to other companies. Between that and GM ending funding for Cruise and citing “increased competition” as a factor, it’s probably safe to say that Tesla could be inching closer to making FSD licensing deals a reality.
What are your thoughts? Let me know at zach@teslarati.com, find me on X at @zacharyvisconti, or send us tips at tips@teslarati.com.
Cruise ordered to pay max penalty for delayed accident report
Elon Musk
Tesla Roadster is ‘sorcery and magic’ and might be worth the wait, Uber founder says
Perhaps the wait will be worth it, especially according to Uber founder Travis Kalanick, who recently teased the Roadster’s potential capabilities based on what he has heard from internal Tesla sources.
Tesla is planning to unveil the Roadster in late April after years of waiting. But the wait might be worth it, according to Travis Kalanick, the founder of Uber, who recently shed some light on his expectations for the all-electric supercar.
We all know the Roadster is supposed to have some serious capability. CEO Elon Musk has said on numerous occasions that the Roadster will be unlike anything else ever produced. It might go from 0-60 MPH in about a second, it might hover, it might have SpaceX cold gas thrusters.
However, the constant delays in the Roadster program and its unveiling event continue to send Tesla fans into confusion because they’re just not sure when, or if, they’ll ever see the finished product.
Perhaps the wait will be worth it, especially according to Uber founder Travis Kalanick, who recently teased the Roadster’s potential capabilities based on what he has heard from internal Tesla sources.
Kalanick said on X:
When I’ve run into people who are in the know, I inquire, they tell me nothing, but their eyebrows raise and their eyes widen in a way that can only mean something of sorcery and magic is coming…
— travis kalanick (@travisk) March 17, 2026
Musk has said this vehicle is not going to be geared for safety, and that, “If safety is your number one goal, do not buy the Roadster.”
There has been so much hype regarding the Roadster that it is hard to believe the company could not come through on some kind of crazy features for the vehicle.
However, the latest delay that Tesla put on the unveiling event is definitely eye-opening, especially considering it is the latest in a series of pushbacks the company has put on the vehicle for the past several years.
Tesla has made several jumps in the Roadster project over the past few months, as it has ramped up hiring for the vehicle and also applied for a patent for a new seat design.
The car has been a back-burner project for Tesla, as it has been focusing primarily on autonomy and the rollout of Robotaxi and Cybercab. Additionally, its other vehicle projects, like the Model 3 and Model Y refreshes, took precedence.
Tesla still plans to unveil the Roadster next month, so we can hope the company can stick to this timeframe.
Cybertruck
Elon Musk clarifies viral Tesla Cybertruck accident with driver logs
Musk has come out to say that the driver logs have already shown that the driver “disengaged Autopilot four seconds before crashing,” in a post on X.
Tesla CEO Elon Musk has clarified some details regarding the viral Tesla Cybertruck accident with company driver logs, which show various metrics at the time of an incident.
The logs have been used in the past to pull responsibility off of Tesla when the automaker’s Full Self-Driving (Supervised) or Autopilot platforms are blamed for a collision or accident. It appears this will be no different.
On Tuesday, a video of a Cybertruck crashing into an overpass barrier in August 2025 was shared by Fox Business in a story that reported a woman was suing the automaker for $1 million in a liability and negligence case.
In the suit, Justine Saint Amour said that, “Something terrifying happened, without warning, the vehicle attempted to drive straight off an overpass.” Her attorney, Bob Hilliard, said Amour “tried to take control, but crashed into the barrier and was seriously injured (mostly her shoulder, neck, and back).”
The Tesla Model Y is leading China’s electric SUV segment by a wide margin
Tesla vehicle crashes are widely popular to report by mainstream media outlets because of the sensationalism of the event. Oftentimes, these outlets will include Tesla in the headline, especially because it will pique the interest of the masses, as most who read the story are waiting to see the claim that Autopilot or Full Self-Driving was the culprit of the accident.
However, Tesla has access to the logs of every vehicle in its fleet, which will show the various metrics, like whether either FSD or Autopilot was active, if the accelerator was pressed, the speed, and other important factors.
Musk has come out to say that the driver logs have already shown that the driver “disengaged Autopilot four seconds before crashing,” in a post on X.
Logs show driver disengaged Autopilot four seconds before crashing
— Elon Musk (@elonmusk) March 18, 2026
If the logs do show this, which Tesla will likely have to prove in court, the real question would be why did the Amour disengage the suite?
Tesla’s Full Self-Driving suite is still not fully autonomous, meaning the driver cannot pull attention away from the road and must be ready to take over the vehicle at all times.
It will be interesting to see how this particular case pans out, especially considering the clip that was released by the law firm starts at about four seconds before the collision. Tesla logs have dispelled media reports in the past that have accused the company’s suite of being responsible for an accident, so there will be some major attention on what is proven in this particular case.
News
Tesla Robotaxi appears to be heading to a new U.S. city
Things are expanding for Robotaxi, but the big sign that it is really moving along greatly will be with the expansion to a new city. Tesla has not gone outside of Austin or the Bay Area as of yet, and launching in a new city will be a great indicator of progress.
Tesla Robotaxi appears to be heading to a new U.S. city, and although the company has revealed plans to launch in six new metros this year, it has yet to establish a new location outside of Austin and the Bay Area of California, where it has operated since last Summer.
A lot full of Model Y vehicles was spotted in Henderson, a town just north of Las Vegas, but there seems to be more than just this hint indicating that the Sin City will be the next location to offer potentially driverless rides in a Tesla using its Full Self-Driving suite.
These Model Ys are not your typical vehicles, as they are fitted with hardware that is only on Robotaxis: a rear camera washer is the dead giveaway:
🚨 These rear camera washers are only present on Robotaxi vehicles
Maybe Las Vegas is the next city to get the Robotaxi suite 😀 https://t.co/my3da5L4zc pic.twitter.com/jYFQuX1j2E
— TESLARATI (@Teslarati) March 17, 2026
The photos and video of the lot were taken by TheZacher on X, who spotted the Model Y fleet in the Henderson parking lot.
The rear camera washer is the main piece of evidence here that indicates Tesla could be looking to expand Robotaxi to Las Vegas, a major ride-hailing hot spot, as it is one of the biggest tourist attractions in the United States. Ride-sharing is a major industry in Vegas, especially for those who are staying off the Strip.
Tesla has also been extremely transparent that Vegas is on its radar for the Robotaxi fleet, as it revealed last year that it was one of five new U.S. cities that it planned to launch the ride-hailing service in this year.
Tesla confirms Robotaxi is heading to five new cities in the U.S.
The others were Phoenix, Dallas, Houston, and Miami.
Things are expanding for Robotaxi, but the big sign that it is really moving along greatly will be with the expansion to a new city. Tesla has not gone outside of Austin or the Bay Area as of yet, and launching in a new city will be a great indicator of progress.
It will also give Tesla a new benchmark against rival company Waymo, which has operated in Las Vegas for some time.
Tesla Roadster is ‘sorcery and magic’ and might be worth the wait, Uber founder says
Elon Musk clarifies viral Tesla Cybertruck accident with driver logs
