mrkeyoor.com_
Tue 01 Sept 17:41 UTC
Automationevaluationupdated 27 Aug 2026

openpilot review

openpilot is an open-source driver-assistance system that adds adaptive cruise control and lane centering to supported cars through comma hardware. It solves the gap between basic factory assistance and a frequently updated Level 2 system, while keeping the driver responsible for the vehicle.

+27 / 5dstars / 7d
Verdict

Our openpilot install took 42 seconds and its build passed in 14 seconds, but the sandbox could not test the 335-car hardware matrix. Use it when your exact vehicle is supported, you accept Level 2 responsibility, and comma hardware is a reasonable purchase. Walk away if you want hands-off driving, factory support, or a casual weekend software project.

We ran it

Lab card: what happened when we ran openpilotScreenshot of openpilot (comma.ai/openpilot)
Install✓ · 42s64 packages · 369 MB
Build✓ · 14s
Testsn/ano test script
Known vulns0(pip-audit)
Repo3492 files~758,556 lines of source · 59.7 MB · 9 CI workflows

Answers from our run

Does openpilot build from source?

Dependencies installed in 42 seconds (64 packages), and the build succeeded in 14 seconds. We cloned commit 4a13639 into a clean Debian container with 3 CPUs and no project-specific setup.

Does openpilot have tests you can run?

Not through a standard command: the project exposes no test script or target that our harness could run.

Does openpilot have known vulnerabilities in its dependencies?

pip-audit found none in the dependency tree at the time of our run.

Who should not use openpilot?

Drivers seeking an autonomous car: the safety document defines openpilot as Level 2 assistance and requires constant attention.

What are the alternatives to openpilot?

sunnypilot, FrogPilot, Factory driver assistance. Our openpilot install took 42 seconds and its build passed in 14 seconds, but the sandbox could not test the 335-car hardware matrix.

Setup2/5Source built quickly; road use needs exact car hardware
Docs5/5Cars, safety, branches, data, and contribution rules are explicit
Community5/563,515 stars and a push on August 27, 2026
Maturity4/5Large test program, but the project still calls itself alpha

Discussed on

  1. hnAutopilot: an open source driving agent344 points
  2. hnOpenpilot – open-source self-driving agent262 points
  3. hnOpenpilot – Operating system for robotics241 points
  4. hnWe Tested Comma AI's OpenPilot195 points
  5. hnOpenPilot isn't Open40 points

Who it’s for

Drivers whose exact car, model year, and trim appear in the supported-car table.
Developers studying production robotics, vehicle interfaces, driver monitoring, or safety controls.
Contributors willing to work within a safety-first review process and prove behavior with tests or plots.
Owners prepared to buy a comma device and the correct vehicle harness.

Who it’s NOT for

Drivers seeking an autonomous car: the safety document defines openpilot as Level 2 assistance and requires constant attention.
Owners whose exact model year or trim is absent from the supported-car table: the README says other hardware is not plug-and-play.
People unwilling to install dedicated hardware in a road vehicle: normal use requires a comma four and a matching car harness.
Privacy-sensitive drivers who will not review the data settings: road camera, CAN, GPS, motion, thermal, crash, and operating-system data upload by default.
Contributors mainly proposing large features or UI redesigns: the contribution guide says most feature pull requests and UI design changes will be closed.

Setup reality

Our sandbox installed openpilot in 42 seconds, adding 64 packages and using 369 MB on disk. The build succeeded in 14 seconds. The checkout contained 3,492 files, about 758,556 source lines, and 9 CI workflows; no test script or target was available, so we skipped tests. Pip-audit found 0 known vulnerabilities.

Road use is a separate setup. The README requires a comma four, a supported car, the correct harness, and the release installer URL. A comma account is tied to connected services and uploaded driving data, although collection can be disabled.

Development outside comma hardware is possible, but the README says it is not plug-and-play. Vehicle behavior depends on the exact make, model year, trim, stock assistance package, and listed speed limits. This is also alpha research software with an explicit instruction to follow local laws.

It is Level 2 assistance for 335 listed cars

openpilot controls adaptive cruise and lane centering on compatible vehicles. The current car table contains 335 entries, and compatibility goes deeper than a badge on the trunk. Model year, trim, factory assistance package, minimum steering speed, and required connector can all change the result. A prospective buyer should treat that table as a parts list and capability contract. The README's broader claim of 300-plus cars is useful shorthand, while the generated table is the document to check before spending money.

The safety document is equally direct about the boundary. openpilot is a Level 2 driver-assistance system, and the driver must remain alert and ready to retake control. Driver monitoring can warn about distraction, but comma says attention alone does not make every situation safe. Brake input and the cancel button must always return control, and actuator limits are designed to give the driver time to react. Anyone shopping for autonomy will be disappointed because this project does not claim it.

