Never Start a Timer Again
DevClocked detects when you start coding across VS Code, Cursor, Terminal, and your browser — then builds your timesheet automatically.
Live session surface
The timer disappears into the workflow.
Show the actual model users will meet in-app: one unified work block fed by IDE, browser, terminal, and desktop signals, with repo, branch, active time, and focus quality visible at a glance.
Manual timers break your flow.
You forget to start them. You forget to stop them. You round up to "close enough." At the end of the week, your timesheet is fiction. Developers lose 15-30 minutes daily on time tracking admin — and still end up underbilling because the data is inaccurate.
Install the extension
Add the VS Code or Cursor extension. Install the Mac app or Chrome extension. Takes under 60 seconds.
Code normally
No timers, no buttons, no interruptions. DevClocked detects file edits, saves, and focus events in the background.
Review your sessions
Every session auto-generated with project, repo, branch, duration, and idle gaps. Your timesheet writes itself.
> alpha-service / feat/auth-v2 / local signals only
Terminal native
CLI for developers who live in the terminal.
The DevClocked daemon watches for coding activity in your shell — file edits, git operations, Claude Code sessions. Or use devclocked start for manual control. Either way, sessions flow to your dashboard automatically.
IDE extensions
Deep integration with VS Code and Cursor.
Native extensions track active time per file, detect idle gaps, and capture branch switches. See exactly where complexity lives — down to the file level. No configuration required.
Browser tracking
Research time counts too.
The Chrome extension captures your research flow on developer domains — GitHub, Stack Overflow, MDN, and documentation sites. Non-dev browsing is never tracked. Research time attaches to your active coding session automatically.
Only dev-related domains are tracked. Gmail, social media, and personal browsing are always ignored.
Multi-source sessions
One session. Multiple tools. Zero gaps.
Switch from VS Code to Chrome to Terminal — DevClocked keeps the same session alive. Activity from any source prevents idle timeout, so your sessions reflect how you actually work.
All sources feed one session. No gaps between tool switches.
Coming soon
Mobile companion app.
View sessions, review timesheets, and manage projects from your phone. Focus timer with Pomodoro mode. Sync across all your devices.
Frequently Asked Questions
Everything you need to know about DevClocked
VS Code and Cursor have native extensions with deep file-level tracking. The Mac desktop app and terminal daemon detect activity in any editor — including Vim, Neovim, Emacs, and JetBrains IDEs.
DevClocked tracks real activity signals — file edits, saves, focus events, and git operations. If no activity is detected for 5 minutes, the session pauses. When you resume, it picks up automatically. No false positives from leaving your editor open during lunch.
Yes — but only developer-related domains (GitHub, Stack Overflow, MDN, documentation sites). Personal browsing is never tracked. Dev domain time attaches to your active coding session as "research time."
Yes. Every auto-generated session can be edited — adjust start/end times, change project assignment, mark as billable or non-billable. The automation gives you the baseline; you control the final record.
DevClocked's multi-source protection keeps your session alive. Activity from any source (IDE, browser, terminal, desktop app) prevents idle timeout. You get one continuous session that reflects your actual workflow, not fragmented entries.
Automatic by default
Your timesheet is already being written.
Install once. Every coding session, captured. Every hour, accounted for. Free tier — no credit card required.
Start Tracking Free