Tesla delays Full Self-Driving beta rollout to ~1,000 drivers with perfect safety scores of 100, Elon Musk says due to a “few last minute concerns”
The “Full Self-Driving” update was supposed to roll out to 1,000 more Tesla owners Friday — Tesla has delayed the rollout …
Context & Ripple Effects
Tesla had just expanded access by letting owners request the beta, a move that drew criticism from regulators and safety advocates. The delay interrupts that broader-access step and is consistent with Tesla's earlier description of the beta as an extremely slow and cautious rollout.
The subsequent rollback from FSD version 10.3 to 10.2 gives the stated last-minute concerns added significance: Tesla was still changing deployment decisions in response to identified issues.
First-order effects
- The roughly 1,000 owners selected through Tesla's safety-score gate do not receive the planned FSD beta update on schedule, while Tesla holds the release for further review.
- Tesla's beta program remains constrained by a safety-score-based access process rather than moving immediately to the next cohort of drivers.
Second-order effects
- Regulators and safety advocates that criticized the request-based expansion gain a concrete example of Tesla pausing a broader beta release over safety-related concerns.
- Tesla must balance the value of gathering beta feedback from more drivers against the operational risk of releasing software that may require a rapid rollback.
Third-order effects
- If repeated pauses and reversions accompany wider beta access, safety gating and staged releases become a more central form of operational AI governance for Tesla's driver-assistance software.
- The episode points to a deployment model in which the pace of consumer-facing autonomy features is set as much by release controls and safety review as by feature development.
The trend: Consumer-facing driving automation is being deployed through progressively gated software betas, with release governance determining how quickly access expands.