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.
News
Apple is developing the missing link for Tesla to get CarPlay: report
A new report claims that Apple is in the process of developing what would be the missing link for Tesla to get CarPlay.
Apple and Tesla have been reportedly working together for some time to give Tesla owners the opportunity to utilize CarPlay within their vehicles. While many owners are more than happy with Tesla’s in-house UI, which is seamless, effective, and smooth, some still want CarPlay, which does have its advantages.
A report from 9to5Mac now states that a new CarPlay technology that was highlighted during the Worldwide Developers Conference (WWDC) would potentially be the bridge between Tesla and Apple. With the addition of a feature known as “Route Sharing,” which gives a navigation app the ability to share routing data with the vehicle, Tesla would be able to launch CarPlay in its vehicles, the report states.
CarPlay has not been a priority for Tesla because it has done extremely well with its in-house UI, but some drivers are just used to it. Additionally, it could improve Tesla’s subpar Navigation or offer improved app capabilities, especially with iMessage.
Route Sharing is an intended addition to CarPlay’s iteration in iOS 26.4, which was released in March:
The addition of CarPlay would undoubtedly be welcome, but at the same time, it seems like Tesla realizes it is not of the utmost priority. There are so many things that Tesla is working on currently within its own vehicles, especially attempting to solve self-driving.
Back in February, Bloomberg had reported that Tesla was still working on bringing CarPlay to its vehicles, but it had not due to app compatibility issues and incredibly low adoption rates of iOS 26.
This bottleneck could buy Tesla the proper amount of time to develop CarPlay for its vehicles. It would be a welcome addition, and could be brought on with either the Summer or Fall 2026 Software Updates.
Investor's Corner
Tesla deliveries get a big boost in expectations from Wall Street
Tesla deliveries got a big boost in expectations from Wall Street firm Goldman Sachs, who believes the company will report some stronger-than-expected numbers when the second quarter comes to an end in the coming weeks.
Goldman Sachs has raised its vehicle delivery forecast for Tesla (NASDAQ: TSLA) in the second quarter of 2026, signaling growing confidence in the electric vehicle leader’s near-term momentum despite mixed market signals. Analyst Mark Delaney lifted the bank’s Q2 estimate to 420,000 units from a previous 405,000, surpassing the Visible Alpha consensus estimate of 400,000.
The upward revision stems from stronger-than-expected sales data across key regions. Europe stands out with projected year-over-year growth of 85-90 percent, driven by robust demand for Tesla’s Model Y and refreshed offerings. China posted high single-digit gains, while markets like South Korea and Australia also contributed positive momentum. These gains help offset mid-teens declines in U.S. deliveries through May, where broader EV market headwinds and competition persist.
Goldman extended its optimism to the full year, increasing its 2026 delivery projection to 1.73 million vehicles from 1.72 million. Longer-term forecasts remain unchanged, with 1.88 million units expected in 2027 and 1.96 million in 2028. The bank also nudged its 2026 earnings-per-share estimate higher to $1.35 from $1.30, reflecting anticipated margin benefits from higher volumes and operational efficiencies.
Despite these positive adjustments, Goldman maintained its Neutral rating and $375 price target on Tesla shares. At current trading levels near $411, the stock sits about 8-9 percent above the target, highlighting ongoing valuation concerns even as delivery momentum builds. Tesla’s Q1 2026 deliveries totaled 358,023 units, setting a baseline for recovery expectations in the current period.
This update arrives as Tesla prepares to report official Q2 figures shortly after June 30. Investors and analysts will closely watch not only headline delivery numbers but also regional breakdowns, average selling prices, and progress on energy storage deployments and autonomous technology initiatives.
The move by Goldman Sachs underscores a broader narrative for Tesla: while legacy auto markets face softening demand and tariff uncertainties, Tesla’s global footprint and product pipeline provide resilience. Europe’s surge reflects pent-up demand and policy support for EVs, while China’s steady growth highlights Tesla’s competitive positioning against local rivals.
Tesla still has its work cut out for it, including U.S. price sensitivity and intensifying competition. Yet Goldman’s revision adds to a series of analyst notes suggesting Q2 could mark a turning point. As Tesla pushes toward higher production rates at facilities in Fremont, Shanghai, and Berlin, sustained execution will be key to validating these higher forecasts.
We have said numerous times that deliveries are becoming a less important metric in the grand scheme of things, as AI truly takes precedence in the company’s thesis.
For Tesla bulls, the Goldman note reinforces faith in underlying demand trends. For skeptics, the unchanged rating serves as a reminder that delivery beats alone may not immediately resolve valuation debates in a high-interest-rate environment. Tesla’s stock reaction will likely hinge on the official numbers and management commentary in the coming weeks.
News
SpaceX makes first acquisition post-IPO with coding leader Cursor
SpaceX has exercised its option to acquire Cursor, the innovative AI coding company, in an all-stock transaction valued at $60 billion. The deal, announced on June 16, marks a significant step in SpaceX’s expansion into advanced artificial intelligence, building on months of close collaboration between the companies.
Cursor, officially operated by Anysphere, Inc., is an AI-native code editor and coding agent designed to transform software development. Founded in 2022 by a group of MIT graduates in San Francisco, Cursor builds on the familiar foundation of Visual Studio Code but integrates powerful AI capabilities directly into the core experience.
Unlike traditional code editors or simple extensions, Cursor functions as a full “coding agent” that turns natural-language instructions into actionable code.
SpaceX has exercised the option to acquire @cursor_ai in an all-stock transaction with the goal of building the world’s most useful AI models.
For the past few months, SpaceXAI has been jointly training a model with Cursor, which will be released in Cursor and Grok Build soon.… https://t.co/X5mepgXgjJ
— SpaceX (@SpaceX) June 16, 2026
Developers interact with Cursor through features like its Composer agent, which can search entire codebases, edit multiple files, run terminal commands, debug issues, and complete complex multi-step programming tasks autonomously.
Users describe high-level goals, such as “build a scalable API endpoint with authentication,” and the AI plans, implements, tests, and refines the solution while the human oversees decisions. Additional tools include advanced autocomplete (Tab), context-aware chat, and infrastructure for handling billions of daily requests.
The platform has gained considerable traction, surpassing $3 billion in annual recurring revenue by early 2026 and earning adoption by over half of the Fortune 500 companies. Its agentic approach accelerates development dramatically, allowing engineers to focus on architecture and creativity rather than repetitive coding.
The acquisition integrates Cursor’s leading product, expert team of roughly 300 engineers, and distribution network among top software developers with SpaceX’s unparalleled computational resources. SpaceX’s Colossus supercomputer, equivalent to a million H100 GPUs, has already powered joint training of next-generation models. These models are expected to launch soon within Cursor and SpaceX’s Grok Build environment.
This combination positions SpaceX to develop the world’s most capable AI systems for coding and knowledge work. Access to Cursor’s real-world usage data from millions of professional developers provides unparalleled feedback loops for model improvement. Training on Colossus enables rapid iteration on massive datasets, potentially creating AI that outperforms current leaders in reliability, context handling, and complex reasoning.
For SpaceX, the benefits extend far beyond software tools. Rocket engineering, satellite constellation management, autonomous flight systems, and Starship development involve millions of lines of highly specialized, safety-critical code.
Cursor’s AI agents, supercharged by proprietary models trained on SpaceX’s domain expertise, could slash development timelines, reduce errors, and enable faster innovation cycles. This vertical integration of AI tooling strengthens SpaceX’s competitive edge in both aerospace and the broader AI race, complementing its xAI initiatives.
The deal reflects the exploding value of AI-native developer platforms. By owning Cursor outright, SpaceX secures a strategic talent pool and product pipeline that will accelerate internal projects while potentially offering enhanced tools to the wider engineering community. As AI continues reshaping software creation, this acquisition underscores SpaceX’s commitment to leveraging cutting-edge technology for ambitious goals, from Mars colonization to global connectivity.