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.

