Cursor changed what its usage page shows on 31 July. Where developers previously saw what each request cost in dollars, they now see token counts. Kevin Neilson of the Cursor team confirmed it in the company’s own forum: “a change shipped today made the Usage page tokens-only for self-serve plans, including Teams”, adding that there is currently no setting to switch back on individual plans.
The next day he removed any doubt about whether it was a glitch. “This was an intentional change, not a temporary reporting issue,” he wrote on 1 August. The timing is awkward. Australian finance teams have spent this year trying to get AI spend under control, and the meter on a widely deployed developer tool has just changed units.
What changed on the usage page
The usage page is where a Cursor user sees consumption against their plan. Until 31 July it broke that consumption down in dollars, per request and per model. It now reports tokens.
The billing has not changed, and neither has the pricing page, which still denominates each plan’s included allowance in dollars. Cursor prices in US dollars: Pro is $20 a month and includes $20 of usage on other models, Pro Plus is $60 and includes $70, and Ultra is $200 and includes $400. The allowance is still priced in dollars. The counter that measures your consumption against it is not.
The change does not appear in Cursor’s changelog. The most recent entries cover Cursor on iPad on 29 July, a low-cost India-only plan on 28 July and the Cursor Router on 22 July. A change to billing visibility shipped without one.
Two different answers from Cursor
A second Cursor employee gave a narrower account on Hacker News, where the thread reached 287 points. Writing as jonjohnsen, they said: “You can still see what you’re billed on the Spending page. We did accidentally break dollar costs in the Usage CSV export yesterday while cleaning up an old feature flag. That was not intentional and the CSV export is fixed now.”
So there are two separate things here, and only one of them was deliberate. The CSV export losing its cost column was a bug, and Cursor says it is resolved. The dollar graph on the usage page was removed on purpose. On that, the same employee was direct: “Some people read it as actual spend, so we decided to remove that graph.”
Enterprise plans keep them. “Enterprise Plans will still show dollar amounts here, but individual plans will not,” Neilson wrote, calling the split deliberate design. The figures were not retired, then. They were withdrawn from everyone below the enterprise tier.

The router that landed nine days earlier
On 22 July Cursor launched Cursor Router, which picks a model for each request rather than leaving the choice to the developer. Cursor’s documentation says two of its three modes, Balance and Intelligence, bill at the routed model’s rate.
The company claims savings of 30 to 50 per cent for enterprise early access customers and around 60 per cent in A/B tests. Those are Cursor’s own figures and have not been independently audited. The same documentation is blunter about the other direction: Balance and Intelligence cost roughly twice as much as the Cost mode on average, and up to two to four times as much depending on the mode selected.
That is the part worth sitting with. A system that chooses the model on your behalf, and can multiply the bill several times over depending on setting, shipped nine days before the page showing what each choice cost switched to tokens.
Why Australian businesses should care
For an Australian firm with an in-house development team, this is a governance problem before it is a pricing one. Cursor Teams is $40 per seat a month on Standard and $120 on Premium month to month, or $32 and $96 on annual contracts. A 25-developer team on Premium annual runs to $2,400 a month before any on-demand usage.
The invoice still arrives, and the Spending page still shows what was billed. What has gone is the granularity underneath it: which model, on which request, for how much. That is the layer an engineering or finance lead uses to work out why one sprint cost triple the last one, or whether the router is picking expensive models for cheap tasks. Teams weighing Cursor against GitHub Copilot now have one fewer way to compare running costs.
Australian firms already reined in AI spending this year as costs ran past budgets, and Claude Sonnet 5 was due for a 50 per cent price rise on 1 September until Anthropic cancelled it on 11 August. Losing per-model visibility in the same quarter makes that harder to manage, not easier. It is the problem AI governance work keeps surfacing: teams buy the tool, then find the reporting belongs to the vendor.
A vendor that is changing hands
There is a second reason to pay attention. On 16 June SpaceX agreed to buy Anysphere, Cursor’s parent company, for $60 billion in stock, as reported by Forbes. The deal is expected to close in the third quarter. Cursor’s annual recurring revenue was put at around $4 billion against a prior valuation near $30 billion.
SpaceX merged with xAI in February, giving the combined entity a valuation of about $1.25 trillion. None of this has closed yet and it may change nothing for customers. But a tool that sits inside your codebase is about to change owner mid-contract, and its reporting behaviour changed first.
The practical response is unglamorous. Pull your own consumption data rather than relying on the vendor’s dashboard, set hard caps on on-demand usage, and check whether your agreement says anything about continuity of reporting or notice on change of control. Most agreements say nothing at all.
