Time Tracking
How to measure where coding time actually goes: from git history, from the terminal, from whichever editor you work in, and from the hours that end up on an invoice. Each guide covers what the method measures, where it stops measuring, and what to do about the difference.
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 Measure Coding Time Without a Timer (2026)
How to measure coding time without a timer: read your git history, add passive telemetry, and skip the stopwatch entirely. A practical guide for developers in the AI era.
Git-Based Time Tracking: What It Is and When to Use It (2026)
What git-based time tracking is, how it compares to plugin-based and manual tracking, and where it actually fits. A practical category guide for developers in the AI era.
How to Track Time Spent Coding on GitHub (2026 Guide)
GitHub does not track time, so to track time spent coding on GitHub you reconstruct sessions from commit history. Why that is only a baseline, and what makes it accurate.
Time Tracking From Git Commits: How It Works and Where It Breaks (2026)
How time tracking from git commits actually works, the three common methods and their accuracy, and why commit history is a benchmark rather than a clock in the AI era.
Developer Time Tracking for Invoicing: How to Bill Hours You Can Actually Prove (2026)
A practical guide to developer time tracking for invoicing: capture billable hours passively, reconcile them against git, and hand clients an invoice backed by an audit trail instead of a guess.
How to Estimate Developer Hours From Commits (a Practical Method for 2026)
A step-by-step method to estimate developer hours from commits: session reconstruction, gap thresholds, and calibration. Plus where git-only estimates break and how to make the number invoice-ready.
Coding Time Tracker Without an IDE Plugin: What Actually Works in 2026
Want to track coding time without an IDE plugin? Start from a git baseline with nothing to install, then add one editor-agnostic CLI tracker for accuracy. Why per-editor plugins fail, and what to use instead.
How Long Does It Take to Build an MVP? Real Timelines in the AI Era (2026)
How long it really takes to build an MVP with AI tools like Claude, Cursor, and Codex. Honest ranges by app type, a real case study, and how to prove the timeline.
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.