Connect your repos
Install the VS Code or Cursor extension. DevClocked finds your active repos automatically.
GitHub & Git analytics
Go beyond commit counts
Commit counts lie. See the real story: session duration, focus time, context switches, and contribution patterns across every repo.
The problem
GitHub's contribution graph rewards frequency, not depth.
A 10-minute typo fix and an 8-hour architecture rewrite both show as one green square. Engineering managers draw wrong conclusions. Freelancers can't prove their actual effort to clients. Your git log tells you what changed, not how long it took or how deep the work was.
How it works
Three steps. Zero configuration.
Step 1
Step 2
Code normally
No timers, no buttons. DevClocked tracks duration, idle gaps, and active coding time on its own.
Step 3
See real impact
Hours per repo, focus windows, and language breakdown. The insight a contribution graph can’t show.
Deep filtering
Filter by project, repo, or branch.
Don't get lost in the noise. Drill into specific projects, repositories, or individual branches. View sessions by day or dive into hour-by-hour velocity. See exactly where the complexity lives.
Project: devclocked-mobile
Repo: devclocked-api
Branch: feat/theme-sync
SESSION_METRICS
Lines Changed
12,824
vs 450 avg
Active Hours
4.2h
92% Focus
Sessions This Week
14
+3 vs last
Activity classification
See how your time breaks down.
DevClocked classifies your coding sessions so you can understand your evolution as an engineer, not just your output.
Planning
24%
Architecture decisions, design docs, and technical planning sessions.
Building
63%
New feature implementation, writing production code, shipping.
Debugging
12%
Issue resolution, stack traces, reproduction steps, patching.
Refactoring
1%
Code cleanup, performance optimization, tech debt reduction.
Comparison
GitHub Insights vs. DevClocked
METRIC
GITHUB
DEVCLOCKED
Commit count
~
✓
Lines changed
~
✓
Session duration
✗
✓
Active coding time
✗
✓
Idle gap detection
✗
✓
Focus windows
✗
✓
Multi-repo projects
✗
✓
Language breakdown
~
✓
Context switch count
✗
✓
Research time (browser)
✗
✓
Frequently Asked Questions
Everything you need to know about DevClocked
GitHub Insights shows commit frequency and lines changed. DevClocked adds the time dimension, how long sessions lasted, where you focused, idle gaps, and multi-tool activity (IDE + browser + terminal). It's the difference between knowing you made 12 commits and knowing you spent 7 hours of deep work across 3 repos.
No. DevClocked tracks metadata, file names, languages, session timestamps, and commit messages. It never reads, stores, or transmits your actual source code. Your code stays on your machine.
Yes. DevClocked tracks activity at the IDE and file system level, not through the GitHub API. Private repos are tracked the same way as public ones, through your editor activity.
It doesn't rely on git alone. DevClocked uses real-time signals from your IDE (file opens, saves, focus events) combined with commit metadata to build an accurate session timeline. Git data enriches the picture, it doesn't define it.
Own your output
Stop letting green squares define your work.
Get the metrics that actually reflect your engineering effort. Free tier, no credit card required.
Start Tracking Free