VS Code time tracking extension

• File, project, branch, language and editor metadata
• Save, debug and build activity
• Keystroke and character counts
• Optional AI attribution fields

• VS Code 1.90 or newer
• wakaclock-cli on PATH, or an absolute path in wakaclock.cliPath
• An API key, stored through Wakaclock: Set API Key rather than in settings.json

Extensions: install "AtoAxis — Developer Time Tracking"
Command Palette: Wakaclock: Set API Key
Command Palette: Wakaclock: Configure CLI Path   # only if the binary is not on PATH

The key goes into VS Code secret storage, not settings.json, so it is never synced or committed with the rest of your editor configuration.

• Typing updates an in-memory buffer for the file you are in
• Saving flushes that buffer immediately and marks the heartbeat as a write
• Switching files flushes the file you left, so its seconds are not attributed to the next one
• A timer re-checks buffers on a fixed interval without bypassing the same-file heartbeat cadence
• One global activity timeline is kept, so moving between files cannot count the same seconds twice

{
  "wakaclock.cliPath": "/usr/local/bin/wakaclock-cli",
  "wakaclock.statusBarEnabled": true,
  "wakaclock.trackDebugSessions": true,
  "wakaclock.trackBuildTasks": true
}

• wakaclock.cliPath: absolute path to the binary; empty resolves it from PATH
• wakaclock.statusBarEnabled: show today’s total in the status bar
• wakaclock.trackDebugSessions: emit debugging heartbeats when a debug session starts and stops
• wakaclock.trackBuildTasks: emit building heartbeats when a task starts and stops
• wakaclock.debugLogging: verbose logging in the extension host console

• File activity only, with no app, domain or url heartbeats
• AI hooks cover Claude Code, Codex CLI and Gemini CLI; Cursor and Copilot need provider-specific adapters
• The extension requires wakaclock-cli and does not talk to the server directly