AINEWS
Cursor's AI code editor now shows individual subscribers token counts where they used to see per request dollars. Cursor calls the change 'deliberate design'; users on the forum say it makes spending harder to track.
Cursor, the AI code editor that costs individual users a flat monthly fee for included usage plus on-demand spending beyond that, has removed the dollar figure from the page its subscribers check most often. The Usage page on individual plans now shows how many tokens each request consumed. The dollar number that used to sit beside those requests is gone from that page.
The change is recent and is driving paying-customer complaints on the Cursor forum and on Hacker News (Cursor forum thread; Hacker News discussion). Cursor's support response in the forum calls the redesign "deliberate." That answer is the story, not a closing argument.
What changed, exactly
The individual-plan Usage page now shows how many tokens each request consumed, with covered usage marked "Included" in the interface. Enterprise plans still show dollars, because their customers pay from a shared, pooled usage budget that the company bills against directly.
Dollar amounts for on-demand usage are not gone from Cursor entirely. They moved. They now live at Dashboard > Spending, which shows the on-demand figure for the current billing cycle in dollars, and in the Cost column of the CSV export at Dashboard > Usage > Export CSV. Neither path is the daily-check page most subscribers trained themselves to open, and neither updates in real time the way the old per-request dollar view did.
Cursor frames the redesign as a response to a specific confusion: the dollar total on the old Usage page routinely exceeded what the customer actually owed. That happened because Cursor's individual plans bundle a generous slice of included usage. If a user burned through, say, $40 worth of model compute in a month but only owed $20 because $20 sat inside their plan, the page showed $40. The number was real, but it was not the bill.
Under the new design, tokens make the underlying quantity legible. "Included" tells the customer they did not pay for that portion. The dollar figure for the portion they did pay for is now a click away, in a different surface.
Why individual users feel the change
For most paid software, the daily-check page is the bill. A reader who built the habit of opening Cursor's Usage page to see what they had spent is now opening it to see what they consumed, in a unit (tokens) that does not translate directly into a credit-card charge.
That habit matters more on team plans. A developer on a shared plan with an on-demand cap can no longer watch their own contribution to the shared bucket in dollars. The per-user cost of their work shows only in tokens on the Usage page or, retroactively, in the CSV. The Spending page on Dashboard > Spending does aggregate dollars for the account, but the per-day, per-request, per-user view that used to be one page away is now a column in a downloadable file.
Cursor's reason, examined
The included-usage-versus-actual-cost tension is real. A dollar total that includes subsidized usage is, strictly speaking, not what the customer owes. Showing the underlying tokens, with "Included" tagged where they are free, is a more honest display of what the customer is doing, even if it is a less convenient display of what the customer is paying.
The honest display is also harder to read at a glance. Tokens do not map cleanly to cents in a user's head, and Cursor does not surface a running per-cycle dollar estimate on the Usage page itself. A subscriber who wants that number has to either look at the Spending page or pull the CSV.
The asymmetry is the part Cursor has not publicly addressed. Enterprise plans still show dollars because their customers are paying from a pooled budget with no per-user "included" slice to mark. Individual plans do not show dollars because the included-usage distinction makes a naïve dollar total misleading. Both are defensible design choices, but they are different choices for different customers, and the design treats the customer paying out of pocket as the one who needs less information.
What individual subscribers should do
For paying users who want the daily dollar check back, two paths exist today. The Dashboard > Spending page shows on-demand spend for the current cycle in dollars. The CSV export at Dashboard > Usage > Export CSV includes a Cost column for every request. Neither is on the page most customers were trained to open.
Whether Cursor adds a user-facing setting to restore the dollar view on the Usage page is the open question. The forum thread is public, the complaint is consistent across multiple subscribers, and the company has not signaled a change of position. For now, individual subscribers are voting with their forum posts, and the dollars live in the export.