Tracking inactive time

Timekeeper monitors system-wide input while an activity is open, including activities started directly in Workweek. Mylyn is not required. Input in another application counts as activity; switching away from Eclipse does not by itself make the computer idle.

Configure Preferences > Timekeeper:

Setting	Default
Number of minutes before user is considered idle	5 minutes
Number of minutes before user is considered away	30 minutes
Automatically stop tracking when away	Enabled

When you return after the idle threshold but before the away threshold, Disregard idle time? asks whether to exclude the absence. Yes closes the old interval at the last detected active time and starts a new interval now. No keeps the elapsed idle time in the existing interval.

When you return after the away threshold, the absence is excluded automatically. With Automatically stop tracking when away enabled, tracking stops and the optional linked Mylyn task is deactivated. With that preference disabled, Timekeeper closes the old interval at the last active time and starts a new one on return. The correction is handled when activity resumes.

Idle detection has native checks on macOS, Windows and Linux/X11. A pure Wayland session is unsupported; XWayland needs a usable DISPLAY and XScreenSaver. See platform acceptance for tested architectures and runtime limits. Where idle detection is unavailable, start/stop and correct intervals manually in Workweek.

Open intervals remain open across restart. Use Workweek to inspect and stop or edit them; startup does not infer their end from the current provider state.