Before You Sideload the Steering Wheel

Drivers are installing aftermarket hardware and unofficial software on ordinary cars to expand their driver-assistance capabilities. One widely circulated example showed Mike LaBarbera’s Tesla Model Y operating with Comma Four hardware and Sunnypilot, a customized fork of Comma AI’s open-source Openpilot software, after his Tesla Full Self-Driving subscription ended. Comma sells a retrofit kit for about $1,000, including sensors and cameras for compatible vehicles.

The federal response is no longer hypothetical. The National Highway Traffic Safety Administration has opened an investigation into Comma AI after five crashes involving vehicles that were running Openpilot. That fact does not establish that Openpilot caused those crashes. It does establish that the performance of aftermarket driving systems now belongs in a regulator’s case file, not only in online demonstrations and software repositories.

The appeal is easy to price. A buyer can obtain useful assistance without indefinitely renting a manufacturer’s closed system, and open software permits inspection, modification, and faster experimentation. Owners have long customized cars. Replacing a stereo, changing suspension parts, and loading code that can influence steering or speed, however, do not place the same claim on everyone sharing the lane.

The advertised purchase is hardware plus software. The actual purchase includes a maintenance job. Owners must track whether their exact vehicle, sensors, and firmware remain compatible; whether a new release fixes or creates problems; and whether the developer of a fork will still support it after the next manufacturer update. A cheap download can acquire an expensive calendar.

The critical distinction is between customization and defeated safeguards. A modification that preserves attention monitoring, clear takeover warnings, operating limits, and retrievable logs presents a different risk from one designed to suppress warnings or extend operation beyond tested conditions. Changes to lane behavior, braking commands, or driver checks deserve more scrutiny precisely because passengers and nearby drivers never agreed to join the test.

Warranty and insurance questions should be settled before installation, not after a collision or repair. An owner should ask the automaker what modifications affect warranty service and recalls, ask the insurer whether the equipment must be disclosed, and determine whether the vendor or software maintainer accepts any responsibility for a control decision. Marketing language about autonomy does not replace a named legal party.

Before buying, verify the supported hardware combination, update and rollback procedures, driver-monitoring requirements, event-log access, recall implications, insurance coverage, and emergency disengagement method. Save installation records and software versions. If nobody can explain who reads the logs, supplies a safety update, and accepts liability when the code chooses the trajectory, the missing item is not a feature. It is the warranty for the road test.