Launching today
Claude Usage Tracker
See exactly how much you spend on Claude, across every tool
265 followers
See exactly how much you spend on Claude, across every tool
265 followers
No single place shows your total Claude spend across tools. If you use Cursor, Claude Code CLI, Windsurf, Cline, or others — each burns tokens separately and you're flying blind. Claude Usage Tracker auto-detects 9+ tools, scans local session data, and shows everything in one dashboard: daily costs, model breakdowns, heatmaps, session logs, and monthly projections. Native macOS app. Not Electron. No cloud, no accounts, no telemetry. 100% free and open source (MIT).
@stevie_658jjh Have you considered adding projections for cache savings, since those can swing costs big time?
@swati_paliwal That's a great idea! Showing something like "You spent $50 but caching saved you $120" would really put the impact in perspective. The data is already there - just need to surface it. Adding to the roadmap, thanks!
Oh I needed this yesterday! I use Claude Code and Cursor every day and it sounds very useful. The heatmap feature is great too - I bet I'll see a pattern of my late night coding sessions. Does it track token usage retroactively from existing session data, or does it only start counting from when you install it?
@ben_gend Thanks so much! And yes, the heatmap is great for exactly that, you'll definitely spot those late-night patterns (guilty here too).
It works retroactively! The app scans the existing JSONL and log files that Claude Code, Cursor, and other tools already store on your machine (e.g. ~/.claude/projects/, ~/.cursor/, etc.). So the moment you open it, you'll see your full usage history - no need to wait for new data to accumulate.
It also uses the actual timestamps from those session files, so your heatmap and cost breakdown will be accurate all the way back. Give it a try and let me know how it goes!
This is the tool I didn't know I needed. I've been using Claude Code and Cursor side by side for months and had zero visibility into which one was actually eating my budget. Just "oh the bill went up" with no idea why.
The per-model breakdown is really useful too. I bet most people don't realize how much they're spending on Opus vs Sonnet calls. Does it show per-project breakdowns or just overall?
@mihir_kanzariya Thanks! That "oh the bill went up" feeling is exactly why I built this. Right now it shows per-source (Claude Code vs Cursor etc.) and per-model breakdowns, so you can see exactly where the spend is going. Per-project breakdown isn't visualized yet but it's on the roadmap. Give it a try!
@stevie_658jjh how accurate is the cost calculation across different tools? Have you validated it against actual billing from Anthropic?
@denious Good question! The costs are calculated using Anthropic's published per-token API pricing, applied to the token counts logged by each tool. For API users, it should closely match your actual bill. For subscription plans (Pro/Max), the numbers represent API-equivalent cost - basically what your usage would cost at pay-per-token rates, which is useful for understanding your consumption. If you spot any discrepancies with your actual API bill, definitely let me know - happy to investigate!
the heatmaps and monthly projections caught my attention. we've been trying to track our AI tool costs manually and it's a mess. being able to see model breakdowns across different tools would help us optimize which models we use where.
@piotr_ratkowski That manual tracking pain is exactly what this solves. The model breakdown makes it easy to spot where you might be using Opus when Sonnet would do the job - those swaps add up fast. Hope it helps!
Clipboard Canvas v2.0
Love the idea of tracking Claude costs, but curious does it handle cases where users switch between multiple device?
@trydoff Great question! It's local-first so it reads data from each machine separately, but there's a built-in export/import feature - you can export your data as JSON from one device and import it on another to get a combined view.
BrandingStudio.ai
This solves a real problem. Right now I have a Chrome tab permanently open just to monitor usage, which is exactly the kind of friction that shouldn't exist when you're deep in a session.
The normalisation across tools is the hard part you probably don't get credit for in the headline. Each tool storing session data in different formats and locations means this isn't just a dashboard, it's a data pipeline with a UI. The zero setup auto-detection is what makes it actually usable rather than just theoretically useful.
The heatmap feature is the one I'm most curious about. I use Claude Code daily for building and I'd genuinely want to see whether my peak spend correlates with productive sessions or with the ones where I'm going in circles and burning tokens on context that isn't working. That could change how I structure my working day. Installing this today. Congrats on the launch!
@joao_seabra Thank you! The normalization layer was honestly where most of the work went - glad someone noticed.
Love your idea about using the heatmap to spot "going in circles" sessions vs. productive ones. Might explore that angle in a future update.
Would love to hear what patterns you spot!