Abhijat.
← Back to work
developer tools · vs code extension

Coding Session Tracker

A VS Code extension for understanding real coding behavior through session activity, debugging, file activity, and active coding time.

  • TypeScript
  • VS Code API
36 views · updated September 15, 2026
Coding Session Tracker

the problem

Time-tracking tools built outside the editor miss what actually happens during a coding session — how much time goes to active coding versus debugging, and which files actually get touched.

what I did

  1. Built a VS Code extension using the VS Code Extension API and TypeScript to observe editor activity directly.
  2. Tracked active coding time, debugging sessions, and file-level activity as they happen inside the editor.
  3. Surfaced session data back to the developer to give visibility into real coding behavior rather than self-reported estimates.

decisions that mattered

Architecture

Runs as a VS Code extension, hooking directly into editor and debug session events via the VS Code API.

Data model

Distinguishes active coding time, debugging time, and file activity instead of a single undifferentiated 'time tracked' number.

what I learned

Self-reported time tracking and editor-observed time tracking rarely agree — the gap itself turned out to be the most useful signal.