I recently posted that Code Tracker AI is opening early access — and I want to clarify what that actually means.
This is feedback-driven early access, not a marketing beta. The point is to get real developer workflows running through it and tune what matters.
(Here’s the original post for context: https://dev.to/monahidalgo/code-tracker-ai-is-opening-early-access-45ha)
What I need from testers
1) Install + run one real project scan
I want to validate that the first-run experience is clean, fast, and stable on real projects.
2) Use Code Books for a week
Code Tracker AI is built to help you capture real work and keep developer-owned documentation inside the IDE. I want to know:
- Does it replace scattered notes?
- Does it fit naturally into your flow?
- What feels friction-heavy?
3) Tell me what to cut
I’m optimizing for signal over noise. I’d rather ship fewer insights that are genuinely useful than flood the UI with “AI output.”
What’s already working (real, end-to-end)
✅ Code Books panel
- Collapsible sidebar + document management
- Search
- Split editor view (built like a proper IDE tool window)
✅ Real project intelligence
- Real Git analysis (commits, branches, contributors)
- Real project scanning (file counts, stack detection, dependency analysis)
✅ Auto-Notes + AI docs
- Project overview + development timeline generated from real scans
- Manual scan button + first-run auto-scan dialog
- Progress UI that shows real analysis results during scan
If you want in
Join the waitlist here: https://codetrackerai.com/
If you do join, I’ll follow up with access + a short “what to test” checklist so you’re not guessing.
— Mona Hidalgo
Founder & Software Engineer
Top comments (1)
This looks like a promising tool! Excited to see how Code Tracker AI can help improve debugging and code insights. The early access approach and feedback loop with testers should really help shape it into something practical. Looking forward to trying it out! 🚀