Never lose a vibe coding session. Archive, replay, search.
Your vibe coding sessions disappear into JSONL files you'll never open again. yolog.dev Desktop fixes this. 🗂️ Archive & Replay – Import from Claude Code. Full playback with timeline. 🔍 Search – Find that decision you made with AI couple days ago. 📊 Vibe Metrics – Token leverage, burn rate, flow detection, streak tracking. 💰 Cost Tracking – Per-project / Per-session breakdowns. 🔒 Privacy-First – All data stays local. ~10MB app.
Hey PH! 👋
I built yolog because I kept having the same frustrating experience: solving a problem with Claude Code, then hitting the same problem weeks later and having no idea where that session went.
AI coding sessions are like a new form of documentation – they capture not just the code, but the reasoning, the failed attempts, and the "aha" moments. They are the pulse of the interaction between you and the AI. They shouldn't disappear.
The "Vibe Metrics" came from realizing that traditional dev metrics (lines of code, commits) don't capture AI-assisted work. When you prompt Claude with 50 characters and get back 500 lines of working code, that's a 10x leverage moment worth understanding.
I'm especially proud of the streak system, it gamifies daily vibe coding and shows long-term patterns in your collaboration style.
Would love your feedback:
* What metrics would you want to track?
* What further vibe coding CLI / tools should we support next?
* Would team/sharing features be valuable?
Best,
Yuanhao
