Tesla has rolled out a new capability that lets its Full Self-Driving (Supervised) software take control of your car's steering while you're driving manually, if it detects an imminent collision that automatic emergency braking cannot prevent. The feature, part of FSD Supervised v14.3.9, represents a significant shift in how Tesla's autonomous system operates, moving from a tool drivers must actively engage to a background safety system that can intervene without permission.

What Exactly Is This New FSD Safety Feature?

The new active safety feature set in v14.3.9 allows FSD Supervised to activate automatically in two specific scenarios. First, when the system detects an imminent collision and determines that Automatic Emergency Braking (AEB) alone may not be sufficient to prevent a crash, FSD can take directional control and steer around the obstacle. Second, the system can engage if Tesla's software detects that you are heavily distracted or have accidentally disengaged FSD.

Until this release, FSD only operated when drivers explicitly turned it on. Now, a portion of the same v14 software stack that Tesla has been rolling out since April runs continuously in the background while you drive manually, ready to intervene at any moment. This represents a fundamental change in the relationship between driver and autonomous system, transforming FSD from an opt-in driving mode to an always-monitoring safety layer.

How Does This Compare to Existing Safety Systems?

Automatic collision avoidance is not new. Automatic Emergency Braking has prevented countless crashes across the automotive industry, and letting a car steer around an obstacle it cannot brake for is a logical extension of that principle. Several automakers have been building evasive-maneuver systems for years. However, Tesla's approach differs in a critical way: FSD is a Level 2 autonomous system, meaning the driver is supposed to remain in control and responsible for the vehicle. When a Level 2 system overrides the driver, questions about liability and safety become complex.

The distinction matters legally and practically. If AEB engages and brakes the car, most drivers accept that intervention. If FSD's directional control takes over the steering wheel while you are actively driving, the situation becomes more complicated. Drivers who have chosen to drive manually have made a deliberate decision to control the vehicle themselves.

What Are the Key Concerns About This Feature?

Tesla has not yet clarified whether drivers can disable this feature, nor has the company explained the specific decision-making logic that determines when steering is safer than braking. These are significant questions given FSD's track record. The v14 software has been documented swerving toward ditches without apparent reason, and Tesla's Autopilot system has a long-running history of phantom braking, where the car brakes suddenly at obstacles that do not actually exist.

A false positive that triggers braking is jarring and inconvenient. A false positive that seizes steering control is a different category of risk entirely. If the system misidentifies a threat and suddenly steers the car, it could cause the exact crashes it is designed to prevent. This concern is particularly acute because the same software stack that will now control steering has demonstrated these reliability issues in the past.

• Liability Questions: If FSD takes control and causes an accident, determining who bears legal responsibility becomes unclear, since the driver did not authorize the intervention.
• False Positive Risk: The v14 software has shown tendencies to swerve unexpectedly or brake at phantom obstacles, raising concerns about unintended steering interventions.
• Driver Autonomy: Drivers who have chosen to drive manually lose the ability to control their vehicle if the system decides intervention is necessary, without clear opt-out options.
• Trust and Transparency: Tesla has not disclosed how the system decides when steering is safer than braking, or whether the feature can be disabled by users.

How Should Drivers Approach This Feature?

For drivers considering or already using Tesla vehicles with FSD, understanding the implications of this new capability is essential. The feature represents a meaningful change in how the autonomous system interacts with manual driving, and clarity on a few key points would help drivers make informed decisions about their comfort level.

• Verify Disabling Options: Check Tesla's documentation or contact support to confirm whether the automatic steering intervention can be turned off and how to disable it if you prefer traditional manual control.
• Monitor Software Updates: Stay informed about FSD version updates and their specific features, as Tesla continues to refine the system's behavior and safety parameters.
• Understand Your Insurance: Contact your insurance provider to clarify how this feature affects your coverage and liability in the event of an accident involving FSD intervention.
• Test in Safe Environments: If you own a Tesla with this capability, consider testing how the system behaves in controlled, low-risk driving situations to build familiarity with its intervention patterns.

The broader issue underlying this feature is trust. Automatic collision avoidance in principle is sound; AEB has saved lives. But this is the same v14 software that has been observed swerving for no apparent reason and braking at phantoms. If Tesla gets the false-positive rate wrong, the feature could create more danger than it prevents. The company's track record with phantom braking and unexplained swerving suggests that caution is warranted.

Tesla announced that v14.3.9 is starting to roll out shortly, meaning the feature is becoming available to users now. As this capability spreads across Tesla's fleet, real-world data will begin to reveal whether the system's intervention rate is appropriate and whether false positives are a significant problem. Until then, drivers should remain aware that their Tesla's FSD system is now monitoring their driving and ready to take control without explicit permission.