🚀 Code Tracker AI - Now Live on Product Hunt

I built a tool that explains your own code back to you - and it's live on Product Hunt today I've lost count of how many times I've opened a file, stared at a function, and thought "who wrote this?" - then realized it was me, six months ago, with zero memory of why I made that decision. That's the problem Code Tracker AI (CTAI) exists to solve. Not "write code faster" - there's no shortage of tools for that now. The gap I kept hitting, building solo out of rural New Mexico with no team to lean on, was understanding code after the fact: mine, a teammate's, or an AI's. What it actually does CTAI is a JetBrains IDE plugin (IntelliJ, PyCharm, WebStorm, Android Studio) that sits in your editor and: - Gives real-time insight into what a file or function is doing and why - Flags issues with root-cause explanations instead of cryptic linter warnings - Walks you through fixes the way a senior engineer would in a pairing session, rather than just flagging and leaving - Automatically keeps Code Books - a running record of the reasoning behind your decisions, generated as you work, not written after the fact when you've already forgotten - Builds a long-term intelligence layer across the whole project instead of file-by-file linting Under the hood it's built on three pieces I designed from scratch: Build Logs (Git history, session replay, IDE events), AI Insights (60+ security and quality checks), and an AI Narrative engine that turns all of that into plain-English explanations. There's also multi-model LLM routing across Claude, DeepSeek, Llama, Mistral, and Amazon Nova for the chat layer, and a Pomodoro-style focus timer (Brain Werks Clock) if you want session structure built in too. Why now AI can write code faster than any of us can read it. That's the actual bottleneck now - not generation, comprehension. Legacy code, onboarding, your own code from last quarter: all of it still requires a human (or an AI) to reconstruct intent from scratch every time, because nothing captured the why when the decision was made. CTAI is my attempt to fix that at the source, inside the editor, as you're working - not as a bolt-on doc tool you'll never actually maintain. Where it's at CTAI launched on Product Hunt today. It's early - I'm a solo technical founder who designed and built the whole architecture myself - but the JetBrains Marketplace listing is up and I'm actively taking feedback from working developers, which is the whole reason I'm posting this here instead of just on PH. If you've ever felt that specific dread of opening a file you don't remember writing, I'd genuinely like to know: what would make onboarding or re-orienting yourself in old code less painful for you? What's the clarity problem you hit most often? 👉 Check it out and upvote on Product Hunt 🌐 codetrackerai.com I'll be in the comments today answering questions. - Mona Hidalgo Founder & Software Engineer Code Tracker AI 📧 m***@codetrackerai.com Top comments (0)