The Code Book your IDE never had.
Code Tracker AI captures every change, developer note, and architectural decision into a permanent, queryable project memory. The “why” survives the next handoff, the next vacation, the next sprint.
Public waitlist open since September 2025. Built by solo founder Mona Hidalgo of Mix It Hub, LLC.
Refresh window is now risk-weighted after the 2024-09 incident report. High-risk uids (elevated sessions, mfa-bypass attempts) get a 60s buffer on top.
Works with the JetBrains IDEs you already use
…and every other JetBrains IDE
The problem
The “why” is the part that disappears first.
Handoffs
The new hire gets the repo, not the rationale. Six weeks later, they re-litigate the same rejected option.
Vacations
A long leave clears working memory. You come back to PR-842 and cannot remember what tradeoff you almost took.
Audits
Six months on, a team lead asks why a decision was made. The Slack thread is gone, the JIRA is closed, the answer is folklore.
What it does
A living memory for the codebase — written by the people who actually know it.
Capture every change with its why.
As you write, Code Tracker AI logs what changed and what you meant by it — the rationale, the rejected alternatives, the constraints. Not a TODO that goes stale. A durable, time-stamped entry that ages into institutional knowledge.
Locked in a local vault.
Encrypted on disk, on your machine. No silent sync, no opaque cloud copy of your project memory. Recall runs locally.
AI-powered recall, on demand.
Ask “why is this here?” — get the original decision, the constraints, the alternatives it tried, in seconds.
Docs that write themselves.
Turn the recorded decisions into the architecture overview, the runbook, the onboarding guide — already half-written.
See it in action
The whole plugin, right inside your IDE.
No dashboards to leave for. Code Tracker AI captures the session, then writes the story — what you built, why, and what's next.
A coding partner that knows your project.
Ask questions, debug, and get explanations without leaving the IDE — the chat sees your real session data, not just your prompt. Switch between models to fit the task.
Your work, written up automatically.
Every session captured — time, files, commits, flow — then turned into an AI narrative of what you built and why. No manual logging.
Catch issues before they cost you.
62+ rules across 10 languages, scored by severity — with a plain-English WHY, HOW, and IMPACT for every finding.
Stay sharp. Avoid burnout.
A built-in focus timer that nudges healthy breaks, so you keep momentum through long sessions without running yourself into the ground.
A real document editor, built for engineers — inside the IDE.
Not a scratchpad. A full Word-style writing space for specs, architecture docs, runbooks, and learning archives — rich formatting, templates, and multi-format export (PDF, DOCX, Markdown). No switching to Notion or Google Docs. Your docs live right next to the code they describe.
How it works
Five steps. Zero ceremony. Runs while you code.
The plugin lives in your JetBrains IDE. Capture is in-band; recall is a keystroke.
- 01
Write
You edit code in any JetBrains IDE.
- 02
Capture
The plugin reads diffs and intent as it happens.
- 03
Lock
Notes + rationale land in the encrypted vault.
- 04
Recall
Ask any time — AI pulls the original context.
- 05
Document
Auto-roll the memory into docs and runbooks.
Why now
Adjacent to the AI-coder boom — built for the gap they leave behind.
Copilot, Cursor, JetBrains AI, and Tabnine own the next line. Code Tracker AI owns every line that already shipped — and rides the AI code-generation market projected to reach roughly $30.1B by 2032. Emerging memory APIs like Mem0 and Zep make a living project memory feasible without a vector DB you have to babysit.
Use cases
Whoever you are, the same pain looks the same.
Solo developer. Scaling team. Enterprise. When the codebase outlives any single contributor's memory, recall beats archaeology.
You are the team. A four-month side project gets picked back up — and the context comes back with it.
“I left this in March. I picked it up in July and we were working again in ten minutes.”
Onboarding stops being a senior-engineer tax. New hires ask the codebase, not the calendar.
“Handing a new joiner the repo and the memory beats handing them the Slack scrollback.”
Audits, compliance, postmortems — decisions you made two years ago come with the receipt and the rationale.
“Compliance asked why we structured the write path like this. One answer: the memory entry from the day.”
Get on the list
Be there when the first build ships.
Early access goes to waitlist members first. Reserve your spot and we'll reach out the moment Code Tracker AI is live on the JetBrains Marketplace.