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.
How to Get the Most Out of DevClocked (Complete Guide)
The full mental model behind DevClocked: coding time vs session hours vs hands-on hours, what each tracker actually records, sessions and work blocks and agent streams, reports, issue links, and invoicing. Written for a first week on the product.
Time Tracking for Engineering Teams in 2026 (Passive, Provable, Not Surveillance)
How engineering team time tracking works in 2026: why manual timers and monitoring tools fail, passive code-native capture, agent hours and token spend, and a rollout the team will accept.
How to Show Coding Activity on Your Resume (2026 Guide)
How to show coding activity on your resume without padding it: turn commits into quantified bullets, link one verifiable destination, and skip the screenshots recruiters ignore.
The Best Way to Track Freelance Developer Hours in 2026 (Passive, Provable, Billable)
The best way to track freelance developer hours is passive tracking built on your git history plus a telemetry layer, not manual timers. Here is the exact setup, step by step.
How to Track Time Spent on a Coding Project (2026 Guide)
How to track time spent on a coding project accurately: scope the project first, pull a free baseline from the repo's git history, then add passive telemetry that attributes sessions (including AI-agent work) to the right project.
How Many Hours Do Developers Actually Code? (The Real Numbers)
Studies put real hands-on coding time between 52 minutes and 6 hours a day, not 8. Here is what RescueTime, Amazon, and 2026 survey data actually found, and why the range is so wide.
How to Track How Much Time You Spend Coding (2026 Guide)
A step-by-step way to track how much time you actually spend coding, why manual guesses run short, and which layer (plugin, git, telemetry) gets you a number you can trust.
Time Tracking for Remote Developers: Output Beats Surveillance (2026)
Time tracking for remote developers in 2026: why screenshot monitoring fails, the 5 best passive trackers compared, and how to prove your output across timezones without being watched.
Coding Time Tracker for Students: The 5 Best Picks in 2026
The best coding time tracker for students in 2026: free picks compared, what each one tracks, and how to turn practice hours into proof you can show your first employer.
Vim Time Tracking: How to Track Coding Time in Vim and Neovim (2026)
How to set up Vim time tracking in 2026: the vim-wakatime plugin, DIY autocmd loggers, git-based inference, and telemetry, what each one misses in a terminal-native workflow, and how to get hours you can actually trust.
JetBrains Time Tracking: How to Track Coding Time in IntelliJ and Its IDEs (2026)
How to set up JetBrains time tracking in 2026: the built-in task timer, plugins, git-based, and telemetry options, what each one misses across IntelliJ, PyCharm, WebStorm and the rest, and how to get hours you can trust.
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.
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.