AI & Agents
What coding agents do while they run, and what that costs in tokens and wall-clock time. Written from session data, for people using Claude Code, Codex and Cursor as part of normal work.
How to Track AI Token Spend by Project (2026)
To track AI token spend by project you need per-session records carrying the model, the token counts split by pricing tier, and the repo the session ran in. Here are five ways to get that, where each one breaks, and real numbers from a 13,674 dollar month.
What Is Agentic Engineering Intelligence? (2026 Definition)
Agentic engineering intelligence is the measurement of software work done by humans and AI agents together: session time across IDEs, terminals, and coding agents, tied to commits, PRs, and token cost. Definition, the five dimensions it measures, and how it differs from developer analytics and editor time trackers.
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.
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 AI Coding Productivity in 2026 (a Framework That Holds Up)
Measure AI coding productivity by tracking leverage and shipped output, not lines or tokens. Here is the framework: what to measure, what to ignore, and why commit volume and token counts mislead in the agent era.
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.