Branches and updates
How NAP branches work, which one to run, and how software updates arrive on your comma device.
Updated June 11, 2026
NAP ships through the same update path as any openpilot fork: the comma device polls for new code on its configured branch and downloads updates over Wi-Fi. You pick the branch when you install NAP by entering the full URL. If you want to change branches later, go to Settings → Software → Custom Fork on the device and update the URL.
The branches
| Branch | Install URL | What it is |
|---|---|---|
nap-release | https://installer.comma.ai/NotAutopilot/nap-release | Production builds. Daily-driver quality. The only branch you should run. |
nap-alpha | — | Tester builds. Don't install this unless you've agreed to test something specific with the team on Discord. |
nap-dev | — | Active development. Never run this. The maintainer breaks it routinely, sometimes badly enough to need a reflash. |
nap-staging | — | Pre-release testing. Coming soon. |
The installer URL the NAP README links to — and the one you should give any new installer — points to nap-release. If you installed from that URL, you're already on the production branch.
How updates arrive
The comma device checks for updates automatically whenever it's connected to Wi-Fi. When a new build is available on your branch it downloads in the background. The update is applied on the next reboot. You'll see a prompt on screen when an update is ready.
You don't need to do anything for routine updates on nap-release. Connect the device to Wi-Fi after driving, let it sit, and updates install themselves. If you want to trigger a check immediately, go to Settings → Software → Check for Updates.
There is no separate "flash" step for NAP code — the standard openpilot OTA mechanism handles everything. The one exception is EPAS firmware, which is a separate operation managed from the NAP settings panel (see NAP settings).
Why you should stay on nap-release
nap-alpha tracks whatever is being actively tested. That means it may include incomplete features, changed calibration defaults, or engagement behavior that's under review. In a car like this — no electronic brakes, regen-only deceleration — running unvalidated longitudinal code has real consequences. The tester builds exist so a small, coordinated group of owners can find problems before they reach everyone else. Don't put yourself in that group by accident.
nap-dev is worse: it's the branch where development actually happens, and it is broken often — sometimes in ways that leave a device stuck until it's reflashed. There is no reason for anyone who isn't writing NAP code to ever install it.
Stay on nap-release. If you want to help test, ask on Discord first.
Switching branches
To move from nap-alpha back to nap-release:
- Go to Settings → Software on the device.
- Tap Custom Fork (or Custom Software).
- Delete the current URL and enter:
https://installer.comma.ai/NotAutopilot/nap-release - Confirm. The device will fetch the release branch and reboot.
Your NAP settings (pedal calibration, radar config, follow distance) are stored in the openpilot Params system and survive a branch switch.
Checking which version is running
Settings → Software shows the current branch and commit hash. The commit hash is what to include when reporting a bug on Discord — "latest release" is too vague when a fix may have gone out yesterday.