Warning: abnormal token counting after Cursor version update; no in-forum support for billing

Heads up to anyone considering updating Cursor to a newer version.

After I upgraded the Cursor app (software version:2.4.28), I started seeing abnormal token usage in my usage report — single requests with tens of millions of tokens (e.g. 27M–230M total, huge cache read numbers) and costs per request that don’t match normal use. I hadn’t changed how I use Cursor; the jump coincided with the version update.

When I tried to get help here, I was told that billing and limit issues aren’t handled on the forum and my thread was unlisted. Support asked me to email [email protected] instead. So if you run into similar issues after updating Cursor, you won’t get a fix in the forum; you have to go through email, and responses can take a while.

My suggestion: before you click “Update” on Cursor, check the latest discussions and your own usage. If your current Cursor version is stable and usage looks normal, don’t upgrade just because a new version is offered — wait until you’re sure the new version’s token counting and limits match what you expect. Once you’ve upgraded and hit usage limits or abnormal charges, getting it sorted is through email only and can be slow.

I’m posting this so others can make an informed decision. No rant, just a caution from experience.

1 Like

I just updated and it immediately told me I had run out of usage (Pro Plus plan), the moment i launched following the update. I’ve never run out of tokens in audo mode before.

+1.
Facing the same issue.