How can we help?
Search for the articles here or browse the categories below.
Browse by topic
Find guides, tutorials, and answers organised by category.
There are no articles here
Popular articles
What other people are reading right now.
My Tesla's navigation destination isn't showing up in codriver
codriver can pick up a destination you already set in your Tesla's own navigation, but two things have to be true first: your Tesla account needs to be connected to codriver (not just your car paired), and your car needs to be moving, not parked, when codriver checks. Steps 1. Connect your Tesla account. Pairing your car with codriver is a separate step from linking your Tesla account. In your codriver account settings, look for Connect Tesla account and turn it on. This is what lets codriver read the destination your Tesla nav already has — pairing alone doesn't do it. 2. Set your destination in the car's native navigation, as normal. 3. Open codriver in the car's browser (app.codriver.io, not the codriver.io website — the car redirects there automatically). 4. Start driving. If codriver opens while the car is still in Park, it won't see a destination yet, even if one is set. Once you're moving, reload the page to pick it up. Why codriver reads your active destination from Tesla directly. Tesla itself only reports an active destination once the car is actually driving — not while it's parked, even if you set the destination minutes earlier. You can see the same thing in Tesla's own phone app: a destination set while parked won't show under "Location" until the car moves. codriver also only checks once, right when it opens — not continuously. So the common sequence of "set destination, then open codriver while still parked" will come up empty. Reloading the page once you're moving forces a fresh check. Edge cases - No error appears if this fails. Whether it's because your Tesla account isn't connected or because the car was still parked, codriver just doesn't pick up a destination — it won't tell you why. - This only works in the car's own browser. codriver detects whether it's running in a real Tesla in-car browser; opening app.codriver.io on your phone or a laptop won't trigger this. - Reload, don't wait. codriver won't automatically retry once you start driving — you need to reload the page yourself after you're moving.
How to report a bug, or suggest an improvement
Tap the speech-bubble button on the right-hand side of the map, under the zoom controls. You can speak instead of typing, and everything needed to investigate is attached for you. You do not need an account. Reports work whether you are signed in or just looking around. Speak it 1. Tap the speech-bubble button on the map. You can also open it from Settings → Feedback. 2. Tap the microphone and say what happened. You have 15 seconds — a sentence is enough. 3. Tap Send. Recording stops on its own at fifteen seconds, and the countdown shows how long is left. You can play it back before sending, or tap the microphone again to re-record. You do not have to type anything. A recording on its own is a complete report. If you do not see a microphone, your car's browser cannot record — type instead, which works everywhere. Or type it The text box is always there. One or two sentences beat a paragraph: what you did, what you expected, what happened instead. Pick the closest label — Bug, Map is wrong, Idea, or Something else. It only helps us sort; nothing depends on getting it right. What gets attached, and what you can turn off So you do not have to describe your setup, a report carries: - A picture of the map as you see it at that moment. Turn it off with the Screenshot checkbox. - Where you are, rounded to about a kilometre by default. Enough to tell which region and which map data you are on, not enough to place your driveway. Switch it to Exact if the problem is about a specific spot, or None if you would rather not send it. - Your car and your settings — the model and screen your car reports, your view mode, units, and the other options you have chosen. - What you did just before — the last handful of things you changed in the app, and any errors it recorded. That last one is usually what makes a report fixable rather than just true. You can see all of it before it sends. Open "Everything we would send, exactly as it would be sent" at the bottom of the dialog. That is the actual data, not a summary of it. Nothing else is collected, and nothing is sent until you tap Send. What happens next Reports go to a person. Voice reports are transcribed first, so what you said arrives as text. We cannot reply to an in-app report. There is nowhere to put your email in the dialog yet, so it is one-way. If you want an answer, email support@codriver.io instead — same people, and you will get a reply. Good things to report: something that behaved differently than you expected, a pin in the wrong place, a road drawn wrongly, a feature you wanted and could not find. Rough is fine. "The police pin stayed on screen after I passed it" is a genuinely useful report.