Sources describe problems at GM's Cruise self-driving car unit, which has had delays, issues with software, and more, after landing $5B in investments
including the difficulty that Cruise cars have identifying whether objects are in motion—mean putting GM's driverless cars on the road in a large scale way in 2019 is looking highly unlikely.” https://www.reuters.com/... Ryan Felton / @ryanfelton : Reuters reports “driverless Cruise cars still struggle to identify whether objects on the road are moving or stationary.” Tracks with what Cruise told SF in the spring about their cars' ability to interact with emregency vehicles. See here: https://www.reuters.com/... pic.twitter.com/O3t758Hw41 Timothy B. Lee / @binarybits : GM's 2019 launch target always struck me as ambitious. Cruise was founded ~4 years after Google's driverless car program, and from talking to various folks in the industry it seems like they're still more than a year behind. http://www.reuters.com/... Timothy B. Lee / @binarybits : Especially because Cruise only had 40 employees at acquisition time in early 2016. Cruise has only had access to Google-level resources for a little over 2 years.
Context & Ripple Effects
Cruise had been running an autonomous ride-hailing service for employees in San Francisco since 2017, and the $5B in fresh investment positioned GM as Google's most credible challenger. This Reuters reporting punctures that narrative from inside: sources describe cars that cannot reliably tell whether road objects are moving or stationary, plus broader software problems, with industry contacts judging Cruise more than a year behind Google's program.
The report matters because it converts a marketing timeline into an engineering question. The prediction that a large-scale 2019 deployment is 'highly unlikely' proved durable — Cruise later formally abandoned its 2019 commercial robotaxi target, citing performance and safety concerns.
First-order effects
- GM's plan to put driverless Cruise cars on the road at scale in 2019 collapses on the timeline side, leaving the $5B in investment tied to a product with unresolved perception failures around moving versus stationary objects.
- Cruise's competitive standing against Google's driverless program worsens measurably — more than a year behind, per industry contacts cited by Reuters.
Second-order effects
- Google's driverless unit gains a de facto lead it can press commercially while GM must choose between delaying revenue and shipping a system with known object-motion detection gaps.
- Continued delays force GM into open-ended capital commitment to Cruise, a cost trajectory that later showed up as an average $588M spent per quarter with staff intervening every few miles.
Third-order effects
- If the pattern holds, robotaxi programs face a structural gap between demo fleets and commercial scale: even after Cruise reached a 24/7 driverless fleet in San Francisco in 2023, the burn rate and intervention frequency show the 2018-era problems were deferred rather than solved.
- Perception reliability — not vehicle hardware or funding — becomes the binding constraint on autonomous deployment, pushing the industry toward longer timelines and heavier remote-assistance staffing than early roadmaps assumed.
The trend: Robotaxi development keeps slipping from headline launch dates to multi-year engineering slogs, where perception reliability and intervention rates, not capital, set the pace.