Track Your Time in the Terminal
Vim, zsh, tmux, make, cargo — your terminal is your IDE. DevClocked is the first time tracker that actually sees terminal-native workflows.
Terminal preview
Shell work gets stitched into the same day.
Terminal-native workflows get a dashboard record beside the CLI: one active session with project, source, focus, and tool context.
Every Time Tracker Was Built for GUI Editors
Toggl needs a browser tab. Harvest needs a desktop app with a start button. RescueTime watches window titles. None of them understand terminal workflows. If you live in the terminal, your time tracking has a massive blind spot — or you're manually starting timers, which defeats the purpose.
How It Works
Install the daemon
The DevClocked daemon runs as a lightweight background process. Install via the Mac app or standalone CLI.
Code in your terminal
Use vim, zsh scripts, make, cargo build — any terminal workflow. The daemon watches for file changes and process activity.
Sessions appear automatically
Every terminal coding session shows up in your dashboard with project, duration, and file metadata. Zero configuration.
Why Track Terminal Sessions?
Capture invisible work
Terminal workflows are invisible to traditional trackers. DevOps, scripting, vim sessions, build processes — DevClocked captures all of it.
Works with every tool
vim, neovim, emacs, nano, tmux, screen, zsh, bash, fish — if it modifies files in a project directory, DevClocked tracks it.
No plugins or extensions needed
Unlike IDE-based trackers, the daemon works at the file system level. No vim plugin, no bash script, no configuration. It just works.
Combine with IDE tracking
Switch from terminal to VS Code to Claude Code — DevClocked keeps one continuous session. All sources feed the same timeline.
Frequently Asked Questions
Everything you need to know about DevClocked
All of them. DevClocked tracks at the file system and process level, not the terminal emulator level. iTerm2, Terminal.app, Alacritty, Kitty, Warp, Hyper — if it runs processes that modify code files, DevClocked sees it.
Yes. The daemon detects file changes and process activity regardless of your terminal multiplexer. Activity in tmux panes, screen windows, or nested shells is all tracked the same way.
Remote SSH tracking depends on where file changes happen. If you're editing files locally that sync to a remote machine, those edits are tracked. For pure remote work, the VS Code Remote extension can send ticks from the remote environment.
Yes. The daemon watches for file saves and modifications in your project directories. When vim or neovim writes to a file, DevClocked detects it and logs the activity. No vim plugin required.
If no file changes or process activity are detected for 5 minutes, the session pauses automatically. When you resume coding, tracking picks back up. No false positives from leaving a terminal window open.
Your Terminal Work Deserves Tracking Too
Install once. Every terminal session, captured automatically. Free tier — no credit card required.
Start Tracking Free