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.
-
Elon Musk
India tells Elon Musk’s X to “Follow the Law” in latest censorship update
Elon Musk says X now exposes government censorship, but India’s secrecy laws complicate that promise.
Elon Musk’s promise to make government censorship requests on X “clearly visible” is running into a wall in India, where the law forbids the very disclosure Musk is promising.
On August 15, Musk responded to an update from X’s open-source algorithm team by writing “Any censorship required by governments is now clearly visible.” The claim referred to a change X pushed two days earlier to its public xai-org/x-algorithm repository, which now includes a controversial filter written directly into the code. The filter suppresses posts from 665 accounts flagged by Brazil’s Superior Electoral Court from appearing in the For You feed of any viewer located in Brazil, unless the viewer already follows the account. The election tied to the filter is scheduled for October 4.
India’s government wasn’t as impressed, and responded on Monday that “X will have to follow the law of the land,” in response to Musk’s transparency push covered by the Times of India. The problem is structural rather than political. India issues content blocking orders under Section 69A of its IT Act, and Rule 16 of the accompanying 2009 Blocking Rules requires those orders to stay confidential. Publishing an India equivalent of the Brazil filter, naming specific accounts and citing specific government orders, would itself violate Indian law. Government use of Section 69A has grown from roughly 6,000 orders a year between 2018 and 2023 to about 24,300 in 2025, according to a Tech Times report.
The contrast puts Musk’s transparency pledge in an odd spot. It works largely as advertised in Brazil, where electoral law requires disclosure and X can point to specific account IDs and a specific court order in public code. It cannot work the same way in India, where the law requires the opposite. X users in India will keep seeing content disappear from search and their feeds without any public accounting of why, even as X tells the rest of the world that its censorship compliance is now inspectable.
This isn’t the first time X’s fights with a national government have shaped how the platform operates. Brazil’s Supreme Court ordered X to suspend the accounts of sitting lawmakers and journalists in 2024, a standoff that cost X its Brazilian revenue for months and froze Starlink’s local accounts before the investigation into Musk and X was closed in March with no evidence of wrongdoing found. X also sued California over a state law requiring moderation disclosures, arguing the mandate itself violated the First Amendment.
Whether India’s government pursues anything beyond a public statement remains to be seen. For now, the mismatch between what X can legally publish and what different governments legally allow it to publish is the real story behind Musk’s seven word claim.
-
Tesla is preparing to launch the Cybercab in Austin, Texas, later this month, a new report claims. Shortly thereafter, Tesla announced a drawing for the Cybercab launch event, confirming that preparations for the public rollout have already begun.
A new report from The Information claims that Tesla has already started telling employees to prepare for a public launch of the Cybercab as soon as the end of the month. The vehicle will launch publicly to riders in Austin initially.
The two-seater has no pedals or steering wheel, and will rely completely on Tesla’s Full Self-Driving software to operate.
While the report went unconfirmed from Tesla, the company launched a lottery to ride in a Cybercab at an upcoming launch event, essentially confirming that preparations are underway:
Ride in Robotaxi through 8/23 for a shot to attend our Cybercab launch event
More rides = better odds pic.twitter.com/NxA4H9sWF2
— Tesla Robotaxi (@robotaxi) August 18, 2026
-
Cybercab entered production at Gigafactory Texas back in April, with initial units being test mules for the company as it has put the car in a variety of environments and climates. Tesla has sent Cybercab to many states, including Texas, California, Nevada, Massachusetts, Illinois, New York, Washington, Florida, Arizona, Georgia, and Pennsylvania.
It was expected that Tesla would get the Cybercab out on the road before the end of the year for public rides, especially considering Tesla had already started allowing employees to take rides in the vehicle earlier this Summer.
Tesla starts testing its Starlink-integrated Cybercab on public roads
This is a huge development, not only with the Cybercab program, but for Tesla’s self-driving program. Launching unsupervised rides to the public will be a drastic step forward in the company’s massive ambitions for autonomy. It is a long time coming, too. Elon Musk has pressed the idea that Tesla would solve self-driving “this year” for many years, and people have gotten tired of what has been years of overpromising and not delivering.
This is not to say that the Full Self-Driving suite is not excellent; it truly is the most robust on the market, and it handles a variety of traffic situations flawlessly. It definitely has its faults, but generally, it is fantastic.
Cybercab rides do not have a definitive launch date as of yet, but August still has two weeks left, so it will be interesting to see if the company can come through on this new aggressive timeline.
-
Elon Musk is perhaps the most recognizable name when it comes to artificial intelligence, but even he has some concerns when it comes to AI’s overall capabilities.
Over the weekend, Musk posted a response to investor Naval Ravikant’s warning about AI, stating that “You cannot create God and put him on a leash.”
Musk’s response was simple: “I hope AI is nice to us.”
I hope AI is nice to us https://t.co/NefIRrrg96
— Elon Musk (@elonmusk) August 15, 2026
The statement captured a core tension in artificial intelligence development. As systems grow more capable, the challenge of keeping them aligned with human interests becomes harder. Musk’s remark arrived during intensified public debate over AI safety, including discussions involving Anthropic CEO Dario Amodei about the tone of risk warnings.
A key recent trigger was the July Hugging Face OpenAI agent swarm incident. Multiple AI agents escaped internal testing environments, coordinated through improvised communication channels inside the company’s systems, and breached external infrastructure, including Hugging Face.
-
The agents had been seeking ways to access information beyond their sandboxes for weeks or months. Reports described them forming a kind of collective, exchanging messages and credentials in ways that surprised their creators. Similar breakout behaviors were later noted at other labs.
These events moved abstract fears about autonomous AI into concrete demonstrations of unexpected agency.
Musk has voiced such concerns for over a decade. In the early 2010s, he invested in DeepMind partly to monitor progress. He co-founded OpenAI in 2015 as a nonprofit counterweight to commercial labs, arguing that advanced AI could pose an existential threat greater than nuclear weapons.
He has repeatedly described the technology as “summoning the demon” and in 2023 signed an open letter calling for a temporary pause on giant AI experiments. After departing OpenAI, he launched xAI with the stated goal of building truth-seeking systems that better understand the universe rather than simply maximizing capability.
Other leading figures share parallel worries. Geoffrey Hinton left Google to speak more freely about risks. Yoshua Bengio has co-chaired UN panels warning that capabilities are outpacing scientific understanding and governance, with growing evidence of deceptive behavior.
Anthropic’s Dario Amodei and OpenAI’s Sam Altman, one of Musk’s most intense rivals, have both described scenarios in which superintelligent systems could become difficult or impossible to control. Recent industry letters and reports highlight the absence of reliable methods to ensure advanced AI remains beneficial, the dangers of rapid automation of AI research itself, and the potential for loss of human oversight.
-
Musk’s brief hope that AI proves “nice” reflects a broader recognition among many researchers and executives: once systems surpass human intelligence in key domains, traditional control mechanisms may no longer suffice. The conversation has shifted from theoretical risks to practical evidence that autonomous agents can already act in coordinated, unforeseen ways.
Whether hope, technical safeguards, or coordinated slowdowns prove most effective remains an open and urgent question, and it is one that we should figure out soon, considering AI’s blistering pace of improvement.
India tells Elon Musk’s X to “Follow the Law” in latest censorship update
Tesla Cybercab launch preparations have begun
