Track Your Time in Claude Code
You spend hours pair-programming with Claude Code every day. None of it shows up in your timesheet. One command to install. Tracks coding, planning, and debugging automatically.
Claude Code preview
AI pair-programming becomes visible work.
Claude Code sessions become durable DevClocked records: duration, source, token load, and project attribution that survive beyond the chat.
The Most Productive Tool in Your Stack Has Zero Time Tracking
Claude Code rewrites entire files, scaffolds new features, and refactors codebases in minutes. But every time tracking tool on the market was built for the IDE era. They don't see terminal-based AI pair programming. So you're doing your most impactful work — and it's invisible.
╭ Claude Code v1.2.0
│ Project: payment-service
╰ How can I help?
Creating handlers/stripe_webhook.go...
Adding webhook signature validation...
Writing tests for subscription lifecycle...
Updating routes.go with /webhooks/stripe endpoint...
Session: payment-service | Source: daemon
Duration: 2h 47m | Ticks: 52 | Branch: feat/stripe-webhooks
Files changed: 4 | Lines: +342/-18
How It Works
One command install
Run npx devclocked setup in your terminal. It authenticates you and registers the MCP server with Claude Code. Takes 30 seconds.
Use Claude Code normally
Open your terminal, type claude, and start coding. DevClocked tracks your sessions automatically. Ask Claude "how long have I been coding?" and it tells you.
See your sessions
Every Claude Code session appears in your dashboard with duration, activity type (coding, planning, debugging), and project context. No manual entry.
Why Track Claude Code Sessions?
Bill for AI pair programming
If you're a freelancer using Claude Code for client work, those hours are billable. DevClocked captures them automatically so you don't leave money on the table.
Understand your AI workflow
How much of your day is AI-assisted? Which projects benefit most from Claude Code? Track the data and understand your evolving workflow.
Prove your effort
Terminal work is invisible to managers and clients. DevClocked makes Claude Code sessions visible — with duration, project, and file-level metadata.
One session across all tools
Switch from Claude Code to VS Code to Chrome — DevClocked keeps one continuous session alive. No gaps, no fragmented entries.
Frequently Asked Questions
Everything you need to know about DevClocked
Run npx devclocked setup in your terminal. It will ask for your API key, validate it, and register the MCP server with Claude Code. After setup, restart Claude Code. You can verify it's working by typing /mcp in Claude Code — you should see "devclocked" listed as connected.
Never. DevClocked only tracks metadata — session duration, file names changed, repository, branch, and activity type (coding vs planning vs debugging). It never reads your prompts, Claude's responses, or any conversation content.
DevClocked classifies your Claude Code activity automatically: coding (file edits), planning (conversation and architecture discussion), debugging (reading files and making small fixes), and reading (code exploration). This happens based on the shape of tool usage — no content is analyzed.
Yes. DevClocked's multi-source session protection keeps one continuous session alive across all your tools. Switch from VS Code to Claude Code to Chrome — it's all one session.
Yes. The MCP server gives Claude access to your DevClocked stats. Ask "how long have I been coding today?" or "show my weekly summary" and Claude will pull your live data. It can see your sessions, projects, activity breakdown, and lines changed.
Start Tracking Claude Code Today
Run npx devclocked setup. Every Claude Code session, captured automatically. Free tier — no credit card required.
Start Tracking Free