Cursor removed cost information from the usage page and CSV export

Cursor users who track their spend through the editor's Usage page found on 31 July 2026 that it had changed: dollar amounts were replaced by token counts, and there is no setting to switch the old view back. A thread on the official Cursor forum titled "Usage Page $$ to Token Amount? WHAT?" drew dozens of replies, and Cursor staff confirmed the change was deliberate rather than a bug.

What was removed

A change shipped that day made the Usage page tokens-only for self-serve plans, including Teams. The Spend metric and the Cost column disappeared, and the usage CSV export no longer contains dollar costs. Individual plans have no option to restore the old view; Enterprise plans still show dollar amounts. Cursor explains the split by plan structure: enterprise plans pool usage, while individual plans bundle a generous amount of included usage into the subscription price.

The official explanation

According to a Cursor staff member, Ultra runs on usage-based (token) pricing. On that model, anything covered by the plan shows token counts marked "Included", because nothing is charged for it, while usage actually paid for — on-demand beyond the included amount — still shows a dollar figure in the Cost column. Displaying dollar amounts for individual plans, staff wrote, was briefly tried and led to confusion, because the figures shown were often higher than the user's plan cost. Where the dollars still are: Dashboard → Spending shows an On-Demand Spending figure for the current cycle, and Dashboard → Usage with a date range plus Export CSV keeps dollar amounts for every on-demand row. For Teams admins there are per-user on-demand totals under Dashboard → Members → On-Demand, and the Admin API still provides spending data and cost fields for usage events — but there is currently no per-model dollar breakdown for self-serve Teams and individual plans.

Reaction and an API regression

Thread participants called the decision a step back for transparency: teams sharing an on-demand cap used the per-user, per-model and per-request figures to control budgets — one commenter reported a combined usage cost of $30,000 for the current cycle — and asked for at least a toggle that defaults to tokens. Users also found that the dashboard usage API endpoint (get-filtered-usage-events) now returns zeroed cost fields (chargedCents: 0, usageBasedCosts: "$0.00", totalCents omitted) for all events, including historical records and on-demand usage that is actually billed. Staff replied that this is intentional, that the zeroing is applied when records are read so historical results are affected too, and that aggregate billing totals are not equivalent to the removed per-request cost data.