Cursor usage tracking changed this week in a way that should worry anyone paying for an AI coding tool. The Cursor team made the usage page tokens-only for individual and Teams plans. Spend metric and Cost column are gone. Usage CSV no longer includes dollar costs.
Users who watch their spending every day lost the one number that mattered. Spend tracking is now token math, and that math doesn’t map to a dollar sign.
The thread on Cursor’s own forum is more than 8,000 views deep and still climbing. It hit the top of Hacker News within hours, racking up hundreds of points and more than 100 comments. The anger isn’t subtle.
Kevin Neilson, who answers for the Cursor team, wrote “This was an intentional change, not a temporary reporting issue.” He posted that in the forum thread.
Neilson added that usage reporting for self-serve plans including Teams is now token-based. Dollar values are no longer returned by the dashboard Usage endpoint. Individual plans keep token counts for included usage. On-demand charges beyond the plan stay visible in the Cost column for Ultra users.
Why the Cursor usage change matters
Cursor’s reasoning, per Neilson, is that dollar amounts confused people. Included usage made the displayed figure look higher than the actual plan cost. So instead of fixing the presentation, the team removed the dollars for everyone on self-serve plans.
Teams admins lost more. One admin reported a combined spend of 30,000 dollars in the current billing cycle. He said there’s now no per-model dollar breakdown for self-serve Teams.
Another wrote that the change feels sketchy. He asked whether the only options are to sit, suffer, and hope Cursor stops being shady.
The official workaround is thin. Dollar figures still exist in the Spending tab, and Teams admins can see per-user on-demand totals under Members. The Admin API still returns cost fields. None of that gives individuals back the per-model, per-request cost view they had before this week.
The retroactive wipe is the real problem
Here’s the part that stings. The change applies to history, not just new activity. One developer who built tooling on Cursor’s usage API found that cost fields are now zeroed out for every event. Old records that previously showed real values are zeroed too.
Neilson confirmed that’s by design. Because the conversion happens when records are read, historical results are affected too. The data clearly still exists internally, since period totals remain. It just isn’t visible to the people paying the bills.
That matters for a metered product. Independent cost trackers, team budgets, and per-model efficiency checks all relied on those fields. Removing them retroactively breaks every tool built on top of them.
Cursor’s answer to Teams admins is a separate Admin API that most users don’t have access to.
What this tells us about AI coding costs
This is the flip side of the tokenmaxxing panic that OpenAI’s agent pricing cuts tried to address. Cursor built its business on usage-based pricing. Ultra plans bill by tokens.
When the number users actually watch is the dollar figure, and the vendor removes it, the reasonable read is that transparency hurts revenue.
The HN thread shows why users care so much. One commenter measured the same agentic task across six harnesses. Token use swung from 172,000 to 5 million depending on the tool.
Another noted that Claude Code’s memory system alone can add thousands of tokens of system prompt per task.
If harnesses and hidden system prompts swing cost by 30x, hiding the dollar amount is the last thing users need. Token counts without prices are meaningless when every model prices differently. Cursor usage screens now force that math onto each user.
I covered Cursor, Codex, and Claude Code in my best AI coding agents roundup recently, and the editor is still excellent.
But this is a product decision that reads like the vendor betting users won’t leave over visibility. Cursor usage data is the one honest signal users have, and this week it went dark.
There’s an easy fix: bring the dollar column back, or add a toggle that defaults to tokens. Neilson said the team has heard the feedback, and the thread is still active.
Until that happens, if you run a team on Cursor, export whatever cost data you still have while the Admin API path works. Set a hard spending alert on your payment side. Watching a Cursor usage total you can’t convert to money is how surprise invoices happen.
That’s the real cost of this change. It didn’t remove spending. It removed the warning label.
If you’re on Cursor and this bugs you, the leverage is real. Competitors like Codex, Claude Code, and open-source options ship their own usage dashboards with dollar figures. Switching a team is easier than it was a year ago.
The HN thread is full of people saying exactly that. Cursor’s own forum shows what happens when a tool that builders depend on starts treating transparency as optional. The backlash lands on the front page in hours. If you run a team, treat this as a warning about every Cursor usage decision that follows.