The normal install starts with a comma four and a harness

Using the release in a car requires 4 items named in the README: a comma four, the release installer URL, a supported vehicle, and the matching harness. The device setup accepts openpilot.comma.ai, while staging and nightly branches have separate URLs. Nightly is explicitly described as unstable. That separation is sensible for a system connected to steering and acceleration, and it gives ordinary owners a clear default.

Running on other hardware is possible, though comma says the route is not plug-and-play. The source tree is a poor proxy for the whole installation because a Debian build cannot confirm a connector, CAN behavior, camera placement, or a specific trim's factory package. Even cars sharing a model name may have different low-speed limits or stock control behavior in the 335-row table. Check the exact row, including its footnotes, before assuming a forum report applies to your car.

What happened when we ran it

Our sandbox installed commit 4a13639 in 42 seconds. It added 64 packages and occupied 369 MB on disk. The build succeeded in another 14 seconds. Pip-audit reported 0 known vulnerabilities in the installed Python environment. These are clean source-preparation results for a repository with 3,492 files, roughly 758,556 source lines, and a 59.7 MB checkout.

We did not run tests because the harness found no test script or target. That is narrower than saying openpilot has no tests. The repository contains 9 CI workflow files, and the README describes software-in-the-loop checks on every commit, hardware-in-the-loop work, and a closet of 10 comma devices replaying routes. Our fresh unprivileged container could verify the build, while it could not reproduce the project's vehicle and device test systems.

The absence of a Dockerfile also matters for contributors who expect one-command isolation. Development instructions point to project tools, documentation, Discord, and the repository's own environment setup. The 14-second build result shows that our prepared image had what this commit needed; it does not establish that a random laptop can run the road stack or simulate a supported vehicle.

Data collection is on until the driver changes it

The README says openpilot uploads driving data by default. Logged sources include the road-facing cameras, CAN, GPS, IMU, magnetometer, thermal sensors, crashes, and operating-system logs. Driver-camera and microphone logging require an explicit opt-in. Owners can disable collection, so this is a configuration decision rather than an unavoidable service condition. It still deserves attention before the first drive, particularly when a vehicle is shared by a family or an employer.

The associated account gives access to driving data through comma connect. The stated terms grant comma broad rights to data generated through the software and related services. A buyer who is comfortable with telemetry for model improvement may accept that exchange. A fleet with internal privacy rules should review the settings and policy before installation instead of discovering the default after routes have uploaded.

Upstream favors small fixes over new features

The contribution guide ranks safety, stability, quality, and features in that order. It says pull requests above 500 lines should be split, UI design lacks a suitable review process, and most new feature submissions will be closed because upstream considers the product largely feature-complete. Contributors are expected to provide verification, including benchmarks for optimization work and plots for tuning changes. That is unusually candid guidance and saves developers from pitching work the maintainers do not want.

Forks are the documented outlet for different behavior. The safety rules warn them against weakening driver monitoring or excessive-actuation checks. Changes to safety code also carry trademark and test obligations. sunnypilot and FrogPilot are real options for owners who want more customization, but choosing a fork means evaluating its release discipline and safety changes separately. Upstream's conservative stance is a feature for drivers who value a narrower review policy.

Current maintenance does not turn research software into a product

GitHub recorded a push on August 27, 2026, with 63,515 stars and 133 combined issues and pull requests. Release v0.11.1 arrived on June 5, 2026 and included a new driver-monitoring model, camera-processing changes, thermal-policy work for comma four, and added vehicle support. Those dated signals show active engineering and user interest; the combined count is not a count of defects.

The legal warning remains blunt: the README calls openpilot alpha-quality research software, disclaims a product warranty, and places compliance with local law on the user. That language fits the practical verdict. The quick 42-second install makes the code easy to inspect, but a road decision depends on hardware fit, driver behavior, privacy settings, and local rules. For the right supported car and an attentive owner, openpilot is the open option worth evaluating first.

Alternatives

ProjectWhat it isPick it when
sunnypilotAn openpilot fork with more user-facing choices and modified assistance behavior.pick this instead when you want extra controls that upstream openpilot deliberately declines to merge.
FrogPilotA customizable community fork built around openpilot-compatible hardware and cars.pick this instead when customization matters more than staying on comma's conservative release path.
Factory driver assistanceThe adaptive cruise and lane-centering system delivered and supported by the car maker.pick this instead when warranty support and zero added cabin hardware matter more than open software.

What people are saying

  1. [velocity-scout] commaai/openpilot

Sources

  1. openpilot README
  2. openpilot supported cars
  3. openpilot safety
  4. openpilot contribution guide
  5. openpilot v0.11.1 release

More automation reviews

rclone · lego · OpenCLI · web-access · Karabiner-Elements · WiiUDownloader · the whole board →