One command to install
Run npx -y @devclocked/cli@latest setup. It authenticates you and registers the MCP server with Claude Code.
The first time tracker built for Claude Code, Codex CLI, and terminal-native workflows. If your IDE is a terminal, DevClocked already sees you.
Definition
Terminal tracking is automatic time tracking for development work that happens in a shell rather than an editor window, including Claude Code and Codex CLI sessions and agent runs in editors like Cursor. DevClocked records each session as a Work Block with its project, duration, model, tokens, and cost, and splits the time between human hands-on work and agent runs. Nothing is entered into a timer, and no keystrokes or screenshots are captured.
Terminal preview
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
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
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 v1.2.0
Project: devclocked-terminal
Ready for agentic coding
Writing middleware/signed_payloads.go...
Updating tracker_service.go...
Running tests...
Session: devclocked-terminal | Source: terminal
Duration: 1h 23m | Ticks: 34 | Branch: feat/signed-tracking
Live dashboard
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.
Run npx -y @devclocked/cli@latest setup. It authenticates you and registers the MCP server with Claude Code.
Use Claude Code, Codex CLI, vim, or any terminal workflow. The Mac app daemon or a tracked CLI session captures the activity.
AI pair-programming sessions show up in your dashboard alongside IDE sessions, no setup per project.
MCP integration
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
Supported tools
Claude Code
Daemon + hooks
Codex CLI
Daemon + hooks
Cursor
Extension + hooks
Antigravity
Extension + hooks
VS Code
Extension
Terminal / zsh
Daemon
Vim / Neovim
Daemon
tmux / screen
Daemon
GitHub
Synced
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
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.
Everything you need to know about DevClocked
Run npx -y @devclocked/cli@latest 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.
AI usage — agent turns, tokens, the AI-vs-human split — is captured for Claude Code, Codex CLI, Cursor and Antigravity. Claude Code and Codex are read by the Mac app's daemon on macOS, or by a hook plugin on Windows and Linux; Cursor and Antigravity are covered by the DevClocked extension plus a hook plugin, and Antigravity reports the model without token counts. Gemini CLI is not captured yet. Terminal and editor time is tracked far more widely than that, and any tool implementing the MCP standard can connect to DevClocked's MCP server.
The Mac app's 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. On other platforms, the CLI's devclocked session command tracks from a wrapped shell.
Yes. The Mac app's 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
Run npx -y @devclocked/cli@latest setup. Claude Code, Codex CLI, terminal workflows, all tracked. Free 7-day trial. Add a card to start.
Start Tracking FreeWrap Claude Code, Aider, and any CLI workflow without changing how you work.
We use cookies to understand how you use DevClocked and to improve the product. See our Privacy Policy.