Does remote-supervised robotaxi qualify as driverless?
Does remote-supervised robotaxi qualify as driverless?
The question
When a robotaxi has no driver in the vehicle but is monitored (and potentially remote-controlled on intervention) by human operators off-site, should that count as "driverless" / "unsupervised" autonomy? How do regulators, users, and observers draw the line?
Why it matters
Tesla markets its Austin/Dallas/Houston service as "Unsupervised Robotaxi," but the vehicles retain remote supervision 2026-04-20-autoresearch-tesla-fsd. waymo also uses remote assistance — but only on exception, not continuous monitoring (exact division between the two is unclear from available sources). California's CPUC has already drawn a line: Tesla's service is a chauffeur / TCP (limousine) service, not an autonomous vehicle service, regardless of who is in the front seat 2026-04-20-autoresearch-tesla-fsd.
What we currently believe
- Terminology ("unsupervised," "driverless," "autonomous") is being used inconsistently across operators and regulators.
- The regulatory category in California (AV permit vs TCP permit) matters more than the marketing label.
- Remote-supervision operating ratios — how many remote humans per vehicle, how often they intervene — are largely undisclosed by every operator.
Evidence we have
- CPUC: Tesla "is not operating an autonomous vehicle service"; its permit is the same type limousine companies hold 2026-04-20-autoresearch-tesla-fsd.
- Tesla would need ≥50,000 supervised autonomous miles before applying for CA driverless testing — a threshold not publicly approached 2026-04-20-autoresearch-tesla-fsd.
- Electrek's reporting: Austin unsupervised fleet is ~4–8 Model Ys with remote supervision 2026-04-20-autoresearch-tesla-fsd.
- Update (2026-08-24), do not close. Tesla's Q2 Update still labels the Bay Area as FSD (Supervised) under CA TCP
# TCP0046782 – Awhile listing Texas/Florida as "Ramping Unsupervised" 2026-08-24-autoresearch-tesla-fsd-robotaxi-jul-aug-2026. - Nevada (20 August 2026): NTA approved Tesla Robotaxi, LLC as an AVNC for paid rides in "fully autonomous vehicles" in Clark County (up to 5,000 in year one). That is a different regulatory category from California's TCP. Approval ≠ operations started (120-day clock; staff verification; airport needs a separate aviation authorization). The official order PDF was not retrieved 2026-08-24-autoresearch-tesla-fsd-robotaxi-jul-aug-2026.
- China (21 August 2026): SAMR S2026M0039I finds Tesla's existing driver-attention monitoring insufficient under combination driving assistance and requires cabin-camera monitoring — a regulator treating the stack as supervised L2 that still needs a watching driver 2026-08-24-autoresearch-tesla-fsd-robotaxi-jul-aug-2026.
Evidence we need
- Remote-supervision intervention rates for Tesla and waymo (minutes per ride, interventions per 1000 miles).
- Remote-operator fleet ratio for each operator.
- Whether other jurisdictions (Texas, Arizona, Nevada) are drafting their own definitions.
How to resolve
- Track regulatory filings and disclosures from both Tesla and Waymo.
- Watch for a state or federal attempt at a standardized "driverless" definition.