Resources
Guides, comparisons and engineering notes on measuring developer time, human and agent. Everything here is written from how the measurement actually works, not from how it is marketed.
Cursor Time Tracking: How to Track Your Coding Time in Cursor (2026)
How to set up Cursor time tracking in 2026: the plugin, git-based, and telemetry options, why Cursor's agent counts as your time, and how to get hours you can actually trust and prove.
VS Code Time Tracking: How to Track Coding Time in VS Code (2026)
How to set up VS Code time tracking in 2026: the plugin, git-based, and telemetry options, what each one misses, and how to get hours you can actually trust and prove.
The Developer Dashboard: What to Put On One (and What to Ignore) in 2026
What a developer dashboard should actually show in 2026: the metrics worth a panel, the vanity numbers to cut, why AI broke the old charts, and how to build one you can stand behind.
Coding Stats: Which Ones Actually Mean Something (2026)
A builder's guide to coding stats in 2026: the numbers worth tracking, the vanity metrics to ignore, why AI broke the classic dashboards, and how to turn stats into proof you can stand behind.
Developer Time Tracking: The Complete Guide for 2026
A practical developer time tracking guide: the four ways to track coding time, why AI broke commit-volume as a proxy, and how to get hours you can actually trust and prove.
How to Track Cursor Usage (Time, AI Diffs, and Shipped Work) in 2026
Track Cursor usage three ways: editor time, AI-generated diff share, and shipped output. Because Cursor is a VS Code fork, editor plugins can see it, but they cannot tell your work from the agent's. Here is how to get a number you can defend.
How to Track Claude Code Usage (Time, Tokens, and Shipped Work) in 2026
Track Claude Code usage three ways: token and cost logs, session time, and shipped output. Here is what each method sees, what it misses, and how to get a number you can actually defend.
AI vs Human Code Attribution: How to Split Credit Accurately (2026)
AI vs human code attribution is not something you can read off a finished diff. Here is how attribution actually works: track authorship at the moment of writing, separate agent output from human decisions, and keep an audited record instead of guessing after the fact.
How to Measure the ROI of AI Coding Assistants (2026)
Measure the ROI of AI coding assistants by comparing what you spend (subscriptions, tokens, review time) against what actually shipped, not lines generated or suggestions accepted. Here is the framework, the numbers that mislead, and how to prove the payback.
How to Track the Percentage of AI-Generated Code in Your Project (2026)
Track AI-generated code percentage by measuring diffs at the commit level, not by eyeballing a codebase. Here is what actually counts as AI-generated, the methods that work, and why the number alone still cannot prove authorship.
How to Turn Your GitHub Activity Into a Developer Resume (2026)
Your GitHub already contains better resume material than anything you could write from memory. How to build a developer resume from GitHub activity: mine your commit history for real bullets, quantify without lying, and link one verifiable destination.
How to Show Your Coding Activity to Recruiters (2026)
Recruiters spend seconds on your profile and cannot tell curated activity from gamed activity. How to show coding activity to recruiters in a way they can actually verify: curated repos, visible recency, and an audited record of what you shipped.
Changelog
All updatesAugust 26, 2026
The DevClocked Agent
Ask questions about your own data in plain language at /agent. It reads through 15 tools covering summaries, projects, time breakdowns, sessions, commits, clients, invoices, unbilled time, timesheet items, invoicing coverage, and workspace rollups. Eight more tools can propose actions, but nothing runs until you accept its confirm card. Ask it to close out the month and it walks the invoicing recipe one step per turn, from coverage check to invoice draft. Available on Pro.
August 23, 2026
Gemini CLI Agent Tracking
The Mac app now reads Gemini CLI sessions, so those agent turns land beside your Claude Code and Codex work instead of disappearing into plain terminal time. The daemon parses your local session files for the model, input, output and cached tokens, tool calls, and subagent nesting, then attributes each session to the right project. Message content never leaves your machine; only counts and metadata are sent. Requires Mac app v1.4.49 or later. Gemini models are not priced yet, so you will see token counts rather than cost.
August 13, 2026
Export Reports as PDF
Every report — Overview, Commits, and Issues — now has an Export PDF button that produces a clean, print-optimized document honouring your active filters and date range, ready to attach to an invoice or share with a client. Exports are generated locally in your browser; no data leaves your machine.
August 13, 2026
Figma Design Tracking
The Mac app now tracks time in the Figma desktop app as real design hours — automatically, with nothing to configure. Turn on optional file-name tracking to attribute design time to individual Figma files and auto-map it to projects by naming files "Project — File". Off by default, reading window titles of design apps only, behind an explicit macOS Accessibility grant you approve yourself.