This content originally appeared on DEV Community and was authored by Mona Hidalgo
It’s been just over a month since day one — and the plugin is still deep in development.
Every commit, test, and tweak moves it closer to something I believe developers actually need — not just another AI code assistant.
The Developer Burnout Problem: Why I Built Code Tracker AI to Protect Focus, Not Replace It
Developers don’t just need AI that writes code — we need AI that watches our workload.
After years of long coding sprints, late commits, and half-written notes scattered across personal journals, I realized most dev tools track what we build — not how we build it.
That’s how Code Tracker AI was born: a JetBrains plugin that doesn’t try to “replace” you with code suggestions, but rather supports your mental focus, workflow health, and intellectual property.
What It Actually Tracks
Session time & context switches — to identify when focus drops
Code Books — automatic developer journals that log your progress
Brain Werks Clock — a Pomodoro-style focus timer for cognitive balance
Proof-of-Dev logs — timestamped records for IP protection and accountability
What’s Next
I’m currently integrating:
Smart session summaries (“What you coded this hour”)
Auto-synced dev logs across JetBrains and VS Code
If you’ve ever hit flow state just to lose track of what changed or how long you’ve been grinding — this one’s for you.
Let’s Talk
Would you actually use a tool that tracks your developer health instead of just your commits?
How do you personally handle burnout, balance, or focus during deep coding sessions?
Try the early preview at codetrackerai.com
Follow me here for dev log updates — I’m sharing everything build-in-public style. 
Part of the Building Code Tracker AI series — sharing the journey from prototype to launch.
— Mona Hidalgo
Founder, Code Tracker AI
mona@codetrackerai.com
This content originally appeared on DEV Community and was authored by Mona Hidalgo