Cursor Usage Page Changes: Removal of Dollar Cost Tracking

Cursor Removes Dollar Cost Visibility for Individual Plans

Cursor has replaced dollar-denominated cost tracking with token amounts on its usage page for individual users. This change is a deliberate design decision intended to reduce confusion among users who saw API-equivalent costs that exceeded their monthly subscription fees due to the generous included usage in individual plans.

According to Cursor staff, the intended behavior is as follows:

  • Individual Plans: The usage page now displays token counts. Items covered by the subscription are marked as "Included."
  • Enterprise Plans: Dollar amounts remain visible due to thes pooled usage structure of enterprise accounts.
  • On-Demand Usage: For usage exceeding the included plan limits, dollar figures continue to appear in the Cost column.

How to Track Spending in Cursor

While the real-time usage graph has been removed for individual users, cost data remains accessible through two primary channels:

  1. The Spending Page: The Dashboard > Spending section provides the total On-Demand Spending figure for the current billing cycle, which matches the final billed amount.
  2. CSV Export: Users can navigate to Dashboard > Usage, set their desired date range, and export a CSV. The Cost column in this export contains dollar amounts for every on-demand request. (Note: A temporary bug that broke dollar costs in the CSV export was reported and subsequently fixed by Cursor staff).

User Feedback and Community Response

The removal of cost visibility has triggered significant backlash from the developer community, with users arguing that transparency is essential for budget management and ROI calculation.

Loss of Budget Control

Many power users and team leads reported using the spending graph multiple times a day to monitor budgets. The shift to tokens is criticized as impractical because token costs vary significantly across different models, making a raw token count an ineffective proxy for financial cost.

"I know countless of Cursor users who used this Spending Graph feature dozens of times a day to keep track of their budget. Now you’re completely hiding the cost. Who cares about tokens? It’s irrelevant as it’s highly different to each model."

Impact on Team Management

Users on Team plans expressed difficulty in tracking per-user and per-model spend, which was previously possible. This lack of granularity makes it harder for managers to allocate costs or for individual team members to track their personal contribution to a shared on-demand usage cap.

Concerns Over "Enshittification"

Some community members viewed the move as a sign of declining user trust and a trend toward "user-hostile" design. Critics argue that hiding costs does not remove the user's anxiety regarding spending but instead removes the ability to verify those costs, potentially leading users to disengage from the tool.

"Hiding a usage number doesn't remove the anxiety, it just removes the user's ability to verify it... A scary number you can explain beats a hidden one they have to guess at."

Alternative Tooling and Market Context

In the wake of these changes, some users have mentioned migrating to alternative agentic IDEs and tools such as Claude Code, Codex, and Claude Desktop. Discussions among users highlight that while Cursor's Composer 2.5 remains a strong feature, the perceived lack of transparency in pricing and usage tracking is driving some users to consider alternatives that offer more direct API-based cost control.

Sources