Question 1

Is codriver a Tesla app?

Accepted Answer

codriver runs in the Tesla browser — no jailbreak, no App Store, no install. Built for the 17-inch landscape screen. Tesla is currently the only carmaker that ships an in-car browser usable while driving (Android Auto added Vivaldi, but only while parked), which is why codriver lives there. Works in any Chromium browser on phone or laptop too. Independent project, not affiliated with Tesla.

Question 2

How is this different from Tesla's built-in nav?

Accepted Answer

Tesla's nav routes you. codriver adds the layer Tesla doesn't ship — live community alerts, charger intel, route notes from drivers ahead, and a calm second voice that reads the road without nagging. We're additive: keep using Tesla's nav for routing, run codriver alongside it for the road context.

Question 3

Where do the alerts come from?

Accepted Answer

Several layers you switch on in Settings. Live incidents — police, hazards, accidents, jams, construction, closures — come from live community traffic data, merged with reports from codriver drivers. Other layers pull from open public datasets you enable individually, like OpenStreetMap for speed cameras and Open Charge Map for chargers. Reports surface seconds after they're posted, dedupe across overlapping sources, and retire on dispute or inactivity so stale pins don't clutter the map.

Question 4

What about chargers and EV routing?

Accepted Answer

Every network, one map. Superchargers and Destination chargers plus the other networks — ChargePoint, Electrify America, IONITY, and the rest — on a single charger layer, powered by Open Charge Map. Smart filters know what your Tesla can actually plug into: compatibility (native connectors on by default, adapters like CCS or CHAdeMO opt-in, auto-tuned to your region), network, free vs. paid, and power (AC, DC fast, 150 kW+ ultra). Free shows the Tesla network plus one more at a time; Premium overlays as many in parallel as you like. Next: charger reliability, queue intel, and EV-aware route notes from driver reports. codriver is an EV-native product — not a general-driving overlay with a charger tab tacked on.

Question 5

How do I sign in? Do I need a password?

Accepted Answer

No passwords — sign in with a magic link sent to your email. The link expires in 15 minutes. On a Tesla, sign in on your phone first, then pair the car with a QR code (the on-screen soft-keyboard is hostile to typed email addresses). No password-reset flow to lose track of, no leaked password risk, no SSO dependency on Google or Apple.

Question 6

Is there a free tier?

Accepted Answer

Yes — and you can try it without an account at all: open the app and look around the live map, pins, closures, rain radar and aircraft included. Navigation, reporting and saved places are what need an account. Free forever once you sign up: both 2D view modes (Compass and Track), two synced favorites named Home and Work, unlimited browser-local favorites (per-car, not synced), full read + write on community alerts, and the full charger map — every network's stations, one extra network overlaid alongside Tesla's at a time. Premium adds the two 3D view modes (Tilt and Cityscape), unlimited synced favorites across every car you pair, route notes, and as many charging networks in parallel as you like. Lite-mode — the performance toggle for older MCUs — is available on every plan.

Question 7

What are the map view modes?

Accepted Answer

Four modes, named by what they show. Compass — 2D, north-up (Free + Premium). Track — 2D, follows your heading (Premium). Tilt — 3D, terrain only (Premium). Cityscape — 3D, with buildings (Premium).

Question 8

What data do you collect?

Accepted Answer

Pseudonymous by default. An email is the only required identity — burner addresses are first-class, no KYC ever. No ads, no surveillance, no upsell to a Google account. You stay in control of what you share: favorites live in your car browser's local storage by default and you can opt to sync some of them to your profile if you want them across devices; your current position and trips are never recorded on the server, and opt-in trip history may land later but will never be a requirement. Anonymous telemetry covers backend latency, UX score, GPS continuity only — the privacy gate rejects forbidden fields at ingest, not after the fact. All data lives in Helsinki, Finland (GDPR coverage, out of reach of US data acts); non-justice-system data-sharing inquiries are refused outright.