Hi HN — I built Cursor Cost Explorer after my monthly Cursor bill started creeping up and the official dashboard gave me almost no clue why.

I use a mix of models across sessions, sometimes one long thread, sometimes lots of tiny requests with different models, and one month my usage just ran wild. The Cursor dashboard showed not the patterns that matter: which models I used for which tasks, when cache wasn’t helping, or whether I’d be cheaper on a different plan.

So I exported my Cursor CSV and built a small analyzer that runs locally. The first time I loaded my CSV I could see a bit inside the data: a handful of expensive "thinking" model calls sprinkled across many tiny tasks. That single analysis pointed to a few concrete changes I could make that immediately cut my projected monthly spend.

What it does (short) - Parse Cursor CSVs and show where money is actually spent (by model, by day, by request) - Highlight model inefficiencies and cache patterns and give prioritized, actionable recommendations (plan change, model migrations, simple workflow fixes) - Runs entirely locally — open the demo in your browser or run `npx cursor-cost-explorer` on your machine and your CSV never leaves you, also great for agents.

UIs: - Web demo: `https://dalssoft.github.io/cursor_cost_explorer/` - CLI: `npx cursor-cost-explorer `

Would love feedback.

Comments URL: https://news.ycombinator.com/item?id=45894242

Points: 1

# Comments: 0