How to track FSD (Supervised) interventions by version
Updated
To track FSD (Supervised) interventions by version, pick one counting rule and stick to it, and after you park, note each event with the date, the place, what the car did, whether it was safety-critical, and the FSD (Supervised) version shown under Controls > Software. Group the notes by version and by place so you can re-drive your trouble spots after an update.
The easy option is Drive Journal (published as TesBots: Drive Journal). It keeps that log for you and sends a retest list when a new version lands. See the Drive Journal page or its x.ai page. It's free to add, but you need a plan that includes Grok Bot (The X Subscription Premium or higher, or an existing SuperGrok plan).
Community trackers tell you how FSD (Supervised) does on average. A personal log tells you whether it handles your commute.
Quick answer
To log FSD (Supervised) interventions, pick one counting rule and stick with it, for example only disengagements, or disengagements plus accelerator taps and scroll-wheel inputs. For each event, note the date, the place in your own words, what the car did, whether it was safety-critical, and the FSD (Supervised) version you were on. Log it after you park. Group notes by place and version so you can retest the same spots after an update.
Five fields for each event:
Date
Place — whatever you call it
What the car did
Critical or not
FSD (Supervised) version
Pick one counting rule
A disengagement is a steering or braking takeover. An intervention is a lighter input that doesn't take over — an accelerator tap, the scroll wheel, or a turn signal. Those definitions come from teslafsdtracker.com/help.
Pick one rule and keep it. Mixing disengagements and every little tap in the same count makes the numbers meaningless. Techbloat makes the same point in its personal-log writeup.
If you want averages across other drivers, Tesla FSD Tracker filters by version and hardware — some people feed it with a MATT3R K3Y or the EVGuyCanada app. Dirt Studios pulls events out of video by version. Those are useful for the big picture. They don't tell you about the left turn on your way to work.
The five fields
For each event, write down the date, the place in your own words ("the Elm merge", "school pickup"), what happened, whether it was safety-critical, and the FSD (Supervised) version you were on.
A saved dashcam clip is optional. Clips can show other people and plates, so treat them like anything else with faces and cars in the frame.
Find your version
When you're parked, open Controls > Software. That's the version to put on the note.
Use the car's own feedback prompt too
After a takeover, the car asks why. Press reports describe the current options as Navigation, Preference, Discomfort, Critical, or a voice note through the steering-wheel mic (Not a Tesla App; Electrek, May 2026). Teslarati reported a different set in April — Preference, Comfort, Critical, Navigation — and the menu has changed more than once. This is from press reports, not Tesla docs, and it may change again.
Answer it hands-free, or once you're stopped and it's safe. Don't tap a random option just to clear the prompt.
Look for repeat spots, not averages
Group your notes by place. Keep a short retest list of 3–5 spots that keep showing up. That's the list that matters after an update — not a miles-per-event average.
Compare versions on your own spots
When a new FSD (Supervised) version lands, re-drive the list. Mark each spot fixed, same, or worse against the version you just left. You're comparing your own corners, not chasing a version number.
Let a bot keep the journal (optional)
If you'd rather talk than type, Drive Journal (published as TesBots: Drive Journal) keeps the history by FSD (Supervised) version and flags which of your trouble spots to retest when a new version lands. Log from your phone or, after you park, from the car: "Hey Grok, ask Drive Journal to log a hesitation at Elm Street." It can also take notes by email at name+drives@mail.grokbot.com; clips attach by filename, and the bot doesn't claim to analyze video. A daily 8:30 AM check (teslascope.com/software, stats.tessie.com, notateslaapp.com, and X) sends one retest message when a new version is reported for your hardware (HW3/AI3 or HW4/AI4) and country; Sundays at 7:00 PM you get a 3-line recap if you logged anything. Notes stay in your own Grok Bot account — TesBots never receives them — and the bot can't read the car or guess your location. It's free to add, but you need a plan that includes Grok Bot. Log after you park when you can.