Guides
Practical guides to tracking coding time: from git history, from the terminal, and from whichever editor you actually work in. Each one covers what the method measures, where it breaks down, and what to do about the gap.
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 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.
Resume vs Proof-of-Work Profile: What Actually Gets Developers Hired in 2026
Resume vs proof-of-work profile, compared for developers in 2026. What each one is for, why a resume is a claim and a proof-of-work profile is evidence, and when you still need both.
LinkedIn vs GitHub for Developers: Which One Actually Gets You Hired in 2026?
LinkedIn vs GitHub for developers, compared for 2026. Which one recruiters actually read, what each is best for, and why neither one proves you wrote the work.
GitHub Profile vs Portfolio Site: Which Should Developers Build in 2026?
GitHub profile vs portfolio site, compared for developers in 2026. Which one actually proves your skill, what each is best for, and why neither verifies the work on its own.
Changelog
All updatesAugust 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.
July 5, 2026
Issue Attribution — Linear & Jira
Connect Linear or Jira to sync your issues and automatically tie them to the sessions and commits that shipped them. DevClocked matches issue keys from branches, commit messages, and pull requests, so delivered work links back to what it was for — read-only, with no writeback to your tracker.
June 25, 2026
Slack Integration
Install the DevClocked Slack app to bring reports into your workspace. Admins pick channels and posting rules, and each member links their own account with /devclocked connect for private personal reports and shared team digests.