Allan Napier

We're thrilled to introduce Efficiency Trend Analysis in ClaudeSavvy v2.2 a smarter way to understand whether your Claude Code usage is actually improving over time. What We Track When you select a time period (Week, Month, or Today), ClaudeSavvy now compares your current metrics against the equivalent previous period: Cost per Session: Are you spending more or less per conversation? Cost per Message: How efficient is each interaction? Tokens per Message: Is your context window staying clean or getting bloated? Cache Hit Rate: Are you effectively reusing cached prompts? The new Tokens per Message metric is particularly useful. If this number keeps climbing, it means your conversations are accumulating context old messages, file contents, and history that inflate every subsequent API call. A rising trend here is a signal to: Start fresh conversations more frequently Use /compact to summarize long sessions Avoid including unnecessary context in prompts Tool Cost Trends on Features Page We've also added trend analysis to the Features page. The tool usage table now shows: Cost per Call: How much does each tool invocation cost? Trend: Is this tool getting more or less expensive to use? This helps you identify which tools are driving costs and whether their efficiency is improving. Smart Recommendations When trends indicate a problem, ClaudeSavvy generates actionable recommendations. For example: Cost per session up 25%? We'll suggest reviewing model selection and conversation length Tokens per message up 30%? We'll recommend context window cleanup strategies Cache hit rate down 10%? We'll explain how stable prompts improve caching check it out now with pip install claudesavvy or visit codebotiks.com

"Hey Product Hunt! I'm Allan, and I've been obsessed with Anthropic s new claude-code CLI. It s incredibly fast, but there was one problem: spend anxiety. I found myself constantly checking my billing dashboard to see if a long session had eaten my budget. We built Claude Monitor to be the 'local control center' for your Claude Code usage. Why we built it local-first: Privacy: It reads your local ~/.claude logs. We don't want your API keys. Speed: Instant dashboard updates. Context: See exactly how much you're saving with prompt caching (the 'hidden' hero of Claude pricing). We had a great reception on Hacker News yesterday (60+ clones in 24 hours!), and we're excited to bring it to the broader maker community here. It's 100% open-source. Check it out, run it locally, and let us know what features you want next (Cost alerts? Per-project breakdown?). Website: https://codebotiks.com Repo: https://github.com/allannapier/c...