Yes. California allows a properly licensed driver to use Full Self-Driving (Supervised) as driving assistance while actively monitoring the road and remaining ready to take control. The important distinction is what the system requires from the person behind the wheel. A feature that can steer, brake, and follow a route under supervision falls on the driver-assistance side of California’s law. Operating a vehicle as a driverless service involves a different set of approvals.
In its February 17, 2026 release, the California Department of Motor Vehicles said Tesla had clarified that its Full Self-Driving feature requires driver supervision and had stopped using Autopilot in California marketing. The agency said the company’s corrective action avoided a 30-day dealer and manufacturer license suspension. The discussion that follows is general in scope. It explains the legal checks that apply in comparable situations and makes no independent findings about the company or any vehicle.
For a driver, the first check is the feature description and operating instructions for the vehicle in front of you. For a buyer, it is the written notice delivered with the vehicle or the upgrade. For someone reading about a driverless ride, it is the operator’s permit. Those three records answer different questions, and each matters for a different reason.
I. What can a driver legally do with supervised driving assistance in California?
A. The legal line is active human supervision
California Vehicle Code § 38750 defines autonomous technology by its capacity to drive without active physical control or monitoring by a human operator. The statute identifies vehicles with integrated Level 3, 4, or 5 technology and separately excludes comparable driver-assistance systems that cannot drive without active control or monitoring, whether the systems are considered individually or together. Lane-keeping assistance, adaptive cruise control, and park assistance are among the statute’s examples. The legal question is what the technology requires of the human, even when it performs several driving functions at once.
The National Highway Traffic Safety Administration’s driver-assistance guidance describes Level 2 as assistance that can control steering and acceleration or braking at the same time. The federal agency says that the driver remains responsible and must stay engaged and attentive. This guidance explains how to read a level designation. California’s statute supplies the state-law distinction that matters when using a vehicle on a California road. The federal description and the state definition point to the same practical check for a supervised feature: whether you are expected to watch the road continuously and intervene when necessary.
The person who drives or is in actual physical control of a vehicle falls within California Vehicle Code § 305’s definition of driver. In an ordinary trip using supervised assistance, the driver should evaluate a lane change, slowing traffic, a temporary road closure, and a pedestrian crossing with the same attention the situation would require during manual driving. An uneventful stretch of operation says little about how the next situation will develop. A steering input, a system prompt, or hands-off operation for part of a trip does not establish that the car may be operated without an attentive driver.
Consider a car that is following a route toward a freeway exit when a temporary sign sends traffic away from the expected ramp. One question is whether the feature can continue navigating under those conditions. The separate, immediate question is who must decide whether the car should follow the detour. With supervised assistance, that decision remains with the person responsible for the drive. It pays to identify the controls for canceling assistance, understand what the display says when assistance changes or stops, and make any settings changes before entering moving traffic. The system’s ability to handle a merge on a previous trip is a poor substitute for checking the road on the current one.
California’s phone rule illustrates a concrete consequence. Vehicle Code § 23123.5 restricts driving while holding and operating a handheld wireless phone or electronic communications device. A hand-operated activation or deactivation under the mounted-device provision requires both an approved mounting position and a single swipe or tap. The provision separately excludes manufacturer-installed systems embedded in the vehicle. Neither the mounted-device provision nor the exception for embedded equipment grants permission to stop supervising a driving feature. Set an address or make a lengthy itinerary change while safely parked, and treat a phone in a mount as a different device from the controls built into the vehicle.
If two drivers share a vehicle, check the feature’s operating instructions before the handoff. One person may have used an earlier software version or a different hardware configuration and may assume the screens, alerts, and controls work the same way. For a rental or a borrowed vehicle, get familiar with what the display shows when assistance engages, where the written instructions are kept, and how to resume manual driving. If the screen, the written instructions, and what the owner says leave an important point unclear, use ordinary manual driving until you resolve the discrepancy. That decision avoids making a safety judgment based on the name of the package.
B. A driverless permit covers the approved operation
California’s autonomous-vehicle regime asks a different question. Under § 38750, public-road testing and operation of an autonomous vehicle follow statutory and regulatory approval rules. The statute addresses manufacturer applications and safety certifications, including controls for engaging or disengaging the technology, alerts when it fails, and requirements relating to testing and insurance. Those provisions concern a vehicle and operation within the state’s autonomous-vehicle framework. A consumer does not enter that framework by purchasing an assistance subscription or installing a feature update.
The DMV publishes California’s autonomous-vehicle regulations and program materials, with links to information about deployment and testing permit holders. The distinction matters because testing with a safety driver, testing without a driver, and deployment serve different purposes. When a claim about authorization appears in a news report or a product video, identify the operator, the site of operation, and the kind of activity described before drawing a conclusion from it. A permit reference without those particulars tells a reader little about what can legally happen on a particular road.
On April 28, 2026, the California DMV announced adoption of updated autonomous-vehicle regulations covering light- and heavy-duty vehicles. The agency described changes to permitting, data reporting, interaction with first responders, and enforcement. Its release distinguishes immediately effective provisions from provisions that phase in. To check an operation on a particular date, use the applicable regulatory text and permit, especially where someone cites an older story about what vehicles could operate or where they could travel. The announcement describes a framework for autonomous-vehicle operators. It does not change what an ordinary driver is expected to do while using a supervised feature.
Here is a practical way to read a claim that a vehicle is authorized. Start with the legal entity that holds the authorization. Then check which permit category the authority issued, the vehicles and operation it covers, and any geographic or operating limits. If the claim is about fare-paying rides, also check the separate rules relevant to passenger service. Those details help distinguish a test vehicle from a deployed vehicle and a private-car trip from a ride provided by a commercial operator. The same brand can appear in a retail context and in an operator’s demonstration, and the governing records may address entirely different activities.
For the commercial side of that distinction, see the separate explanation of California robotaxi permits and freeway liability. The facts needed for a commercial ride include the operator and its authorized service area. For a private car with supervised assistance, the records that explain the immediate obligations are the feature instructions, the state rules for a person driving, and the circumstances in which assistance was engaged. If a dispute arises after a particular trip, record the location, vehicle, feature status, and any warning before memories of the event become mixed with general claims about automated driving.
II. What should you check before buying the feature or disputing how it was sold?
A. Read the notice for the car and software you actually receive
California Vehicle Code § 24011.5 addresses two points. Subdivision (a) requires a distinct notice naming the feature and clearly describing its functions and limits when a covered new passenger vehicle is delivered or when an update or other vehicle upgrade adds a partial driving automation feature. Subdivision (b) restricts names and marketing language that would lead a reasonable person to believe the feature allows the car to operate as an autonomous vehicle or has functionality it lacks. The statute defines partial driving automation by reference to Level 2. It also provides that compliance does not change existing duties of care or limit the civil liability of a manufacturer or dealer.
The notice requirement has a specific trigger. For an update, ask whether it adds a covered partial driving automation feature. A release that changes the appearance of a menu or improves an existing maneuver can raise a different question from an upgrade that adds a function. The statute also allocates responsibilities between the manufacturer and the dealer for supplying notice information. If a sale or upgrade is disputed, keep the notice you received, the date and manner of delivery, the sales paperwork, and any update description. It is useful to identify who provided each document before deciding whose statement or omission is actually at issue.
The California DMV described its administrative resolution in the February 17, 2026 announcement of corrective action. The agency identified proceedings Nos. 21-02188 and 21-02189 and said its underlying decision was issued on December 16, 2025. It reported that the manufacturer had previously changed the wording for the supervised feature and subsequently stopped using Autopilot in California marketing. According to the agency, those steps avoided the license suspension. That was an agency account of a marketing and licensing matter. A purchaser’s records still determine what was offered, what was delivered, and what the purchaser saw.
California also has a broader prohibition on misleading statements in the sale of goods and services. Business and Professions Code § 17500 addresses public statements made to induce a transaction that are untrue or misleading and known to be so, or that reasonable care would reveal to be so. Preserve the precise claim you relied on before purchase, including the date and where it appeared. A remark about a capability in a demonstration, a representation on the mandatory order screen, and a prediction about a future software release are different pieces of evidence. Put each in its own place in the sequence of events.
For example, a buyer might remember that a salesperson discussed a future hands-off commute, while the order form says the software is supervised. Write down what was said, who said it, when it was said, and whether the buyer saw a written description at the time. A second buyer may have seen an online statement only after paying for the feature. The screenshots, receipts, delivery notice, service records, and feature status on the vehicle will help differentiate those accounts. Someone who buys a used vehicle can additionally check whether the seller was promising a feature already present on that car, an account entitlement, or the ability to purchase an upgrade later. Preserve the seller’s actual wording before making assumptions about transfer.
Look at the vehicle and the transaction separately. A settings page can help identify what is enabled at the time of inspection. An invoice can identify the package paid for. Neither document alone establishes what the buyer was told months earlier. Conversely, a dated description of a package can explain the sales representation without establishing what the car did at a specific intersection. The less those records are mixed together, the easier it is to frame the actual question: a missing entitlement, a disputed sales claim, a feature behaving differently from its operating instructions, or a road incident while assistance was on.
B. The court record can tell you which issue was decided
In LoSavio v. Tesla, Inc., No. 25-7927, the United States Court of Appeals for the Ninth Circuit on October 16, 2026 vacated three class certifications and remanded. The court concluded that exposure to the challenged hardware statement could not be inferred across the classes from the availability of an optional webpage, and that individualized exposure questions undermined the certification analysis. The memorandum is unpublished and identifies the limits on its precedential use. For a buyer, the practical distinction is between a page that anyone could visit and evidence of the statement that actually appeared before payment. The disposition addressed whether claims could proceed together in those classes and left the merits for further proceedings.
In Waller v. Tesla, Inc., No. 26-cv-05350-RFL, the United States District Court for the Northern District of California on June 30, 2026 denied without prejudice a motion to stay a separate putative class action. The district judge reasoned that the two cases were before the same judge and that a pause would not then make the newer case more efficient. When checking whether a buyer is included in a lawsuit, start with the docket and the latest class order for that lawsuit rather than a report that a related case was allowed to proceed. The June order concerned case management at that stage. It did not determine who belonged in a class, decide whether anyone was entitled to a recovery, or resolve a question about driving without supervision.
In Lamontagne v. Tesla, Inc., No. 23-cv-00869-AMO, the United States District Court for the Northern District of California on September 30, 2024 dismissed a federal securities complaint with leave to amend after finding the allegations insufficient under the investor-claim pleading standards. A buyer checking what was promised with a vehicle should distinguish investor statements and federal securities pleadings from the purchase documents and California provisions governing that sale. The district court evaluated a complaint about securities. Its ruling did not decide whether a particular buyer received the required notice or whether a particular trip complied with California traffic law.
Read the operative part of an order before treating a headline about a lawsuit as an answer. A certification dispute asks whether specified claims can be litigated together. A stay asks whether proceedings should pause. A dismissal with leave to amend resolves the sufficiency of the pleading then before the court and gives the plaintiffs an opportunity to amend. Those are distinct procedural moments. In a purchase dispute, inspect the receipt and feature notice. In a driving dispute, reconstruct how the vehicle was being operated. In a question about a court case, identify the order and the issue the judge actually decided.
For a driving incident, preserve neutral facts first. Record the vehicle identification information, the displayed software version, the road, weather and lane markings, any alert the system displayed, and when manual control was resumed. Keep the original files if you have lawful access to dashcam footage or other records. If assistance was reportedly active, distinguish what a recorded display or available log shows from what a driver later recalls. A later software release or a different car’s performance cannot establish the mode that was active at the time. Be equally careful with clips cut to show only the seconds before or after a maneuver. The missing sequence may matter to an accurate account.
Federal reporting records can supplement an account of a driving incident. The National Highway Traffic Safety Administration’s standing general order page describes federal reporting requirements for covered entities involving certain crashes when an automated driving system or Level 2 assistance is in use. These reports serve a safety oversight purpose. The agency’s published data have limits, including incomplete or changing information, and raw counts are a poor way to compare vehicles whose trips take place under different conditions. If you find a report that appears to match a specific event, check the date and location, the system identified in the report, and whether the available fields distinguish an initial report from an update.
In WP Company LLC v. National Highway Traffic Safety Administration, No. 24-cv-1353, the United States District Court for the District of Columbia on March 25, 2026 granted in part and denied in part the defense summary judgment motions and denied the newspaper’s cross-motion without prejudice. The dispute concerned access to particular fields in crash reports under federal freedom-of-information law. The court sustained certain withholdings and permitted the defense to supplement its showing on other fields. A driver checking a specific collision should treat a missing detail in a public crash spreadsheet as a prompt to look for incident records, rather than as proof about what the system did. The ruling resolved disclosure questions and left accident causation outside the decision.
If you are comparing two records of a trip, look for timestamps and identify what each record actually measures. The time shown in an exported clip may differ from the time displayed in a trip summary. A dashboard icon visible before a maneuver can help identify the mode at that moment. Whether the mode remained active afterward depends on the next part of the record. A report from the other vehicle or a witness can supply context for the maneuver itself. If the records leave a gap, identify the gap rather than reconstructing the missing move from a product demonstration or a generalized account of what automated cars do.
For a sales dispute, build a timeline from first exposure to the product description, through the order and the handover, to any changes made later. Save the terms and the communication attached to the original transaction even if a current website uses different wording. Identify the specific benefit the buyer thought was included and the document that conveyed it. If the dispute concerns an upgrade, determine what was available before and after the upgrade and whether the vehicle displayed any different limits. These checks can clarify whether the disagreement is about the state of the feature, its description, or a separate decision about driving. They also keep a public agency decision from being mistaken for a ruling on an individual transaction.
Conclusion
California permits supervised driving assistance while the driver remains attentive and ready to take control. Driverless deployment calls for a separate authorization that applies to the operation it covers. Before a trip, check the feature instructions for the vehicle and plan to supervise it for the whole drive. Before a purchase or upgrade, keep the notice that describes what the feature can do. If a dispute follows, use the evidence for that specific trip or sale and read any court order for the issue it actually resolved.