One command to install
Run npx devclocked setup. It authenticates you and registers the MCP server with Claude Code.
> TERMINAL & AI-NATIVE TRACKING
Track time where AI developers actually work
The first time tracker built for Claude Code, Codex CLI, and terminal-native workflows. If your IDE is a terminal, DevClocked already sees you.
Terminal preview
CLI and agent sessions become first-class work blocks.
Terminal tracking is most believable when the command output and dashboard summary appear together: active session, source, project, token usage, and cost in one compact product surface.
The blind spot
6 hours of AI pair programming. 0 hours tracked.
AI-native developers live in the terminal. Claude Code, Codex CLI, vim, tmux. Traditional time trackers don't see terminal activity. If you're pair-programming with an AI agent all day and none of it shows up in your timesheet, your billing is broken. The agentic coding paradigm is a blind spot for every other tracker.
Fix This NowIn action
DevClocked sees your terminal sessions.
Claude Code can plan, edit, and test from the terminal while DevClocked records the session as real work: source, project, duration, ticks, and branch, without keystroke logging.
Claude Code
$claude
Claude Code v1.2.0
Project: devclocked-terminal
Ready for agentic coding
>Refactor tracking middleware to use signed payloads
Writing middleware/signed_payloads.go...
Updating tracker_service.go...
Running tests...
DEVCLOCKED_TRACKING
Session: devclocked-terminal | Source: terminal
Duration: 1h 23m | Ticks: 34 | Branch: feat/signed-tracking
devclocked
●Bash(node dist/index.js summary | cat)
main
22mTracking
Today: 4h 3m · 4 repos · 12 blocks · +6.0k/-797 · 176...
devclocked/marketing
1h 58m
devclocked/mac-app
1h 33m
devclocked/cli
22m
devclocked/docs
10m
Live dashboard
Your day at a glance. Right in the terminal.
Developers who live in the shell should not need a browser tab to know what has been tracked. The CLI summary gives current branch, active session time, repo breakdown, and tracked blocks in the same place the work is happening.
How it works
One command. Code with AI. Sessions appear.
Step 1
Step 2
Code with your tools
Use Claude Code, Codex CLI, vim, or any terminal workflow. The daemon watches process and file activity.
Step 3
Sessions appear automatically
AI pair-programming sessions show up in your dashboard alongside IDE sessions, no setup per project.
MCP integration
Native Model Context Protocol support.
DevClocked speaks MCP natively. Any MCP-compatible tool can send activity signals to DevClocked without custom integration. As the MCP ecosystem grows, your tracking grows with it.
MCP is the open standard (backed by Anthropic) for connecting AI tools to external services. DevClocked was one of the first productivity tools to adopt it.
MCP architecture
Claude Code
→DevClocked MCP
Codex CLI
→DevClocked MCP
Cursor (MCP)
→DevClocked MCP
Custom MCP client
→DevClocked MCP
Supported tools
Works with the tools you already use.
Claude Code
Supported
Codex CLI
Supported
Cursor
Via MCP
VS Code
Extension
Terminal / zsh
Daemon
Vim / Neovim
Daemon
tmux / screen
Daemon
GitHub
Synced
setup
$npx devclocked setup
DevClocked CLISetup: one command, fully installed
Step 1/2: Authenticate
Enter your DevClocked API key: ****
Authenticated as you@email.com
Step 2/2: Register MCP server
MCP server registered with Claude Code
DevClocked is installed!
Restart Claude Code to activate.
One command install
npx devclocked setup. That's it.
One command authenticates you and registers the MCP server with Claude Code. No config files, no manual steps. After setup, restart Claude Code and ask “how long have I been coding today?” and it just works.
Frequently Asked Questions
Everything you need to know about DevClocked
Run npx devclocked setup in your terminal. It will prompt for your API key, validate it, and register the MCP server with Claude Code automatically. After setup, restart Claude Code and the MCP server will be active. You can verify by typing /mcp in Claude Code.
MCP (Model Context Protocol) is an open standard for connecting AI tools to external services. It means Claude Code can query your DevClocked stats directly, ask "how long have I been coding today?" and it answers with your live session data. As more AI tools adopt MCP, DevClocked's tracking coverage grows automatically.
Claude Code is supported via both the daemon (automatic session detection) and the MCP server (live stats in Claude). Codex CLI and Cursor support MCP natively. Any tool that implements the MCP standard can connect to DevClocked's MCP server.
The DevClocked daemon monitors Claude Code session files and file system changes in your project directories. When it detects AI-assisted coding activity, it classifies it (coding, planning, debugging, reading) and sends ticks to the tracking server. No keystroke logging, just file change detection and session metadata.
Yes. The daemon detects activity at the file system and process level, so it works regardless of your terminal multiplexer. Activity in tmux panes is tracked the same as direct terminal usage.
Built for 2026, not 2020
Your AI tools track your time. Automatically.
Run npx devclocked setup. Claude Code, Codex CLI, terminal workflows, all tracked. Free tier, no credit card required.
Start Tracking Free