San Francisco Mayor Daniel Lurie has sent a letter to the California Department of Transportation (Caltrans) asking the agency to establish statewide standards for autonomous vehicle operations, following two high-profile incidents in which Waymo robotaxis became stranded and paralyzed city traffic. The San Francisco Chronicle first reported the letter, with TechCrunch confirming the details on July 16, 2026 TechCrunch.

Lurie's letter cited two specific events. The first was a widespread power outage in December 2025 that left Waymo vehicles immobilized on city streets. The second occurred during the July 4 Golden Gate Bridge fireworks show, which drew an estimated 100,000 spectators and produced gridlock complicated by stranded robotaxis TechCrunch. The Chronicle had reported on the transit fallout from that event the following day, noting that Caltrans representatives did not respond to requests for comment on July 5 SF Chronicle.

Waymo currently operates an estimated 1,000 robotaxis across the Bay Area as of July 2026 TechCrunch. At that fleet scale, even a small percentage of vehicles encountering edge-case scenarios during a surge event translates into dozens of immobile cars blocking active lanes.

Lurie's letter to Caltrans proposed four specific requirements for autonomous vehicle companies. First, companies should be required to immediately remove or relocate robotaxis from active travel lanes when they become immobilized. Second, companies should adapt in real time, adjusting routes, service areas, and pick-up and drop-off locations in response to changing conditions. Third, companies should share real-time operations data with local agencies, including service disruptions, locations of immobile robotaxis, and recovery efforts. Fourth, companies should demonstrate through testing that they can handle large influxes of people and traffic before deploying at scale TechCrunch.

The letter is directed at Caltrans, not at the California Public Utilities Commission. That distinction matters because California's autonomous vehicle regulatory framework involves two separate permit processes: one administered by the Department of Motor Vehicles and the other by the CPUC. The DMV pathway covers testing and deployment permits, while the CPUC regulates commercial passenger service under its transportation charter-party carrier framework. Lurie is effectively asking a state transportation agency to weigh in on operational standards that have, to date, been addressed primarily through the DMV and CPUC permitting processes TechCrunch.

The proposed requirements, if adopted, would push AV operators toward a more dynamic operating posture than the current model allows. The real-time data-sharing proposal is the most consequential of the four. It would create a live operational feed from AV companies to local traffic management and emergency response agencies, a capability that does not currently exist in any formalized framework. Local agencies would gain visibility into fleet locations, service disruptions, and recovery efforts as they unfold rather than after the fact.

The real-time adaptation requirement, similarly, would compel operators to adjust routing and service boundaries dynamically during large events and emergencies. The July 4 fireworks scenario is the case study: a sudden influx of 100,000 people into a concentrated area, combined with intermittent road closures, produced conditions that apparently exceeded the operating envelope of deployed vehicles. Lurie's proposal would require companies to prove, through testing, that their systems can handle such surges before being permitted to operate in them.

Worth flagging is the governance question the letter raises. By addressing Caltrans rather than the CPUC or DMV, Lurie is reaching for a state-level authority that sits outside the existing AV permitting structure. Whether Caltrans has the statutory mandate to establish the kind of statewide operating standards Lurie envisions is an open question. The agency had not responded to Chronicle inquiries about transit problems related to the July 4 event as of July 5 SF Chronicle, and the regulatory pathway for implementing any of the four proposed requirements has not been detailed.

The broader context is that San Francisco has been the primary testing ground for commercial autonomous ride-hailing in the United States, and the city's relationship with AV operators has moved through phases of friction and accommodation. A fleet of roughly 1,000 robotaxis operating across the Bay Area represents a scale where edge cases are no longer rare events but recurring operational challenges. The December power outage and the July 4 fireworks are different categories of disruption, one infrastructure-related and one demand-related, but they converge on the same failure mode: vehicles that cannot move and cannot be moved quickly enough to keep lanes clear.

What Lurie's proposals would enable, if implemented, is a tighter feedback loop between AV fleet operations and the city's traffic management infrastructure. The data-sharing requirement alone would give San Francisco agencies something they have not had during prior incidents: a real-time picture of where AV failures are occurring and what recovery actions are underway. The testing requirement would shift the burden of proof onto operators to demonstrate surge resilience before deployment rather than after a public failure.

The letter is a proposal, not a regulation. None of the four requirements carry the force of law, and the path from mayoral letter to enforceable standard runs through Caltrans, the DMV, the CPUC, or some combination of all three. What it signals is that a city absorbing the daily operational impact of a large commercial AV fleet is now asking for structural changes to how that fleet is governed.