The agent distinguishes active time (input or foreground work) from idle time (no interaction). Sessions flush when a machine locks or goes idle.
Reading idle time
- Idle is not "not working" — meetings off the tracked device, phone calls, reading on paper and legitimate breaks all read as idle.
- What matters is the pattern over time, not a single day's percentage.
- A sudden rise in idle across a whole team more often means a device stopped reporting than a change in behaviour — check data quality.