Topic
Vehicle software, connected features, and autonomous-driving capability.
Lyft says eligible trips in its central Nashville Waymo zone can now be matched to a fully autonomous Waymo at no added charge, and riders can decline or opt out.
AVP says it temporarily recognized RDW’s provisional approval on Sept. 7; Tesla says rollout will begin soon, while the system remains supervised driver assistance and the driver stays responsible.
Not a Tesla App calls 2026.27.6 the first public FSD 14.3.9 build, while Tessie and Teslascope also show nonzero distribution; those tracker samples do not establish Tesla-fleet penetration or safety effectiveness.
The Sept. 3 action covers 171 Heimer Road; San Antonio Express-News identifies the planned use as Tesla robotaxi parking and dispatch, but the zoning vote does not authorize rider service or establish construction timing.
Rivian says update 2026.31 moves both R1 generations onto its common software platform with R2; Gen 2 uses Unreal Engine 5, while Weather and Mobile Live Trips require Connect+.
Tesla’s Cybercab FAQ still limits Cybercab-specific ride availability to parts of Austin; its broader Robotaxi pages have since dropped the future-tense Cybercab wording seen on Sept. 3.
The dashboard’s fleet collision study uses 2024–2025 data frozen for RDW review and says some European comparisons rely on engineering vehicles or North American FSD collision data; Tesla’s newer five-country claim covers April–August 2026.
The Aug. 31 agreement turns their earlier SDV research into a joint development program, but the companies did not name a U.S. or Canadian model and do not describe the shared architecture as EV-only.
The recruiting description calls it a new role and assigns it partner-support infrastructure, incident escalation and team building. The posting does not name Uber or Nuro.
Lei Xing identified FSD 14.3.7 in the Aug. 26 report; NHTSA's PE25012 request separately asks Tesla for railroad-crossing incident flags, software versions, warnings, takeover timing, speeds, logs and system-response details. Neither establishes a systemic defect.
Flipturn’s current documentation says signed-off automations can run unattended and depicts a soft-reset workflow that escalates by text when a charger stays faulted.