Cursor quietly removed cost tracking from its usage dashboard, leaving teams blind to per-model AI spend

Cursor Removed Cost Data From Its Dashboard. Teams Can No Longer See What They Spend.

On July 31, Cursor replaced every dollar figure on its usage dashboard with token counts. Self-serve plan customers, including Teams, lost their cost data overnight. 1

Kevin Neilson, a staff member at Cursor, confirmed in the company's community forum that the change was deliberate. A code update shipped that day made the usage page tokens-only for self-serve plans. The Spend metric and Cost column were removed from the dashboard, CSV exports no longer contain dollar costs, and the API endpoint that previously returned per-request cost fields now returns zeros. Enterprise plans retained full dollar visibility. 1

For engineering teams that treat Cursor as core infrastructure, the practical consequence is immediate. There is no longer a way to audit per-model or per-user spending on any self-serve plan. A Teams plan administrator posting on the forum reported a combined usage cost of $30,000 in the current billing cycle and asked how to track spend by model and by user going forward. Neilson confirmed that no per-model dollar breakdown exists for self-serve plans, though Teams admins can still access a per-user on-demand total through the admin dashboard. 1

The removal is also retroactive. Because the zeroing is applied when usage records are read rather than when they are stored, historical cost data that teams had already exported and built reporting around is now blank. A forum user reported that API fields which previously carried real dollar values, including chargedCents and usageBasedCosts, now return zeros for every event, including on-demand usage that customers are actively billed for. 1

This lands on top of a pricing shift that was already making bills hard to predict. In June 2025, Cursor moved from request-based pricing, where Pro users had a fixed monthly limit of 500 requests, to API-based pricing tied to each model's token consumption. Under the new model, the same number of requests could cost vastly different amounts depending on which models a developer selected. 2

The rollout drew immediate backlash from users hit with unexpected charges. Michael Truell of Cursor posted an apology on July 4, 2025, acknowledging that the company "didn't handle this pricing rollout well" and offering refunds for surprise usage incurred between June 16 and July 4. Cursor committed to providing "advance notice, clearer documentation" for future pricing changes. 2

The cost tracking removal shipped with neither. Forum users discovered it when their dashboards changed, not through any company announcement. 1

The pattern is worth naming. Replace a predictable request-based pricing model with metered billing that makes monthly costs variable. Then remove the dashboard, the export, and the API fields that let customers see the meter running. It is the equivalent of a restaurant switching from a fixed-price menu to a la carte ordering and then erasing the prices from the bill. The kitchen knows what each dish costs. The diner does not.

The vendor retains full visibility into what every account spends. Neilson's explanation that the zeroing happens when records are read, rather than when they are stored, confirms the underlying cost data still exists in Cursor's systems. The company chose to stop sharing it with customers on self-serve plans. 1

Customers get token counts instead. One forum user called token-only reporting "irrelevant as it's highly different to each model," because raw token counts reveal nothing about cost when different models price at radically different rates per million tokens. 1

The discussion reached Hacker News within hours, where developers expressed frustration over the removal. 3

For finance teams at engineering organizations, the math is direct. A platform that charges based on model-specific token consumption has removed the only view that showed what each model costs per user. Teams running five-figure billing cycles on Cursor can still see a per-user total. They can no longer see which models are driving the bill.