/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

San Francisco asked California regulators to halt or scale back the expansion of Cruise and Waymo, after repeated incidents with stopped and idle robotaxis

SAN FRANCISCO — San Francisco is trying to slow the expansion of robotaxis after repeated incidents in which cars without drivers stopped …

NBC News David Ingram

Context & Ripple Effects

San Francisco's request to California regulators is the opening move in a fight over who controls driverless deployment: city officials had already complained they had no say as the state prepared to decide on allowing 24/7 Waymo and Cruise driverless cabs. The trigger was repeated incidents of stopped and idle robotaxis blocking city streets.

The request set the frame for the year that followed — the 24/7 rollout that brought traffic jams and obstructed emergency vehicles, the DMV's probe that forced Cruise to halve its fleet, and the eventual delay of Waymo's Los Angeles expansion application.

First-order effects

  • California regulators must now weigh San Francisco's halt-or-scale-back demand against Cruise and Waymo's expansion plans, with the city formally on record that repeated stopped-vehicle incidents justify restraint.
  • Cruise and Waymo face heightened scrutiny of every incident in San Francisco, since the city's complaint gives regulators a documented basis to condition or slow permit expansion.

Second-order effects

  • The incidents erode the public-trust foundation both operators need for 24/7 service — the same trust unraveling documented when the city opened fully to driverless cabs — raising the operational cost of incidents like Waymo paying workers via the Honk app to close doors and tow cars.
  • Rivals and city governments elsewhere watch San Francisco as the test case: a successful city intervention becomes a template for other municipalities seeking a voice in robotaxi deployment.

Third-order effects

  • If the pattern holds, US robotaxi expansion becomes gated by incident-driven regulatory pullbacks rather than pure technology readiness — as later seen when California delayed Waymo's Los Angeles and peninsula expansion application to June 2024.
  • The state-versus-city authority gap over autonomous vehicles is forced into the open, pointing toward a structural rebalancing in which municipalities win formal roles in permitting driverless fleets.

The trend: Robotaxi deployment in US cities is shifting from state-permitted, operator-paced expansion to incident-contingent growth, where municipal complaints and regulator probes — not technology milestones — set the fleet's size.

Discussion

  • @davidzipper David Zipper on x
    In their new letter to the CPUC, San Francisco leaders say that the city's emergency services were alerted to 92 “unique incidents” regarding robotaxis last year. A “large majority” involved Cruise. Here's a map. https://twitter.com/...
  • @davidzipper David Zipper on x
    SF's letter to CPUC about Cruise is available here: https://www.sfmta.com/... A separate (less damning) letter about Waymo is available here: https://www.sfmta.com/... Both were sent this week. https://twitter.com/...
  • @wiredscience @wiredscience on x
    City agencies say the incidents and other disruptions show the need for more transparency about the vehicles and a pause on expanding service. https://www.wired.com/...
  • @nbcnews @nbcnews on x
    San Francisco is trying to slow the expansion of robotaxis after repeated incidents in which cars without drivers stopped and idled in the middle of the street for no obvious reason. https://www.nbcnews.com/...
  • @david_ingram David Ingram on x
    Cruise and Waymo are racing to deploy more robotaxis in San Francisco. The city wants them to hit the brakes. https://www.nbcnews.com/... via @nbcnews
  • @aniccia John Berry on x
    Buried the lede: last week, San Francisco firefighters had to shatter a front window of an uncrewed Cruise AV to stop it from interfering with them fighting a major fire in the Western Addition These robot “drivers” are way too dangerously unintelligent. https://www.wired.com/...
  • @tsimonite Tom Simonite on x
    Three times since December, GM's driverless car unit Cruise called 911 in San Francisco because a passenger had become “unresponsive.” Each time, police and firefighters found the passenger had simply fallen asleep. The city says that wasted public funds. https://www.wired.com/..…
  • @aarianmarshall Aarian Marshall on x
    icymi, yesterday we published on a new letter from a clearly frustrated trio of SF agencies. They say the driverless vehicles operated by Cruise and Waymo are jamming up traffic, creating dangerous road situations, delaying public transit, and uh this https://www.wired.com/... ht…