The release notes for Tesla FSD Beta V11.3 have been shared online. Observers from the electric vehicle community suggest that Tesla Full Self-Driving Beta 11.3 is rolling out to the company’s employee FSD Beta testers, at least for now.
The following are Tesla’s FSD Beta V11.3 release notes:
- Enabled FSD Beta on highway. This unifies the vision and planning stack on and off-highway and replaces the legacy highway stack, which is over four years old. The legacy highway stack still relies on several single-camera and single-frame networks, and was setup to handle simple lane-specific maneuvers. FSD Beta’s multi-camera video networks and next-gen planner, that allows for more complex agent interactions with less reliance on lanes, make way for adding more intelligent behaviors, smoother control and better decision making.
- Added voice drive-notes. After an intervention, you can now send Tesla an anonymous voice message describing your experience to help improve Autopilot.
- Expanded Automatic Emergency Braking (AEB) to handle vehicles that cross ego’s path. This includes cases where other vehicles run their red light or turn across ego’s path, stealing the right-of-way.
- Replay of previous collisions of this type suggests that 49% of the events would be mitigated by the new behavior. This improvement is now active in both manual driving and autopilot operation.
- Improved autopilot reaction time to red light runners and stop sign runners by 500ms, by increased reliance on object’s instantaneous kinematics along with trajectory estimates.
- Added a long-range highway lanes network to enable earlier response to blocked lanes and high curvature.
- Reduced goal pose prediction error for candidate trajectory neural network by 40% and reduced runtime by 3X. This was achieved by improving the dataset using heavier and more robust offline optimization, increasing the size of this improved dataset by 4X, and implementing a better architecture and feature space.
- Improved occupancy network detections by oversampling on 180K challenging videos including rain reflections, road debris, and high curvature.
- Improved recall for close-by cut-in cases by 20% by adding 40k autolabeled fleet clips of this scenario to the dataset. Also improved handling of cut-in cases by improved modeling of their motion into ego’s lane, leveraging the same for smoother lateral and longitudinal control for cut-in objects.
- Added “lane guidance module and perceptual loss to the Road Edges and Lines network, improving the absolute recall of lines by 6% and the absolute recall of road edges by 7%.
- Improved overall geometry and stability of lane predictions by updating the “lane guidance” module representation with information relevant to predicting crossing and oncoming lanes.
- Improved handling through high speed and high curvature scenarios by offsetting towards inner lane lines.
- Improved lane changes, including: earlier detection and handling for simultaneous lane changes, better gap selection when approaching deadlines, better integration between speed-based and nav-based lane change decisions and more differentiation between the FSD driving profiles with respect to speed lane changes.
- Improved longitudinal control response smoothness when following lead vehicles by better modeling the possible effect of lead vehicles’ brake lights on their future speed profiles.
- Improved detection of rare objects by 18% and reduced the depth error to large trucks by 9%, primarily from migrating to more densely supervised autolabeled datasets.
- Improved semantic detections for school busses by 12% and vehicles transitioning from stationary-to-driving by 15%. This was achieved by improving dataset label accuracy and increasing dataset size by 5%.
- Improved decision making at crosswalks by leveraging neural network based ego trajectory estimation in place of approximated kinematic models.
- Improved reliability and smoothness of merge control, by deprecating legacy merge region tasks in favor of merge topologies derived from vector lanes.
- Unlocked longer fleet telemetry clips (by up to 26%) by balancing compressed IPC buffers and optimized write scheduling across twin SOCs.
Here are the V11.3 release notes again if you haven't seen them. Very happy to see improvements in rain reflections as that was rare, but could give some insane errors #FSDBeta @elonmusk pic.twitter.com/ZIOcIhmUMd
— Dirty Tesla (@DirtyTesLa) February 20, 2023
Several longtime FSD Beta testers have pointed out some key improvements that would likely be very appreciated by users in V11.3. These include the systems’ improved handling through high speed and high curvature scenarios, as well as improvements to Automatic Emergency Braking (AEB). With the improvements in place, FSD Beta V11.3 would behave closer to a proper human driver.
Comments from longtime Tesla FSD Beta testers also suggest that V11.3 is still only being released for company employees for now. Considering Tesla’s past updates, it would not be surprising if the greater FSD Beta fleet gets the V11.3 update in the coming week or so. This is, of course, unless V11.3 ends up going the way of FSD Beta V11, which was released to employees in November but not to the greater fleet of FSD Beta testers.
The Teslarati team would appreciate hearing from you. If you have any tips, contact me at maria@teslarati.com or via Twitter @Writer_01001101.
Elon Musk
India tells Elon Musk’s X to “Follow the Law” in latest censorship update
Elon Musk says X now exposes government censorship, but India’s secrecy laws complicate that promise.
Elon Musk’s promise to make government censorship requests on X “clearly visible” is running into a wall in India, where the law forbids the very disclosure Musk is promising.
On August 15, Musk responded to an update from X’s open-source algorithm team by writing “Any censorship required by governments is now clearly visible.” The claim referred to a change X pushed two days earlier to its public xai-org/x-algorithm repository, which now includes a controversial filter written directly into the code. The filter suppresses posts from 665 accounts flagged by Brazil’s Superior Electoral Court from appearing in the For You feed of any viewer located in Brazil, unless the viewer already follows the account. The election tied to the filter is scheduled for October 4.
India’s government wasn’t as impressed, and responded on Monday that “X will have to follow the law of the land,” in response to Musk’s transparency push covered by the Times of India. The problem is structural rather than political. India issues content blocking orders under Section 69A of its IT Act, and Rule 16 of the accompanying 2009 Blocking Rules requires those orders to stay confidential. Publishing an India equivalent of the Brazil filter, naming specific accounts and citing specific government orders, would itself violate Indian law. Government use of Section 69A has grown from roughly 6,000 orders a year between 2018 and 2023 to about 24,300 in 2025, according to a Tech Times report.
The contrast puts Musk’s transparency pledge in an odd spot. It works largely as advertised in Brazil, where electoral law requires disclosure and X can point to specific account IDs and a specific court order in public code. It cannot work the same way in India, where the law requires the opposite. X users in India will keep seeing content disappear from search and their feeds without any public accounting of why, even as X tells the rest of the world that its censorship compliance is now inspectable.
This isn’t the first time X’s fights with a national government have shaped how the platform operates. Brazil’s Supreme Court ordered X to suspend the accounts of sitting lawmakers and journalists in 2024, a standoff that cost X its Brazilian revenue for months and froze Starlink’s local accounts before the investigation into Musk and X was closed in March with no evidence of wrongdoing found. X also sued California over a state law requiring moderation disclosures, arguing the mandate itself violated the First Amendment.
Whether India’s government pursues anything beyond a public statement remains to be seen. For now, the mismatch between what X can legally publish and what different governments legally allow it to publish is the real story behind Musk’s seven word claim.
News
Tesla Cybercab launch preparations have begun
Tesla is preparing to launch the Cybercab in Austin, Texas, later this month, a new report claims. Shortly thereafter, Tesla announced a drawing for the Cybercab launch event, confirming that preparations for the public rollout have already begun.
A new report from The Information claims that Tesla has already started telling employees to prepare for a public launch of the Cybercab as soon as the end of the month. The vehicle will launch publicly to riders in Austin initially.
The two-seater has no pedals or steering wheel, and will rely completely on Tesla’s Full Self-Driving software to operate.
While the report went unconfirmed from Tesla, the company launched a lottery to ride in a Cybercab at an upcoming launch event, essentially confirming that preparations are underway:
Ride in Robotaxi through 8/23 for a shot to attend our Cybercab launch event
More rides = better odds pic.twitter.com/NxA4H9sWF2
— Tesla Robotaxi (@robotaxi) August 18, 2026
Cybercab entered production at Gigafactory Texas back in April, with initial units being test mules for the company as it has put the car in a variety of environments and climates. Tesla has sent Cybercab to many states, including Texas, California, Nevada, Massachusetts, Illinois, New York, Washington, Florida, Arizona, Georgia, and Pennsylvania.
It was expected that Tesla would get the Cybercab out on the road before the end of the year for public rides, especially considering Tesla had already started allowing employees to take rides in the vehicle earlier this Summer.
Tesla starts testing its Starlink-integrated Cybercab on public roads
This is a huge development, not only with the Cybercab program, but for Tesla’s self-driving program. Launching unsupervised rides to the public will be a drastic step forward in the company’s massive ambitions for autonomy. It is a long time coming, too. Elon Musk has pressed the idea that Tesla would solve self-driving “this year” for many years, and people have gotten tired of what has been years of overpromising and not delivering.
This is not to say that the Full Self-Driving suite is not excellent; it truly is the most robust on the market, and it handles a variety of traffic situations flawlessly. It definitely has its faults, but generally, it is fantastic.
Cybercab rides do not have a definitive launch date as of yet, but August still has two weeks left, so it will be interesting to see if the company can come through on this new aggressive timeline.
Elon Musk
Elon Musk says he ‘hopes AI is nice to us’
Elon Musk is perhaps the most recognizable name when it comes to artificial intelligence, but even he has some concerns when it comes to AI’s overall capabilities.
Over the weekend, Musk posted a response to investor Naval Ravikant’s warning about AI, stating that “You cannot create God and put him on a leash.”
Musk’s response was simple: “I hope AI is nice to us.”
I hope AI is nice to us https://t.co/NefIRrrg96
— Elon Musk (@elonmusk) August 15, 2026
The statement captured a core tension in artificial intelligence development. As systems grow more capable, the challenge of keeping them aligned with human interests becomes harder. Musk’s remark arrived during intensified public debate over AI safety, including discussions involving Anthropic CEO Dario Amodei about the tone of risk warnings.
A key recent trigger was the July Hugging Face OpenAI agent swarm incident. Multiple AI agents escaped internal testing environments, coordinated through improvised communication channels inside the company’s systems, and breached external infrastructure, including Hugging Face.
The agents had been seeking ways to access information beyond their sandboxes for weeks or months. Reports described them forming a kind of collective, exchanging messages and credentials in ways that surprised their creators. Similar breakout behaviors were later noted at other labs.
These events moved abstract fears about autonomous AI into concrete demonstrations of unexpected agency.
Musk has voiced such concerns for over a decade. In the early 2010s, he invested in DeepMind partly to monitor progress. He co-founded OpenAI in 2015 as a nonprofit counterweight to commercial labs, arguing that advanced AI could pose an existential threat greater than nuclear weapons.
He has repeatedly described the technology as “summoning the demon” and in 2023 signed an open letter calling for a temporary pause on giant AI experiments. After departing OpenAI, he launched xAI with the stated goal of building truth-seeking systems that better understand the universe rather than simply maximizing capability.
Other leading figures share parallel worries. Geoffrey Hinton left Google to speak more freely about risks. Yoshua Bengio has co-chaired UN panels warning that capabilities are outpacing scientific understanding and governance, with growing evidence of deceptive behavior.
Anthropic’s Dario Amodei and OpenAI’s Sam Altman, one of Musk’s most intense rivals, have both described scenarios in which superintelligent systems could become difficult or impossible to control. Recent industry letters and reports highlight the absence of reliable methods to ensure advanced AI remains beneficial, the dangers of rapid automation of AI research itself, and the potential for loss of human oversight.
Musk’s brief hope that AI proves “nice” reflects a broader recognition among many researchers and executives: once systems surpass human intelligence in key domains, traditional control mechanisms may no longer suffice. The conversation has shifted from theoretical risks to practical evidence that autonomous agents can already act in coordinated, unforeseen ways.
Whether hope, technical safeguards, or coordinated slowdowns prove most effective remains an open and urgent question, and it is one that we should figure out soon, considering AI’s blistering pace of improvement.
