TL;DR
Use Auto Track when you want Drivurs to handle the run lifecycle for you.
Use manual mode when you need broader session control and you do not want the app to finish the run automatically.
They are not duplicate buttons. They support different workflows.
Auto Track
Auto Track is the better default for most users.
It is designed for sessions where you want:
- automatic readiness and arming behavior,
- clear run boundaries,
- and less manual intervention while driving.
This is usually the cleaner experience when the goal is trustworthy session capture with minimal friction.
Manual sessions
Manual mode is useful when you want broader control over the recording window.
That matters when the session should continue until you explicitly stop it rather than finishing at the standard boundary.
Manual mode is not “advanced because it feels cooler.” It is for a different operational need.
How to choose
Use Auto Track when:
- you want the app to handle the run lifecycle,
- you care about clean boundaries,
- and you are optimizing for repeatable session capture.
Use manual mode when:
- you need the recording window to stay open until you stop it,
- or you are intentionally capturing a broader slice of activity.
Common mistakes
- Using manual mode when Auto Track would produce cleaner data
- Treating Auto Track as “less serious” because it automates more
- Comparing runs without realizing they were captured under different session assumptions
Why the distinction matters in the UI
The product should make it obvious that:
- session mode changes the workflow,
- the run viewer reads the result of that workflow,
- and the leaderboard layer only makes sense if the underlying session truth is clear.