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
SpaceX just combined Grok, Cursor, and X into one mega plan
SpaceXSI merges Grok, Cursor, and X Premium into one plan, raising questions for Tesla owners.
SpaceX Super Intelligence has rolled out The X Subscription, a single plan that combines Grok, Grok Bot, Cursor, and X Premium.
There are five levels, including a free plan that includes daily Grok access and a starter allowance for Cursor’s coding agents. Plus is $8 per month, Premium is $30, Super is $100, and Ultra is $200. Usage scales as you move up, with Premium offering four times the Plus allowance, Super 15 times, and Ultra 50 times. Annual billing brings the prices down a bit further, with Premium at $300 per year.
We’ve unified plans across Grok, Cursor, and X Premium.
Introducing The X Subscription. https://t.co/SvkrVvBa0p
— SpaceX Super Intelligence (@SpaceXSI) October 12, 2026
The $30 Premium tier is where SpaceXSI says it packs the benefits of SuperGrok, Cursor Pro, and X Premium+, which previously added up to $90 per month. Grok Bot, the agent that handles tasks like ordering food or managing a calendar, is included from Premium upward but not on Plus. Paid plans share one weekly usage pool across Grok and Cursor, and each plan includes at least twice the coding usage of the comparable Cursor plan. Third party models in Cursor remain available on Premium and above, but they are billed separately at API list prices.
That last detail matters because of what has happened around Cursor this year. SpaceX exercised its option to buy the company for $60 billion in June, and the deal closed in August. Weeks later, OpenAI said it will cut Cursor’s access to its models on November 12. Bundling Cursor with Grok usage gives SpaceXSI a reason to steer developers toward its own models.
Tesla integrates Grok Bot into its vehicles for the ultimate personal assistant
For Tesla owners, the connection is Grok Bot. Tesla brought it into its vehicles last month, and at that point access inside the car was limited to SuperGrok Heavy subscribers. Grok Bot is now enabled across every Cybercab and the rest of the Model Y Robotaxi fleet. Neither SpaceXSI nor Tesla has said how the new plans change inside the car access for owners, or whether a $30 Premium subscription now covers Grok Bot in a personal Tesla. That is the question owners will want answered first.
The company is also changing its name along the way. The rollout follows the rebrand Musk announced on October 4, when he said SpaceXAI would become SpaceXSI, and the plan page now carries that branding.
The X Subscription is available to new customers starting now, and SpaceXSI says it will reach everyone globally over the next few days. Existing SuperGrok, Cursor, and X Premium subscribers do not have to switch. The option to move will appear gradually in billing settings, with a prorated refund for the unused time on the old plan. Switching is permanent once the accounts are unified, and old plans are closed to new sign ups.
Energy
Taiwan power firm bets big on Tesla Megapacks as AI data center thirst grows
Taiwan’s Apollo Power orders 260 Tesla Megapacks, betting AI data centers will need more electricity.
A Taiwanese power company has ordered 260 Tesla Megapack 2XL units, roughly 1GWh of storage, betting that electricity rather than chips will decide how fast AI data centers come online. Apollo Power signed the contract with Tesla’s Taiwan energy arm on October 8, according to the company’s filing with the Taiwan stock exchange.
The filing says the units are meant for behind the meter storage and resilient grid projects, with delivery in batches from the end of 2027 and sites operating in 2028. Apollo and Tesla did not disclose a price, citing a confidentiality agreement. Apollo plans to pay for the equipment through a cash capital increase and bank financing, and it noted the purchase is not revenue and does not mean it holds firm orders from its partners.
Biggo reported that only about 33 units are under signed customer contracts, with roughly 150 more in negotiation. The same report put total project investment near NT$130 billion, but that figure includes installation work, with the equipment itself making up about 40 to 50 percent. In other words, a large share of this order is Apollo reserving supply ahead of demand. Apollo’s chairman told local media global large storage supply is tight, which is why the company locked in the units early, according to Yahoo Taiwan Finance.
Apollo also launched an AI data center and grid resilience alliance with Phison, Gigabyte and Shihlin Electric. The pitch rests on a pilot at Phison’s Zhunan plant, where Apollo and Tesla Energy Taiwan installed grid forming Megapack 2XLs in June. Tesla Energy Taiwan general manager Sun Hsiao-Han said the project went from demo to 1GWh in four months, and that Tesla Energy has deployed more than 50GWh worldwide.
Taiwan’s cabinet has approved amendments that would require large energy users to install their own generation and storage, which gives enterprise storage a regulatory tailwind.
The deal fits a pattern Teslarati has tracked. Tesla’s Megablock targets 1GWh commissioned in 20 business days, a pitch aimed squarely at fast moving data center builds. Megapacks already back xAI’s Colossus in Memphis and a 400MW AI campus in Brazil. Sun Media adds that Megapack 2XL was named among the first products in Nvidia’s DSX Ready qualification for battery storage in AI factories.
Deliveries are more than a year away, so the real test is how much of that 260 unit order turns into signed customer contracts.
For a century, the car has asked the same thing of its owner, which is basically to pay attention. Even the best ride-hailing app like Uber or Lyft only moved the problem into someone else’s hands. You stopped driving, but you still sat in a stranger’s car, while half listening, and wondering whether to take a phone call in the car without being rude. The Cybercab has no wheel, no pedals and no driver. With Grok @bot now live inside it, it becomes something else entirely, and I think that matters more than the fleet count that everyone is tracking.
Grok @bot is an agent, not a voice assistant. A rider signs in once, and from then on can say what they need and watch it happen. Order dinner from a favorite restaurant. Fill the grocery cart. Move money, answer email, adjust a calendar, push a work project forward. Tesla engineer Yun-Ta Tsai confirmed it is enabled across every Cybercab and the rest of the Model Y fleet, and Tesla’s own pitch is that Full Self-Driving handles the commute while Grok handles the errands.
Think about what that does to a thirty minute ride. Uber sells you a trip, while Waymo sells you the same trip in a more private setting. Tesla is selling the thirty minutes themselves, returned to you with an assistant attached. Errands that used to eat a Saturday get done between pickup and drop off. The ride stops being dead time between two places and becomes a place of its own.
Tesla integrates Grok Bot into its vehicles for the ultimate personal assistant
Best of all, your Bots follow you into any Cybercab, and presumably your own Tesla, then logs you out automatically when you step out. Anyone can bolt a chatbot onto a screen, but much harder to own the vehicle, the autonomy stack and the assistant at once. It also quietly ties SpaceX’s Super Intelligence business to Tesla’s fleet, after Tesla converted its xAI stake into SpaceX equity. The relationship between those two companies is getting harder to describe as separate.
This is also where the hard questions start, because an agent that can spend your money in a vehicle other people also ride in needs some answers. How does it handle a voice it shouldn’t trust? What gets recorded, who can see it, and for how long? What happens when a rider leaves halfway through a task?
If Tesla gets those answers right, the scoreboard changes. We have been counting Cybercabs and wait times. The more telling number may be what riders accomplish per trip. That is data almost no one else will ever have, and it is the real reason to watch Grok @bot.
What do you think? Leave me a comment.
SpaceX just combined Grok, Cursor, and X into one mega plan
Taiwan power firm bets big on Tesla Megapacks as AI data center thirst grows
Tesla Cybercab and Robotaxi’s real advantage won’t be the ride service
The Pentagon taps Elon Musk to design the battlefield of the future
Tesla Roadster’s new patent preps white-knuckle speeds, keeping it grounded
