Minneapolis council backs robotaxi human-monitor rule; Frey vetoes it
Council supporters want licensed human monitors inside commercial robotaxis. Mayor Jacob Frey calls that a backdoor ban and favors other regulation. Minneapolis council members failed to override his veto on October 15.
Case period:
Published by The Dispute Index editorial teamPublished Updated
Overview
The council's October 1 account of its adopted ordinance describes paid human monitors in the driver's seat, with immediate access to steering, braking and acceleration. Monitors would need to be at least 18 and hold a valid driver's license. The requirements concern commercial rides originating in Minneapolis. The council approved the measure 7-6 on October 1, with an October 1, 2027 effective date. Frey vetoed it the next day. On October 15 the council voted 7-5, with one absent, and the official legislative file records the veto as sustained. Frey favors regulation of operational issues but rejects a mandatory driver.
People in this case
Robin WonsleyDirectly involved
Jacob FreyDirectly involved
Timeline
3 timeline entries on this page. Dates: October 1, 2026 to October 15, 2026
October 2026
Council passes human-monitor rule
The council approves the robotaxi ordinance 7-6.
[01]Minneapolis describes the adopted human-monitor requirements
The council's October 1 bulletin describes the ordinance it had adopted, including paid licensed monitors in the driver's seat and the proposed October 2027 effective date.
Minneapolis describes the adopted human-monitor requirementsAutonomous vehicle regulations ordinance section[02]Minneapolis official autonomous-vehicle legislative history and votes
The official file identifies ordinance 2026-034, records its adoption and mayoral veto, and lists the veto as sustained after the October 15 vote.
Minneapolis official autonomous-vehicle legislative history and votesFile 2026-00738; October 1 and October 15 roll calls[03]Jacob Frey explains veto in FOX 9 interview
Frey objects to a mandatory human monitor while supporting regulation of safety and other operational issues.
Jacob Frey explains veto in FOX 9 interviewMayor Frey vetoes autonomous vehicle ordinance and Frey veto letter sectionsFrey vetoes the ordinance
Frey vetoes the human-monitor measure.
[02]Minneapolis official autonomous-vehicle legislative history and votes
The official file identifies ordinance 2026-034, records its adoption and mayoral veto, and lists the veto as sustained after the October 15 vote.
Minneapolis official autonomous-vehicle legislative history and votesFile 2026-00738; October 1 and October 15 roll calls[03]Jacob Frey explains veto in FOX 9 interview
Frey objects to a mandatory human monitor while supporting regulation of safety and other operational issues.
Jacob Frey explains veto in FOX 9 interviewMayor Frey vetoes autonomous vehicle ordinance and Frey veto letter sectionsCouncil fails to override veto
Seven council members voted aye and five voted nay, with one absent. The ordinance's official legislative file records the mayoral veto as sustained.
[02]Minneapolis official autonomous-vehicle legislative history and votes
The official file identifies ordinance 2026-034, records its adoption and mayoral veto, and lists the veto as sustained after the October 15 vote.
Minneapolis official autonomous-vehicle legislative history and votesFile 2026-00738; October 1 and October 15 roll calls[04]Minneapolis council fails to override robotaxi veto
FOX 9 reports the October 15 failure to reach the nine votes required to override Frey's veto.
Minneapolis council fails to override robotaxi vetoCity Council fails to override mayor's veto
Claims
Claims separate what was said from what is contested. Follow each source for the original wording and context.
What's disputed
Disputed claim
Minneapolis should require licensed human safety monitors inside commercial robotaxis.
Sources (3)
- Minneapolis describes the adopted human-monitor requirementsAutonomous vehicle regulations ordinance section
- Minneapolis official autonomous-vehicle legislative history and votesFile 2026-00738; October 1 and October 15 roll calls
- Proposed Minneapolis autonomous transportation ordinanceSections 342.10 and 342.90(d)-(e)
Response record
Responses
Choose one response filter, or select All responses to see the full record.
2 matching responses. Newest first.
Jacob FreyMayor of MinneapolisDirectly involvedBefore this statement
The interview followed the council's October 1 approval of the ordinance.
"It doesn't make sense to require a driver in a driverless car."
CondemnedCase context: Minneapolis council backs robotaxi human-monitor rule; Frey vetoes it
Full statement and sources
Frey says a required human driver defeats the model of driverless vehicles.
After the statement
He favors regulation of safety and operational issues instead.
Jacob Frey explains veto in FOX 9 interviewMayor Frey vetoes autonomous vehicle ordinance and Frey veto letter sectionsWhy this label?
The reference point is the mandatory human-monitor rule. Frey expressly rejects that requirement.
This label describes the statement's response within the context above.
Robin WonsleyMinneapolis city council memberDirectly involvedBefore this statement
The ordinance includes a city license for companies that originate rides in Minneapolis.
"Action: Voted aye on the Minneapolis autonomous-vehicle ordinance requiring human safety monitors."
Defended or excusedCase context: Minneapolis council backs robotaxi human-monitor rule; Frey vetoes it
Full statement and sources
Wonsley votes for the ordinance requiring human safety monitors inside commercial robotaxis.
After the statement
The council approved it 7-6. Frey vetoed it the following day.
Minneapolis official autonomous-vehicle legislative history and votesFile 2026-00738; October 1 and October 15 roll callsMinneapolis describes the adopted human-monitor requirementsAutonomous vehicle regulations ordinance sectionWhy this label?
The case concerns requiring human monitors inside commercial robotaxis. Wonsley supports that requirement through her recorded aye vote.
This label describes the statement's response within the context above.
Sources
(5)
Original text
Minneapolis official autonomous-vehicle legislative history and votes
Relevant passage: File 2026-00738; October 1 and October 15 roll calls
About this source
The official file identifies ordinance 2026-034, records its adoption and mayoral veto, and lists the veto as sustained after the October 15 vote.
- Accessed
Official statement
Minneapolis describes the adopted human-monitor requirements
Relevant passage: Autonomous vehicle regulations ordinance section
About this source
The council's October 1 bulletin describes the ordinance it had adopted, including paid licensed monitors in the driver's seat and the proposed October 2027 effective date.
- Published
- Accessed
Reporting
Minneapolis council fails to override robotaxi veto
Relevant passage: City Council fails to override mayor's veto
About this source
FOX 9 reports the October 15 failure to reach the nine votes required to override Frey's veto.
- Author
- FOX 9
- Published
- Accessed
Interview
Jacob Frey explains veto in FOX 9 interview
Relevant passage: Mayor Frey vetoes autonomous vehicle ordinance and Frey veto letter sections
About this source
Frey objects to a mandatory human monitor while supporting regulation of safety and other operational issues.
- Author
- Nick Longworth
- Published
- Accessed
Original text
Proposed Minneapolis autonomous transportation ordinance
Relevant passage: Sections 342.10 and 342.90(d)-(e)
About this source
The published proposal requires a licensed human monitor in the driver's seat with immediate access to controls and includes compensation requirements. This copy was posted before the October council vote.
- Author
- Robin Wonsley, Jamal Osman, Jason Chavez and Aurin Chowdhury
- Published
- Accessed
Share or embed this case
The embed keeps its attribution link to The Dispute Index. Credit the image to The Dispute Index and link to the case page.
Cite this record
- Publisher
- The Dispute Index
- Title
- Minneapolis council backs robotaxi human-monitor rule; Frey vetoes it
- First published
- Last updated
- Permalink
- https://disputeindex.com/cases/minneapolis-robotaxi-human-monitor-rule-frey-veto
The Dispute Index. "Minneapolis council backs robotaxi human-monitor rule; Frey vetoes it". First published: 2026-10-15. Last updated: 2026-10-15. https://disputeindex.com/cases/minneapolis-robotaxi-human-monitor-rule-frey-veto