DevClocked - Know Where Your Dev Hours Actually Go
Automatic time tracking across VS Code, Cursor, Claude Code, and Chrome — with a unified dashboard to see everything.
Most time trackers ask you to start a timer. DevClocked doesn't. It runs silently in the background, capturing every coding session, commit, and AI interaction — then gives you a complete picture on your DevClocked dashboard.
This extension is one piece of the puzzle. DevClocked tracks your full dev workflow — IDE, terminal, browser, and AI tools — from a single dashboard. Create a free account to get started.
How It Works
- Install this extension in VS Code or Cursor
- Get your API key at devclocked.com (free account)
- Code normally — tracking starts automatically, no buttons or timers
- Open your dashboard at app.devclocked.com to see where your time went
That's it. No configuration required.
What Gets Tracked
- Every coding session — start time, duration, project, and branch
- File activity — which files you worked on and for how long
- Git commits — time linked to specific commits
- Cursor AI activity — metadata only (no prompts or responses are ever collected)
- Idle detection — automatically pauses when you step away
What does NOT get tracked: Your code, your prompts, your file contents. Only timestamps and metadata. Read our privacy details below.
Why DevClocked Over WakaTime / Codetime?
|
DevClocked |
Others |
| AI tool tracking (Claude Code, Cursor) |
Yes |
No |
| Chrome extension for browser activity |
Yes |
Limited |
| macOS desktop app (menubar) |
Yes |
No |
| Unified dashboard across all tools |
Yes |
IDE-only |
| Privacy-first (no code collection) |
Yes |
Varies |
DevClocked is purpose-built for the AI-assisted development workflow. If you use Cursor, Claude Code, or browser-based AI tools alongside your IDE, no other tracker gives you the full picture.
The Full DevClocked Ecosystem
This VS Code extension tracks your IDE activity. For full-workflow coverage:
- Web Dashboard — Analytics, session history, project breakdowns
- Desktop App — macOS menubar app, tracks Claude Code terminal sessions
- Chrome Extension — Tracks GitHub, Stack Overflow, and browser-based dev tools
- CLI —
devclocked login, devclocked status from your terminal
Sign up free at devclocked.com to connect everything.
Commands
| Command |
Description |
DevClocked: Set API Key |
Connect your DevClocked account |
DevClocked: Clear API Key |
Disconnect your account |
DevClocked: Start Session |
Manually start a tracking session |
DevClocked: Stop Session |
End the current session |
DevClocked: Select Active Project |
Choose which project to track |
DevClocked: View Stats |
Open your dashboard |
DevClocked: Flush Queue |
Force sync pending activity |
DevClocked: Settings |
Open extension settings |
Configuration
Configure via VS Code Settings (Cmd+, / Ctrl+,):
| Setting |
Default |
Description |
devclocked.autoStart |
true |
Auto-start tracking when opening a workspace |
devclocked.tickInterval |
30 |
Activity tick interval in seconds |
devclocked.idleTimeout |
15 |
Minutes of inactivity before pausing (1-60) |
devclocked.excludedFolders |
["node_modules", ".git", "dist", "build"] |
Folders to exclude from tracking |
devclocked.deviceName |
"" |
Custom device name for multi-device setups |
devclocked.cursorIntegration |
true |
Track Cursor AI chat activity metadata |
devclocked.debug |
false |
Enable debug logging |
Privacy & Security
- Your code never leaves your machine — only timestamps, file paths, and project names are synced
- No prompts or AI responses collected — Cursor integration tracks metadata only
- Secure transport — all data encrypted via TLS 1.3
- API key stored in VS Code's encrypted secrets — not in plaintext config
- No telemetry — we don't collect usage analytics from the extension
- Open source — inspect the code yourself
Works With
- VS Code — Full support
- Cursor — Full support with AI activity tracking
- VS Code Insiders — Full support
- Remote Development — SSH, WSL, and Containers
Troubleshooting
Extension shows "Not Connected"
- Run
DevClocked: Set API Key from the command palette
- Ensure your API key starts with
dck_
- Check your internet connection
Activity not syncing
- Run
DevClocked: Flush Queue to force sync
- Check the Output panel (
View > Output > DevClocked) for errors
- Verify your API key hasn't been revoked at devclocked.com/settings
High CPU usage
- Add large folders to
devclocked.excludedFolders
- Increase
devclocked.tickInterval to reduce frequency
Support
devclocked.com — See where your dev hours actually go.
