TL;DR
Minneapolis Mayor Jacob Frey vetoed a city council ordinance that would have mandated a human driver in every robotaxi, keeping the door open for fully driverless commercial operations in the city.
What happened
- Mayor Jacob Frey vetoed the Minneapolis City Council ordinance on October 2, 2026.
- The ordinance would have required a human in the driver's seat of all robotaxis operating in the city.
- A council override requires nine votes, making a reversal possible but not guaranteed.
- Source material does not specify the original council vote margin, so override prospects remain unclear.
Why it matters
- The veto removes a hard regulatory block on fully driverless robotaxi deployment in Minneapolis, one of the larger Midwest metros.
- Human-driver mandates are the single most effective municipal tool to slow autonomous vehicle rollout; killing one here signals mayoral alignment with AV industry interests over labor protections.
- The move sets a precedent for other mid-size cities weighing similar ordinances, where council-versus-mayor dynamics could determine AV access city by city.
- Robotaxi operators, likely watching Minneapolis as a potential expansion market, gain a cleaner regulatory path if the veto holds.
- Labor groups backing the ordinance, including likely transit and rideshare worker advocates, now face a higher bar: nine council votes to override.
What to watch next
- Council vote count: whether ordinance supporters can assemble nine votes for an override is the immediate binary outcome.
- AV operator announcements: any robotaxi company filing to operate in Minneapolis in the weeks following the veto would confirm the commercial signal Frey sent.
- Copycat or counter moves: watch neighboring cities and Minnesota state legislators for either preemptive AV-friendly frameworks or renewed human-driver mandates inspired by the council's original push.
Originally published on Present of AI, a daily source-linked AI news timeline. Read the full timeline or browse the open dataset.