Robotaxis Aren’t as Autonomous as They Seem
SubscribeSign in
Robotaxis Aren’t as Autonomous as They Seem<br>Calling robotaxis autonomous flatters the technology and hides who is responsible when something goes wrong. The real issue is not just the vehicle. It is the system around it.
Bryan Reimer<br>May 19, 2026
11
Share
(Image: iStock)<br>When my 12-year-old looked up the word autonomous, the definition was straightforward: self-governing, independent. That is exactly why the term breaks down when applied to robotaxis.<br>Thanks for reading Junko's Tech Probe! Subscribe for free to receive new posts and support my work.
Subscribe
Calling them autonomous flatters the technology and hides who is responsible when something goes wrong. It shapes how the public and policymakers understand these systems. Autonomous suggests a machine that governs itself.<br>But the systems now being deployed on public roads, especially robotaxis, rely on human support, operational oversight, maintenance, and institutional coordination that the label obscures. Calling these vehicles autonomous does not just flatter the technology. It narrows accountability.<br>That matters because language shapes governance. If leaders believe they are regulating a self-sufficient machine, they may focus too narrowly on the vehicle itself: its sensors, software, and safety record. But if these systems are service networks with hidden human inputs and fragile dependencies, the policy questions become more urgent. The real question is whether policymakers are willing to regulate the whole system rather than the branding around it.<br>Military drones are often discussed as though they operate alone, even when they rely on remote operators, communications links, intelligence inputs and institutional rules of engagement. The machine may be distant, but the system remains deeply human.<br>The same is true on public roads. Robotaxis may remove the driver from the front seat, but they do not remove people from the system.<br>The Human Layer Behind Robotaxis
For years, the story around robotaxis was simple: cars that drive themselves, less human error, safer streets, cheaper rides.<br>The reality is more complicated. These systems do not run themselves. Someone answers rider questions. Someone cleans the sensors. Someone sits at a desk ready to step in when the car gets confused. There is maintenance, software updates, and mapping refinements. None of that is glamorous, but it is what keeps the service running.<br>This does not delegitimize the technology. If anything, it clarifies what makes it work. Redundancy and human backup may be exactly what makes these systems as safe as they are. But the public deserves a more honest accounting of what autonomous really means in practice. At that point, autonomous starts to look less like a technical description and more like a marketing choice that has stuck for too long.<br>The Governance Question Cities Cannot Dodge
Many local leaders are made to feel they are either pro-robotaxi or anti-innovation. That is a false choice.<br>The real question is whether officials understand what is being deployed on their streets and are willing to govern it, rather than simply get out of the way. Cities do not need to design the technology. But they do need to coordinate with firms to shape how the service operates in public space.<br>That means asking questions well beyond vehicle performance. Who provides remote assistance, and from where? What standards govern intervention? What happens when communication fails, or when flooded roads and other edge cases create uncertainty? Where do vehicles go when they are not on active rides? How should residents report unexpected or unsafe behavior? How are vehicles maintained, inspected, cleaned, and recalibrated? How do emergency responders interact with the vehicle and its remote support? How quickly can local officials obtain meaningful records after an incident?<br>California’s new regulations may begin to point the way, but cities and states cannot answer these questions on their own. They will need shared frameworks, coordination with technology providers and other stakeholders, and a broader view of what these systems involve. These issues are central to public safety and public trust and are too complex for individual localities to manage alone.<br>I remain skeptical that robotaxis will deliver the low-cost rides often promised. The layers of redundancy are expensive. That does not mean the business cannot succeed. It means profitability may be harder than many investors and innovators expect.<br>When profitability proves difficult, pressure to cut costs follows. Unless governance keeps pace, cost pressure will create incentives to weaken some of the support layers that currently make these systems publicly acceptable. Elected officials, not just corporate leaders, should be debating those tradeoffs.<br>The same logic extends beyond safety. Will these services lower transportation costs, or simply shift costs into...