Your usage is still being recorded correctly on every request, and both your limits and billing run off that live data, so nothing’s being lost or mischarged. It’s the Spending meter itself that’s stuck: on busy accounts it’s served from a cached figure that can freeze, which is an issue we’re tracking (not anything on your end).
For your real numbers right now, use the per-request Usage events / Spending detail on cursor.com/dashboard. And since you mentioned the reset: included usage resets at your subscription’s anchor time (when you first subscribed), not midnight, so it can look like it hasn’t rolled over until later in the day.
No timeline to share yet, but I’ll post here when there’s an update.
One note, I do find the Spending page very valuable because it helps me judge the overall costs of my usage. This last day of my plan, I had a need to use a lot of frontier level planning without knowing if I was hitting the limit or not, but seeing the spending amount allows me to pace model usage throughout the month. I can’t really use the Usage Screen quite the same way, each has important detail which needs the other to paint a complete usage picture.
That said, it is an important stat for me to keep within my limits, thus, I have a feature suggestion: place the Spending data on the Usage screen so it can all be seen in one location. Having the spending widget at top with usage below would be seriously useful instead of having to go back and forth. And make it available in the Cursor settings, like “Plan & Usage” does, or make that page show both data.
The Spending page freeze is fixed. It turned out to be an issue on our side with how usage totals were aggregated for display, and it was resolved on our end around August 14, so there’s nothing you need to do — the meters caught up on their own. As before: your usage was recorded correctly the whole time, so limits and billing were never affected by the stuck display. If you ever spot the Spending page lagging behind your real usage again, please let me know.
We are a Teams customer who incurred ~US$2,500 in on-demand charges while this exact totalPercentUsedbug was active (11–12 Aug 2026). The usage percentage shown to the seat holder remained frozen/stale throughout the period, while on-demand billing continued silently in the backend.
We have opened multiple support tickets (T-E88959, T-E88979, T-E88987, T-E89233) but have received only identical AI auto-replies from “Sam” refusing human review and citing a blanket “no refunds for on-demand usage” policy. None of the replies addressed the documented defect.
This bug is not cosmetic — for Teams members, the frozen percentage was the only usage signal available, as there is no per-seat on-demand dollar view and no per-seat hard limit on self-serve Teams. Combined with zero warnings delivered during the 48-hour window, the customer had no mechanism to detect or stop the charges.
