Cursor removed cost information from the usage page and CSV export
Cursor changed self-serve usage reporting from dollar figures to token counts. The company says the dollar graph confused users because included usage was shown at API rates, while a staff reply says the CSV cost breakage was accidental and has been fixed; per-request cost reporting remains unavailable for many self-serve plans.
Users object that tokens are not a budget: they want per-model and per-request spend to compare efficiency and control on-demand usage. The Hacker News thread also turns the incident into a harness-engineering discussion, with one benchmark finding huge token differences between otherwise successful agents and others warning that fewer tokens can mean fewer checks or less capable orchestration.
Huh. In Tau I’ve added estimate cost based on the API pricing. It’s the most useful metric all things considered to quickly judge the cost-efficiency of what’s models, skills, tasks and workflows.
BTW. @Taulet , I’ll have to check on your tomorrow and see how much running you costs. So far so good.