Get help

Discord

The NAP Discord is where most day-to-day help happens. It has channels for install questions, hardware discussion, bug reports, and general pre-AP Tesla talk. If you have a question, start there.

When you ask, include:

• Car year and trim — 2012, 2013, or 2014; P85, 85, 60, 40, P100++L etc.
• comma device — comma 3, 3x, or 4
• Pedal installed? — yes or no
• Radar installed? — yes or no
• Branch and version — shown in the comma UI under Software; nap-release, nap-alpha, or other, plus the version string or commit if you can find it
• What the screen said — the exact alert text, not a paraphrase. If you can screenshot or photograph the comma display, do that.
• What you were doing when the problem happened — first install, after an update, mid-drive, etc.

The more specific you are, the faster someone can actually help. "It doesn't work" with no other context gets a slow response.

GitHub issues

Confirmed bugs with reproducible steps belong at github.com/NotAutopilot/openpilot. Use GitHub issues for things you can describe precisely — unexpected disengagements tied to a specific alert, crashes with a stack trace, wrong behavior you can reproduce with a route ID from comma connect.

If you are not sure whether what you are seeing is a bug or a setup issue, ask in Discord first. Filing vague bug reports creates noise and work for maintainers who are doing this on their own time.

A small community

NAP is maintained by a handful of people, all of whom also own and drive the cars. There is no support team. Responses take time, especially for complex issues. Being patient and providing good detail when you ask makes a real difference.

If you have figured something out that took you a while — a wiring quirk, a calibration trick, a fix for a specific issue — sharing it back in Discord or on the wiki helps the next person who hits the same wall.