THE CALIFORNIA PERMIT APPLICATION DELAY ?

 

GROK:

Tesla has not applied for a driverless (autonomous) permit in California—including for operations in San Francisco—because it hasn't met the state's basic prerequisites, and its current robotaxi efforts in the Bay Area aren't truly driverless.

As of May 2026, here's the situation based on official California DMV records and regulator statements:

• Tesla (via Tesla Robotaxi LLC) only holds the entry-level DMV permit for testing autonomous vehicles with a safety driver on board. This has been in place since 2014 and allows testing on public roads but does not permit driverless operation or charging passengers for rides in autonomous mode.
• It has not applied for driverless testing or deployment permits from the DMV, nor the additional CPUC approvals needed for commercial autonomous passenger service (robotaxis). DMV and CPUC spokespeople have repeatedly confirmed this.
• Tesla logged zero autonomous test miles in California in 2025 (the sixth straight year of essentially none). Its total since 2016 is only about 562 miles—nowhere near the ~50,000 supervised miles required under DMV rules before even applying for a driverless permit.

Why the delay?
California's rules are strict for a reason (safety data, public reporting, incident transparency). To go driverless, companies like Waymo had to:

1. Test extensively with drivers.
2. Apply for and get driverless testing approval.
3. Then get deployment approval for paid rides.

Tesla has skipped steps 2 and 3. Its "robotaxi" activity in the Bay Area is actually a chauffeur service with human drivers using FSD (Supervised)—classified as SAE Level 2 driver assistance, not true autonomy.
Regulators explicitly say it's not an autonomous vehicle service and falls under the same rules as a limousine company (via its TCP/Charter-Party Carrier permit). No AV-specific safety reporting or transparency is required.
Broader context on the "threshold of robotaxis flooding the streets"
The hype around Tesla robotaxis (Cybercab unveil, production ramp plans) is real, but the regulatory and technical reality in California lags:

• Tesla's core approach is vision-only FSD trained on billions of customer fleet miles nationwide, not city-specific geo-fenced testing like Waymo/Cruise. It prioritizes software that works everywhere over proving it in one tough market like SF first.
• True unsupervised robotaxis are rolling out (or planned) faster in states with simpler rules (e.g., Texas, Arizona). California is notoriously complex due to its hills, dense traffic, pedestrians, and strict oversight.
• Purpose-built Cybercabs are entering production, but CA deployment still requires those missing permits + miles. No evidence of recent applications as of May 2026.

In short, Tesla isn't "on the threshold" in San Francisco the way Waymo is—it's deliberately taking a different path that avoids heavy CA-specific testing so far.
Regulators say they're ready to review applications whenever Tesla submits them, but the company hasn't. The gap between Musk's timelines and CA bureaucracy is a recurring theme here. If/when unsupervised FSD hits the level needed, expect Tesla to pursue the permits then.

Tesla has given no official timeline for when it will reach the California-specific regulatory threshold to apply for a driverless permit (the ~50,000 supervised autonomous test miles in the state plus formal DMV application).

As of late May 2026, the company has made zero visible progress toward it:

• Still only holds the basic “testing with a safety driver” permit (unchanged since 2014).
• Has logged zero autonomous test miles in California in 2025 (and virtually none for years prior—total lifetime ~562 miles).
• Has not applied for driverless testing or deployment permits, per repeated DMV and CPUC confirmations.

Why the lack of a firm date?
Tesla’s entire autonomy strategy is deliberately different from Waymo/Cruise:

• It does not rely on massive geo-fenced, state-specific test fleets in California. Instead, it uses billions of real-world miles from the customer FSD fleet nationwide (vision-only, end-to-end neural nets).
• The company has repeatedly said it will deploy unsupervised FSD first in easier regulatory environments (Texas, Arizona, etc.) and only later tackle California’s stricter rules.

Closest “expected” milestone

• Unsupervised FSD (true driverless, no human in the car) for consumer vehicles and robotaxis is currently targeted for Q4 2026. Elon Musk reiterated in mid-May 2026 that robotaxi operations without safety monitors “probably will be widespread in the U.S. by end of this year.”
• Once that national unsupervised capability is proven reliable, Tesla would likely submit its CA permit applications (using the mountain of fleet data it already has).
• Even then, California approval isn’t automatic—it still requires the in-state supervised miles (or equivalent data the DMV accepts) plus CPUC commercial-service sign-off. Historical precedent with other companies shows this step can take months to years.

Bottom line for San Francisco / California
True driverless robotaxis in the Bay Area are not expected before late 2026 at the earliest, and more realistically 2027 or beyond.
Tesla is already running paid robotaxi rides in Texas cities (Austin, Dallas, Houston) without safety drivers and plans rapid expansion elsewhere in 2026. California remains the notable exception because Tesla has chosen not to play the traditional “log miles here first” game.
In short:
the “threshold” you asked about is tied to Tesla’s broader unsupervised FSD milestone (target: Q4 2026).
They haven’t started the California-specific clock yet, and regulators say they’re ready whenever Tesla decides to file.


The gap between Musk’s ambitious national rollout plans and California’s bureaucracy continues.


https://teslasharetrend.blogspot.com/2026/01/perfect-fsd-impossible.html