WakaTime

WakaTime uses plugins for various development tools and dedicated desktop apps for Mac, Windows, and Linux to track coding time. These plugins run in the background, recording activity based on file edits and time spent actively working in the editor. The data is securely sent to WakaTime's servers and displayed in your personal and team dashboards.

WakaTime's open-source plugins only track when you're typing in your editor. If you stop typing longer than your keystroke timeout preference, the plugin stops tracking your stats. Reading or scrolling through code may trigger heartbeats if your cursor moves or the focused file changes, depending on the editor.

WakaTime is accurate to 1 microsecond (0.000001 seconds), but the plugins depend on your computer's clock and operating system. On Windows, precision is only ±16 milliseconds (0.016 seconds). Heartbeats are sent from your editor when the file changes, when you save a file, and every 2 minutes of typing in the same file.

WakaTime plugins send heartbeat events containing data such as file paths, project names, branch names, editor names, languages, libraries used, line counts, cursor position, and timestamps. File contents are never sent, only file paths. You can configure privacy settings to hide or obfuscate sensitive information.

Yes, you can configure WakaTime to hide or obfuscate sensitive files and folders. Options include hiding project folders, obfuscating file names, excluding certain folders, and using regex patterns to control what data is sent to WakaTime's servers.

If you're offline, your coding activity is saved in a local database (boltdb) at $HOME/.wakatime/offline_heartbeats.bdb. The next time you're online, your activity will be synchronized to your WakaTime dashboard. This feature is supported by all editor plugins using the wakatime-cli.

The daily average is calculated as the total hours coded divided by the number of days you coded at least one minute in the last seven days. For example, if you coded 2 hours on Monday and 4 hours on Tuesday, your daily average would be (2 + 4) / 2 = 3 hours.

Your public profile uses a default 15-minute timeout and a time range of the last 7 days from yesterday. It also subtracts time categorized as 'Other' language. Your personal dashboard uses your custom timeout preference and a time range from today. Leaderboards and public profiles update less frequently and may lag behind your dashboard.