News
Cruise in hot seat amid Fire Department’s claims that robotaxis delayed responders in fatal incident
General Motors’ self-driving unit, Cruise, saw protests outside its San Francisco headquarters earlier this week. The protests come amidst the San Francisco Fire Department’s claims that some of the company’s autonomous robotaxis contributed to the tragic death of a pedestrian.
The incident, which happened on August 14, involved a pedestrian who was hit by a car in the South of Market neighborhood of San Francisco. The pedestrian’s injuries were so severe that there was heavy bleeding, and the person was no longer responding to verbal commands. It was evident that the injured pedestrian needed urgent medical care, so it was pertinent to have the person transported to a hospital as early as possible.
Public reports from the San Francisco Fire Department that were obtained by Forbes claimed that the behavior of Cruise robotaxis ended up impeding the workflow of emergency responders, so much so that critical medical care was delayed. One of the Fire Department’s reports about the incident reads as follows.
“On 8/14/2023, I was assigned to Medic 87 and responded to Incident FD23108420, at 7th Street and Harrison, for an auto vs. pedestrian. Harrison Street is 4 lanes of one-way traffic heading westbound. Upon arrival on scene, the victim was found in the (2) left lanes of Harrison Street, suffering from life-threatening injuries. SFPD and E01 had arrived prior to M87’s arrival. SFPD had a vehicle parked in the #1 lane of Harrison, and E01 had positioned its apparatus across the left 2 lanes of Harrison to shield the patient from oncoming traffic. The right 2 lanes of Harrison were blocked by (2) autonomous Cruise vehicles that had stopped and were not moving, blocking ingress and egress to the incident scene.
“The patient was suffering from life-threatening injuries, with a GCS 3, agonal respirations, and absent peripheral pulses. SFPD had applied a tourniquet to the left lower extremity to stop life-threatening bleeding from injuries sustained after being struck by a vehicle. Ventilations were assisted with a BVM, and the patient was packaged for rapid transport to a trauma center.
“While loading the patient to the ambulance, the (2) Cruise vehicles were still stopped in the right 2 lanes of Harrison, prohibiting rapid egress from the scene. SFPD had attempted manual takeover of the autonomous vehicles, but were unsuccessful. This contributed to a delay in transport with a critical trauma patient.
“SFFD members had to locate an SFPD officer and request him to move his vehicle to allow successful egress from the scene, but doing so further delayed patient care. These delays caused by (2) autonomous vehicles blocking a normal egress route from the scene contributed to a poor patient outcome, delaying the definitive care required in severe trauma cases. The patient was pronounced deceased at SFGH approximately 20-30 minutes after arrival due to severe blunt-force trauma.”
Cruise has spoken out against the Fire Department’s account of the event. In a comment to The San Francisco Standard, a Cruise spokesperson noted that “we did not impede the vehicle from getting to the hospital” and “what the fire department said is not accurate.”
“The first vehicle promptly clears the area once the light turns green and the other stops in the lane to yield to first responders who are directing traffic. Throughout the entire duration the AV is stopped, traffic remains unblocked and flowing to the right of the AV. The ambulance behind the AV had a clear path to pass the AV as other vehicles, including the ambulance, proceeded to do so. As soon as the victim was loaded into the ambulance, the ambulance left the scene immediately and was never impeded from doing so by the AV,” Cruise noted in a statement.
Cruise has reportedly provided a video to back up its claims. The video reportedly showed that while one Cruise robotaxi was indeed stopped at an intersection, there was a free lane to its right where traffic was moving. The video, which was reviewed by Forbes, did show numerous vehicles, including a small ambulance, moving through the free lane. However, the publication noted that it was not clear from the footage if the larger SFFD ambulance, which was likely transporting the severely injured pedestrian, could have navigated the area as easily.
Below are incident reports from the San Francisco Fire Department. The case in question is described in Page 68 and 69 of the document.
Cruise San Francisco Reports by Simon Alvarez on Scribd
Don’t hesitate to contact us with news tips. Just send a message to simon@teslarati.com to give us a heads-up.
The in-car Tesla Theater is among the most unique features available within the cars. When charging, parked, camping, or just hanging out, vehicle occupants can access a variety of streaming platforms on the large center screen, helping keep them entertained during downtime.
However, the Theater might be getting plenty more streaming platforms, something that owners have requested for some time.
Tesla owners recently discovered that visiting Apple TV in the vehicle browser can launch a fullscreen interface that looks and behaves like a dedicated application rather than an ordinary webpage:
Today I learned that if you go to Apple TV in the Tesla browser, it will open up an actual Apple TV app, fully functional. Not just the site.
Apparently there are more apps than just the few that show on the apps page. pic.twitter.com/os1Ypfm4JR
— Jason W (@jmwilt21) August 20, 2026
The experience drops the usual address bar and browser chrome, presenting catalogs, continue watching rows, and playback controls in the same window Tesla Theater already uses for its listed services. Independent testers soon found similar treatment for HBO Max, Paramount+, Peacock, Disney+, and Prime Video when those sites are opened from the car browser.
This shift is a plausible early signal that Tesla is widening Theater support without a formal software note. Theater has long been a set of web views rather than native applications, so recognizing extra domains and stripping the browser frame is a small server-side change that can expand the catalog quickly.
Owners still lack permanent Theater icons for the newly recognized services, and video remains limited to Park, yet the smoother launch is a meaningful step toward a broader lounge while charging.
Tesla Theater arrived with software version 10 in September 2019. The first video services were Netflix, YouTube, and Hulu, available only while parked and originally tied to WiFi. Spotify arrived in the same era as music rather than Theater video. Disney+ joined officially in July 2021 with the 2021.24 update, giving owners another major catalog on the center screen. Twitch and TikTok later appeared among the default Theater tiles, and Tesla Tutorials remained a persistent educational tile.
Not every addition stayed put. In December 2023, a Holiday software build removed the Disney+ tile for many United States owners after a public dispute involving advertising on X. Hulu stayed visible even though Disney owned it. Visiting disneyplus.com in the browser often restored the tile, which suggested the removal was a recognition list change rather than a complete block. Owners have also reported occasional blank Theater grids after updates, usually fixed by language toggles, resets, or later firmware.
Tesla axes Disney+ from vehicles with Musk-Iger rivalry, but there’s a workaround
Code archives from 2024 listed many unused source names, including Apple TV and Prime Video, that never became official icons, which now looks like groundwork for the current fullscreen browser behavior.
Now that this hint toward an expanded Theater experience has been recognized, Tesla could follow through with these additional shortcuts as a sign that more streaming platforms are available in Teslas than ever before.
Tesla recently received its largest order for the all-electric Semi from Einride, a Swedish transport service, for 500 units, a groundbreaking invoice to receive before the first deliveries begin.
Even more remarkable, Einride CEO Roozbeh Charli said in a recent interview that he expects his company to take delivery of all 500 — the entire order — before the end of 2027. He even expects to have 75 Tesla Semi units in the Einride fleet before the end of this year.
🚨 Einride CEO Roozbeh Charli on the Tesla Semi partnership:
“If we start with the Amazon announcement that we did earlier this year, that was on the back of having gone through a proving period together with them and proving out our technology. Then we took that next step in… pic.twitter.com/oazkXjwoig
— TESLARATI (@Teslarati) August 28, 2026
Charli said the Tesla partnership was part of a broader push, along with its earlier partnership with Amazon. Einride is assisting Amazon with the use of its Saga AI platform, which helps eliminate questions about budgeting and forecasting for logistics companies.
The Semi, as well as Tesla’s production and subsequent delivery of the units to Einride, will help the company “to have a good supply of vehicles that we can deploy on the [Saga AI] platform,” Charli said. “Tesla is also a relationship we’ve had for a while, and as the Tesla Semi deliveries are firming up, we decided to do a larger commitment to that and deploy that on our platform.”
In its initial announcement, Einride said it anticipated taking delivery of the trucks over the next two years, but now it appears the company is expecting all 500 units within the next 16 months.
Built at a dedicated factory in Sparks, Nevada, the Tesla Semi has been perhaps the biggest and most intensive testing process the company has ever had for a single vehicle model. For the past several years, Tesla has been working with many companies, most notably Frito-Lay and PepsiCo, to gain knowledge on the performance on regional routes.
Tesla plans to launch the Semi officially on September 24, five months after production started ramping.
Additionally, drivers have said they are happy about the Semi’s performance and that its numerous safety and productivity features have made their jobs and routes much easier.
Tesla Cybercab is using a unique strategy for picking up the correct rider, which is a crucial part of ride-hailing to ensure people end up in the right place and are charged the correct price.
Cybercab will utilize an RGB strip in its front light bar that will illuminate in a variety of different colors to mark itself.
This identifying mark will also appear in the Robotaxi app, giving riders in the same location a notable distinction in an effort to avoid any confusion regarding who should get in each vehicle.
🚨 Tesla is using different light bar colors to help riders understand which vehicle is theirs
Pretty cool strategy pic.twitter.com/eGMpEMeRpc
— TESLARATI (@Teslarati) August 27, 2026
Other ride-hailing services use similar strategies: Lyft and Uber rides are recognizable through driver identity, vehicle type and color, as well as license plate. Waymo will display the rider’s initials on top of the vehicle, letting them know that the specific vehicle for them has arrived.
Tesla’s strategy is unique and interesting, but there are some flaws. Cybercab’s main purpose is aimed toward being an autonomous ride for all, including those who have disabilities like being blind or even color blind.
Tesla will likely have something in the pipeline for those who cannot see colors or have limited vision. There will definitely be multiple ways to identify which vehicle is the one that “you” specifically ordered.
Cybercab is set to start giving public rides next Thursday, September 3, in Austin, as it announced a dedicated event last week and invited many members of the Tesla community.
Additionally, members of the public will be invited as well. Tesla has been offering employee rides in Cybercab for nearly two months.
Tesla Theater might be getting plenty more streaming platforms
Tesla Semi’s biggest adoptee gives an update on production timeline
